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 #91863 (Closed): Remove selected option with http://forge.typo3.org/issues/918632020-07-24T14:13:37ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>EXT:styleguide inline usecombination (Form engine - inline use combination: uid 1) press the "Create new relation" button</p>
<p>Expectation:</p>
<p>The first option of the select box should be added as inline element and be removed from the select box.</p>
<p>Current:</p>
<p>The first option is added as inline element but is not removed from select box.</p> TYPO3 Core - Bug #91839 (Closed): IRRE add relation button not workinghttp://forge.typo3.org/issues/918392020-07-22T16:40:07ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>Some TCA adding a new IRRE field to any table:</p>
<pre>
'translations' => [
'exclude' => 1,
'l10n_mode' => 'exclude',
'label' => 'Translations',
'config' => [
'type' => 'inline',
'foreign_table' => 'pages_translations',
'foreign_field' => 'parentid',
'foreign_sortby' => 'parentsort',
'foreign_table_field' => 'parenttable',
'foreign_selector' => 'language',
'foreign_unique' => 'language',
'foreign_label' => 'language',
'maxitems' => 9999,
'appearance' => [
'collapseAll' => 1,
'expandSingle' => 1,
'newRecordLinkAddTitle' => 1,
'newRecordLinkPosition' => 'top',
'useCombination' => 0,
'useSortable' => 0,
'showPossibleLocalizationRecords' => 0,
'showRemovedLocalizationRecords' => 0,
'showAllLocalizationLink' => 0,
'showSynchronizationLink' => 0,
'enabledControls' => 'delete',
],
'behaviour' => [
'localizationMode' => 'keep',
'localizeChildrenAtParentLocalization' => 0,
'disableMovingChildrenWithParent' => 1,
],
],
],
</pre>
<p>Expectation:</p>
<p>The user should be able to add the first entry from the selectbox by click on the "add new relation" button</p>
<p>Current:</p>
<p>The button doesn't do anything.</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 #88781 (Closed): UI improvements for page clearing actionhttp://forge.typo3.org/issues/887812019-07-16T14:15:29ZNicole Cordestypo3@cordes.co
<p>Due to the changes done in <a class="external" href="https://forge.typo3.org/issues/88718">https://forge.typo3.org/issues/88718</a> the user experience should be improved.</p>
<p>before:<br />- the user saw an action happening after he/she pressed the button <br />- he/she knew about reloading and waiting time<br />after:<br />- no visual action seen anymore; the button can be pressed multiple times<br />=> maybe the button should turn into a spinner and be disabled after the first usage as long as the request takes<br />- if the user changes the view (e.g. views another page, edit the page or a content element) the browser (at least chrome) stops the asynchrone request immediately; no further notification for the user will be shown<br />=> the user should be informed that the "clearing request" is still in progress and gets aborted if the view is changed</p>
<p>Furthermore I think there should be some conceptional work on how to deal with the actions in context menu. Currently there is no visible processing (at least for cache clearing) either. Some wild proposals from my side: a spinning icon in the page tree if any action was chosen or an overall ajax processing queue that is visible e.g. within the top bar.</p> TYPO3 Core - Bug #87827 (Closed): Wrong default database charset appliedhttp://forge.typo3.org/issues/878272019-03-03T19:50:03ZNicole Cordestypo3@cordes.co
<p>With the patch <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/59323">https://review.typo3.org/c/Packages/TYPO3.CMS/+/59323</a> an empty default charset if not defined. However before the default charset was ensured be to set to 'utf8'.</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 #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 #86147 (Under Review): Prevent updating unchanged fields in DataMapProcessorhttp://forge.typo3.org/issues/861472018-09-04T16:45:58ZNicole Cordestypo3@cordes.co
<p>Given:</p>
<p>- a table with some additional IRRE relations and fields with TCA configuration ['behaviour']['allowLanguageSynchronization'] enabled<br />- open a record from the given table<br />- save it without any changes</p>
<p>Expected:</p>
<p>- saving an untouched record should not update any other record as nothing has changed</p>
<p>Actual:</p>
<p>- related records are updated even without any changes<br />- fetching related records recursively (parents, siblings, relations) takes very long and may result in a "maximum execution time" error</p> TYPO3 Core - Bug #82880 (New): Synchronize inline records triggers maxItemsErrorhttp://forge.typo3.org/issues/828802017-10-29T14:01:51ZNicole Cordestypo3@cordes.co
<p>How to reproduce:</p>
<p>1. Install attached extension.<br />2. Add new page.<br />3. Insert "Container" record on the created page.<br />3.1 Add two content records to "Container" field.<br />4. Translate the page to another language.<br />5. Translate the content element with "Translate" mode.<br />6. Open the container element in default language and attach a third inline content element.<br />7. Open the translated container element. You will see the third inline content element without translation.<br />8. Synchronize translated records with "Synchronize with original language"</p>
<p>Expected result:</p>
<p>I see three translated content records.</p>
<p>Actual result:</p>
<p>I see only two content elements afterwards. An error "A maximum of 3 child records are allowed." is triggered. Reloading the page however shows the expected records.</p>
<p>Guess:</p>
<p>I think the error is triggered before the untranslated record is removed. Thus the JavaScript prevents add the new (translated) content record. It seems the PHP-part of the localization works without errors.</p>