TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-06-26T13:37:49ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101168 (New): Copy elements with IRRE field deletes copied translationshttp://forge.typo3.org/issues/1011682023-06-26T13:37:49ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- system with at least two languages<br />- install the attached extension<br />- create a new page and translate into another language<br />- create a new content element "copy_irre" and attach a child link<br />- translate the content element into the other language<br />- change the link label of the translated child link<br />- copy the content element and paste it anywhere on the site</p>
<p>Expectation:</p>
<p>- a copied content element should be visible<br />- the label of the translated child should match the original translation</p>
<p>Actual:</p>
<p>- the original link gets synchronized again, the label gets lost</p>
<p>It seems the correct translation is created first but gets deleted again and a new synchronization is created.</p>
<p>The copy & paste steps work correctly if the allowLanguageSynchronization is turned off.</p> TYPO3 Core - Bug #100807 (New): Analyze Database Structure fails with EnforceableQueryRestriction...http://forge.typo3.org/issues/1008072023-05-04T10:34:43ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- an own class implementing the QueryRestrictionInterface and EnforceableQueryRestrictionInterface using a constructor dependency to another class<br />- this class is marked as public in settings.yaml<br />- this class is registered in $GLOBALS['TYPO3_CONF_VARS']['DB']['additionalQueryRestrictions']</p>
<p>Expectation:</p>
<p>- calling "Analyze Database Structure" in maintenance module should compare the current database structure with expected on</p>
<p>Actual:</p>
<p>- an error occurs as the (constructor) dependency cannot be resolved<br />- the failsafe container instead of the symfony dependency container is used</p> TYPO3 Core - Bug #95967 (Closed): Drag & Drop broken in page modulehttp://forge.typo3.org/issues/959672021-11-12T14:24:48ZNicole Cordestypo3@cordes.co
<p>Given:<br />- TYPO3 11 installation<br />- admin user<br />- disabled hash cache with `$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['hash'][backend'] = \TYPO3\CMS\Core\Cache\Backend\NullBackend::class;`<br />- page with at least two content elements</p>
<p>Expected:<br />- one content element can be moved</p>
<p>Actual:<br />- PHP exception is thrown and content element isn't moved</p> TYPO3 Core - Bug #93216 (Under Review): Include addRootLineFields in page tree controllerhttp://forge.typo3.org/issues/932162021-01-04T16:00:06ZNicole Cordestypo3@cordes.co
<p>Given:<br />- an own overlay for pages should be added using the $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS'][\TYPO3\CMS\Core\Imaging\IconFactory::class]['overrideIconOverlay']<br />- coming from \TYPO3\CMS\Backend\Controller\Page\TreeController::fetchDataAction only a hardcoded list of fields is available in a page record row</p>
<p>Expectation:<br />- page records are fetched with fields from $GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields']</p>
<p>Actual:<br />- only static fields are fetched (see \TYPO3\CMS\Backend\Controller\Page\TreeController::getPageTreeRepository)</p> TYPO3 Core - Bug #91491 (Closed): Speed up pages_language_overlay update wizardhttp://forge.typo3.org/issues/914912020-05-26T12:58:54ZNicole Cordestypo3@cordes.co
<p>To speed up the MigratePagesLanguageOverlayUpdate wizard (especially for big sites with lots of pages), the pages table needs to get an index for legacy_overlay_uid column.</p> TYPO3 Core - Bug #90182 (Closed): Missing text when linking to other site with non-existing languagehttp://forge.typo3.org/issues/901822020-01-23T12:29:45ZNicole Cordestypo3@cordes.co
<p>Given:<br />- two roots with site configuration<br />- one page tree (1) uses two languages (e.g. de and en)<br />- the other page tree (2) uses other languages (e.g. de and dk)<br />- a text element in (1) and in en links to a page in (2)</p>
<p>Expectation:<br />- the link cannot be generated as (2) does not support en<br />- the text should be visible without any link</p>
<p>Actual:<br />- the linked text is completely missing in output</p> TYPO3 Core - Bug #89153 (Closed): Wrong Extbase record is shown for slughttp://forge.typo3.org/issues/891532019-09-11T17:27:08ZNicole Cordestypo3@cordes.co
<p>Given:<br /> - page with at least two languages configured<br /> - Extbase extension with own records<br /> - two records with translations in multiple (at least two) languages<br /> - own slug configuration for translations</p>
<p>Simple example:<br /> - current news version<br /> - routeEnhancers configuration from <a class="external" href="https://docs.typo3.org/p/georgringer/news/master/en-us/AdministratorManual/BestPractice/Routing/Index.html#about-routes-and-aspects">https://docs.typo3.org/p/georgringer/news/master/en-us/AdministratorManual/BestPractice/Routing/Index.html#about-routes-and-aspects</a><br /> - two news in default language and (all) translations<br /> - slug for news 1 / language 1 = foo<br /> - slug for news 1 / language 2 = bar<br /> - slug for news 2 / language 1 = bar<br /> - slug for news 2 / language 2 = foo</p>
<p>Expectation:<br /> - path: /language1/foo shows news 1<br /> - path: /language1/bar shows news 2</p>
<p>Actual:<br /> - both paths show the same news (either news 1 or news 2)</p> TYPO3 Core - Bug #87188 (Closed): FrontendUserImageUpdateWizard is marked as done even when error...http://forge.typo3.org/issues/871882018-12-17T15:42:28ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- an installation to upgrade from 7.6.32 to 8.7.22<br />- some missing files in uploads/pics/ that are used in fe_users.image field</p>
<p>Expected:</p>
<p>- an error/information about the missing file(s) is shown<br />- the update wizard can be re-run</p>
<p>Actual:</p>
<p>- the update wizard is marked as done and needs to be re-enabled manually</p> TYPO3 Core - Bug #87187 (Closed): Upgrade wizard ignores step "Update database schema" if an SQL ...http://forge.typo3.org/issues/871872018-12-17T14:29:52ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- an upgrade from 7.6.32 to 8.7.21<br />- an extension with wrong SQL in ext_tables.sql</p>
<p>```<br />CREATE TABLE tx_foo_domain_model_bar (<br /> fetched boolean DEFAULT '1' NOT NULL,<br />);<br />```</p>
<p>Expected:</p>
<p>- an error should be shown anywhere</p>
<p>Actual:</p>
<p>- the step "Update database schema" is silently skipped resulting in a fatal error because of missing l10n_source field in tt_content</p> TYPO3 Core - Bug #86958 (Closed): Disable Extension update in Composer modehttp://forge.typo3.org/issues/869582018-11-20T23:16:16ZNicole Cordestypo3@cordes.co
<p>Currently it is possible to trigger an extension update even in Composer mode. This needs to be disabled to not break any installation.</p> TYPO3 Core - Bug #86655 (Closed): GeneralUtility::rmdir needs a fully initialized Environment ins...http://forge.typo3.org/issues/866552018-10-14T21:12:34ZNicole Cordestypo3@cordes.co
<p>The typo3/testing-framework calls GeneralUtility::rmdir to remove existing test instances. Unfortunately this fails an Windows systems as those are not properly detected by an uninitialized Environment and Environment::isWindows() returns false.</p> TYPO3 Core - Bug #86403 (Closed): Missing FlexForm context for USER display conditionshttp://forge.typo3.org/issues/864032018-09-27T16:06:08ZNicole Cordestypo3@cordes.co
<p>Given:<br />- a FlexForm with a field having a display condition using a user function</p>
<p>Expected:<br />- the user function should receive all information provided by the parent object (TYPO3\CMS\Backend\Form\FormDataProvider\EvaluateDisplayConditions)</p>
<p>Actual:<br />- only the current used database row, the parsed condition parameter and a flexformValueKey is provided<br />- the whole information about which field is evaluated or the parsed FlexForm context is missing</p> TYPO3 Core - Bug #86212 (New): Extended tab with IRRE relation is not opened by defaulthttp://forge.typo3.org/issues/862122018-09-10T00:02:49ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- the attached extension installed<br />- open a new tt_content element record<br />- go to tab "Extended" add a new "Related Content" and save<br />- again go to tab "Extended" and save (no other changes necessary)</p>
<p>Expected:</p>
<p>- the last opened tab "Extended" should be reopened by default</p>
<p>Actual:</p>
<p>- the tab "Extended" is marked as active, but the content from "General" is shown</p> TYPO3 Core - Bug #86208 (Closed): Cannot close "Check for broken extensions" overlayhttp://forge.typo3.org/issues/862082018-09-09T18:50:47ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- go to "Upgrade" module<br />- hit the "Check Extension Compatibility" button<br />- an overlay opens and the extensions are checked</p>
<p>Expected:</p>
<p>- if everything is successfully finished, I want to go back to any other module</p>
<p>Actual:</p>
<p>- there is no way to close the overlay (neither if an error occurs)</p> TYPO3 Core - Bug #85404 (Closed): Missing button to lock install toolhttp://forge.typo3.org/issues/854042018-06-27T12:26:05ZNicole Cordestypo3@cordes.co
<p>With the rewrite of the install tool a way to lock the install tool again seems to be missing. Neither in the standalone part nor in the backend I'm able to lock the install tool again.</p>
<p>Scenario:</p>
<p>- login to the backend as admin user <br />- open one install tool module<br />- logout</p>
<p>Expected:</p>
<p>- the install tool is not accessible anymore</p>
<p>Actual:</p>
<p>- the install tool is still available within the browser session without any change to lock it</p>