TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-08-09T18:22:08ZTYPO3 Forge
Redmine TYPO3 Core - Bug #85797 (Closed): Too many record uids in plain data resolver break TYPO3http://forge.typo3.org/issues/857972018-08-09T18:22:08ZGleb Levitingleb.levitin@dkd.de
<p>Do not use prepared statements in sorting function of plain data resolver.</p> TYPO3 Core - Bug #85795 (Closed): Too many records on reference index updating break TYPO3http://forge.typo3.org/issues/857952018-08-09T16:59:34ZGleb Levitingleb.levitin@dkd.de
<p>Do not use prepared statements for updating reference index</p> TYPO3 Core - Bug #81619 (New): stdWrap_override does not override the current value if new value ...http://forge.typo3.org/issues/816192017-06-19T16:14:04ZGleb Levitingleb.levitin@dkd.de
<p><strong>IS STATE</strong></p>
<p><a href="https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php#L1864" class="external">EXT:sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php::stdWrap_override</a> does not override <code>$content</code> variable with a value, if this new value consists of a single symbol "0". This is for example necessary, if a result of TypoScript condition should be overriden.</p>
<p><strong>SHOULD STATE</strong></p>
<p>It should be at least possible to override the existing TypoScript content with a string containing a single symbol "0".</p>
<p><strong>Further considerations</strong></p>
<p>It must be also considered, whether every content presenting in <code>$conf['override']</code> should be taken as replacement. In case, if overriding should not occur due to appropriate override condition, than <code>$conf['override']</code> key can be completely removed from <code>$conf</code> array. The only test, if the content is to be overridden can then be alone the existence of <code>$conf['override']</code>.</p> TYPO3 Core - Bug #80001 (New): Workspace email notification contains preview link ony to the firs...http://forge.typo3.org/issues/800012017-02-24T14:17:13ZGleb Levitingleb.levitin@dkd.de
<p>The workspace email notification to users after completion the DataHandler operations contain the preview link <strong>only to the first page</strong> in the set of changed data.</p>
<p><strong>Example:</strong></p>
<p>Imagine, there has been changes for the following content elements within a workspace:<br /><pre>
"pages:234, pages:1723, tt_content:2410";
</pre></p>
<p>Then the following lines of code wil explode the first {table:uid} occurrence for generating the preview link (here page with uid 234).</p>
<p><code>SYSEXT:version/Classes/Hook/DataHandlerHook.php::notifyStageChange</code><br /><pre>
list($elementTable, $elementUid) = explode(':', $elementName);
$elementUid = (int)$elementUid;
</pre></p>
<p><strong>IS STATE:</strong><br />The remaining records in the dataset are ignored. This is not correct!</p>
<p><strong>SHOULD BE STATE:</strong><br />The preview links should be generated for all the changed pages or pages containing changed records.</p> TYPO3 Core - Bug #78976 (Closed): Add missing DOM ready check for JavaScripts in filelist modulehttp://forge.typo3.org/issues/789762016-12-13T13:08:26ZGleb Levitingleb.levitin@dkd.de
<p>In spite of adding the missing DOM ready checks to various AMD modules in <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Add missing to DOM ready checks to all AMD modules (Closed)" href="http://forge.typo3.org/issues/70601">#70601</a>, there is still a number of AMDs in the Core, suffering from this defect. <br />For example the JavaScripts from <code>filelist</code> Extension, placed in <code>SYSEXT:filelist/Resources/Public/JavaScript</code> are affected by this defect.</p> TYPO3 Core - Task #78975 (Closed): Refactor DOM ready check with AMD loader plugin domReadyhttp://forge.typo3.org/issues/789752016-12-13T12:52:37ZGleb Levitingleb.levitin@dkd.de
<p>In <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Add missing to DOM ready checks to all AMD modules (Closed)" href="http://forge.typo3.org/issues/70601">#70601</a> a lot of RequireJS AMDs were provided with a DOM ready check function to prevend their potential run into race condition. <br />The DOM ready check was taken with JQuery. It works, but in RequireJS there is an AMD loader plugin <a href="https://github.com/requirejs/domReady" class="external">domReady</a> for this purpose. It should be used instead.</p>
<p>Here is the appropriate API documentation and an understandable example:</p>
<p><a class="external" href="http://requirejs.org/docs/api.html#pageload">http://requirejs.org/docs/api.html#pageload</a></p> TYPO3 Core - Bug #78872 (Closed): Deprecate method getRecordUidsToCopyhttp://forge.typo3.org/issues/788722016-12-03T11:31:48ZGleb Levitingleb.levitin@dkd.de
<p>The following method is not used at any place and can be deprecated for the next TYPO3 version.</p>
<p><code>SYSEXT:backend/Classes/Controller/Page/LocalizationController.php:getRecordUidsToCopy</code></p> TYPO3 Core - Bug #78856 (Closed): Page Tree is not loadedhttp://forge.typo3.org/issues/788562016-12-01T17:57:17ZGleb Levitingleb.levitin@dkd.de
<p>The page tree in TYPO3 Backend is in the meantime not loaded. Firebug console shows the following error messages:</p>
<p><img src="http://forge.typo3.org/attachments/download/31804/page_tree_js_error.png" loading="lazy" style="width:850px;" alt="" /></p> TYPO3 Core - Bug #78701 (Closed): The source language is wrong determined for copied record trans...http://forge.typo3.org/issues/787012016-11-15T13:38:03ZGleb Levitingleb.levitin@dkd.de
<p><strong>How to reproduce:</strong></p>
<p>Imagine, you have a single record with translation.</p>
<p><img src="http://forge.typo3.org/attachments/download/31749/original_data_set.png" alt="" loading="lazy" /></p>
<p>Now copy this record into a new page and add a new content element to the default language column.</p>
<p><img src="http://forge.typo3.org/attachments/download/31750/new_record_in_the_copied_data_set.png" alt="" loading="lazy" /></p>
<p>Now click "Translate" button in the target language column.</p>
<p><img src="http://forge.typo3.org/attachments/download/31751/wrong_counted_record_summary.png" alt="" loading="lazy" /></p>
<p>The element to be translated (New record) is not displayed in the records summary, but the already translated record (Text & Media Datensatz).</p>
<p><strong>Technical problem description:</strong></p>
<p>TYPO3 uses <em>t3_origuid</em> to determine, which language the translated records were originally derived from. In the case of a simple translation, <em>t3_origuid</em> is actually the UID of the record from which it was translated. However, <em>t3_origuid</em> is not only limited to this single function, but extends to many other types of derivation.</p>
<p>If a translated record is copied, the <em>t3_origuid</em> of the <ins>copied translated record</ins> will get the UID of the <strong>original translation</strong>, but not the <strong>original record</strong> itself.</p>
<p>Now, when creating new translations within the copied data set, the source language will be wrong determined and the already existing translated records will now be translated in the same language again.</p> TYPO3 Core - Task #78652 (Closed): Localization with defLangBinding = 1 is not limited to the sel...http://forge.typo3.org/issues/786522016-11-11T13:00:42ZGleb Levitingleb.levitin@dkd.de
<p>In page modul within Languages view there is only one common Translate button for all the records in the column in default case. When a redacteur clicks this button, then the counted record summary contains all the records of the column, that have not been translated in the target language until now. This is correct!</p>
<p><img src="http://forge.typo3.org/attachments/download/31734/localization_behavior_ok.png" alt="" loading="lazy" /></p>
<p>The following PageTS configuration allows however to provide each individual record in the column with a separate Translate button.</p>
<p>PageTS Configuration<br /><pre>
mod {
web_layout {
defLangBinding = 1
}
}
</pre></p>
<p>If any of these buttons is clicked, the counted record summary contains nevertheless still all the records of the column, that have not been translated in the target language until now. That is not correct und must be fixed!</p>
<p><img src="http://forge.typo3.org/attachments/download/31735/lacalization_behavior_error.png" alt="" loading="lazy" /></p>
<p><strong>Technical background</strong></p>
The following method is responsible for fetching the records for translation:
<ul>
<li><code>SYSEXT:backend/Classes/Controller/Page/LocalizationController.php::getRecordLocalizeSummary</code></li>
</ul> TYPO3 Core - Bug #77673 (New): URL parameters are updated only after the second saving of content...http://forge.typo3.org/issues/776732016-08-29T16:00:23ZGleb Levitingleb.levitin@dkd.de
<p>After initial saving of content element the URL-Parameters are not updated. This phenomenon makes it difficult to work for example with embedded wizards, when the current request uri must be forwarded to another script.</p>
1. Open content Element Wizard and choose any content element
<ul>
<li><strong>The displayed content ID:</strong> NEW</li>
<li><strong>Browser-URL:</strong> <a class="external" href="https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content][806]=new">https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content]<sup><a href="#fn806">806</a></sup>=new</a>...</li>
</ul>
2. Save the content element
<ul>
<li><strong>The displayed content ID:</strong> 2516</li>
<li><strong>Browser-URL:</strong> <a class="external" href="https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content][806]=new">https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content]<sup><a href="#fn806">806</a></sup>=new</a>... <br />SOLL ZUSTAND:<br /><del><a class="external" href="https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content][806]=new">https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content]<sup><a href="#fn806">806</a></sup>=new</a>...</del><br /><a class="external" href="https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content][2516]=edit">https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content]<sup><a href="#fn2516">2516</a></sup>=edit</a>...</li>
</ul>
3. Save Content Element once more
<ul>
<li><strong>The displayed content ID:</strong> 2516</li>
<li><strong>Browser-URL:</strong> <a class="external" href="https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content][2516]=edit">https://myhost.dev/typo3/index.php?route=/record/edit&token=d9384c66984433444278976106be63717ee63897&edit[tt_content]<sup><a href="#fn2516">2516</a></sup>=edit</a>...</li>
</ul> TYPO3 Core - Bug #76729 (Closed): Link to file's metadata does not work in full windowhttp://forge.typo3.org/issues/767292016-06-22T11:45:59ZGleb Levitingleb.levitin@dkd.de
<p>Metadata editing for file references works only within iframe (regular behavior). <br />If content element is opened in a full window, it's not more possible to navigate to file's metadata via appropriate icon.</p> TYPO3 Core - Task #76517 (Closed): Doctrine: migrate abstract functional test case. http://forge.typo3.org/issues/765172016-06-08T10:08:19ZGleb Levitingleb.levitin@dkd.de
<ul>
<li>FunctionalTestCase.php</li>
</ul> TYPO3 Core - Task #76471 (Closed): Doctrine: migrate sysext:saltedpasswordshttp://forge.typo3.org/issues/764712016-06-06T16:41:12ZGleb Levitingleb.levitin@dkd.deTYPO3 Core - Task #75642 (Closed): Refactor scheduler extensionhttp://forge.typo3.org/issues/756422016-04-15T09:52:11ZGleb Levitingleb.levitin@dkd.de
<p>The scheduler extension needs to be completely converted to extbase/fluid.</p>