TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-08-30T11:27:43ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101798 (New): Prevent saving unchanged inline records to save performancehttp://forge.typo3.org/issues/1017982023-08-30T11:27:43ZSebastian Michaelsenmichaelsen@t3seo.de
<p><strong>Problem</strong></p>
<p>When you have a record, which has 10 inline items and the record is translated (along with the inline items) into 10 languages, then saving the record even with no changes to the inline items causes the DataHandler to save 110 database records which can take some 30 seconds.</p>
<p><strong>Why is that?</strong></p>
<p>The inline records have toggles to hide/unhide them (unless the table does no support that), which means when saving the record there will be a `someid => ['hidden' => '0']` entry for each inline item, which causes DataHandler to save that inline item, which then also triggers saving of its translations.</p>
<p><strong>Solution(?)</strong></p>
<p>It could be solved in backend JavaScript, so that the inline `hidden` form fields are only included in the request when their value was changed.</p>
<p><strong>Workaround</strong></p>
<p>For our project I created a backend middleware, that intercepts the `data` when a record is saved and removes any entries, that have just the hidden field and it is unchanged. (Yes, I create a database request for each of those entries but it's still <em>way</em> faster than before)</p> TYPO3 Core - Bug #97776 (New): Disabled scheduler tasks are not dimmed outhttp://forge.typo3.org/issues/977762022-06-15T09:50:04ZSebastian Michaelsenmichaelsen@t3seo.de
<p>The <code>SchedulerModueController</code> says <code>// Row is shown dimmed if task is disabled, unless it is still running</code> and a corresponding CSS class <code>disabled</code> is set on disabled tasks, but visually there is no difference.</p>
<p>Tested in TYPO3 v10, but I suppose this is also the case in higher versions.</p> TYPO3 Core - Bug #93480 (New): PDF Cropping configuration is not possible for editorshttp://forge.typo3.org/issues/934802021-02-10T09:42:03ZSebastian Michaelsenmichaelsen@t3seo.de
<p>TYPO3 can create images from PDFs and can also crop them. But for editors it's not possible to set that cropping, because the cropping wizard doesn't work for PDFs.</p> TYPO3 Core - Bug #93433 (New): TCA placeholder __row|field doesn't translate related recordshttp://forge.typo3.org/issues/934332021-02-04T11:40:41ZSebastian Michaelsenmichaelsen@t3seo.de
<p>When using the __row|field syntax in placeholders, the related row is not overlaid with its translation.</p>
<p>example TCA for a tt_content field:<br /><pre>
'tx_myext_teaser_title' => [
'label' => $lll . '.tx_myext_teaser_title',
'config' => [
'type' => 'input',
'placeholder' => '__row|tx_myext_teaser_page|title',
],
],
</pre></p>
<p>For a translated content element, the placeholder should be filled with the value from the translated page record.</p> TYPO3 Core - Bug #92909 (New): Page Translation list is not orderable, but is rendered always in ...http://forge.typo3.org/issues/929092020-11-23T15:24:12ZSebastian Michaelsenmichaelsen@t3seo.de
<p>In the list view for translated pages the "Page Translation" list is always on top.</p>
<p>In the daily work of content editors this list will hardly ever be the most important one, but there is no possbility to reorder it, because <code>mod.web_list.tableDisplayOrder</code> doesn't have any effect on it.</p>
<p>The fact that you also can't really collapse it (<a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: Page and Page Translation lists can not be collapsed/expanded independently (New)" href="http://forge.typo3.org/issues/92907">#92907</a>) makes the situation worse.</p> TYPO3 Core - Bug #92907 (New): Page and Page Translation lists can not be collapsed/expanded inde...http://forge.typo3.org/issues/929072020-11-23T15:06:14ZSebastian Michaelsenmichaelsen@t3seo.de
<p>In the list module when you collapse/expand the "Page Translation" list, it will not be persisted. Instead it seems that it will always take over the state of the "Page" list.</p>
<p>Reproduce in a multi-language installation:</p>
<ol>
<li>Open a page in the list module that has translations and subpages. It will have “Page Translations” and “Page” record lists.</li>
<li>Collapse the “Page Translation” list by clicking the little “up”-chevron in the top right.</li>
<li>Refresh the module. “Page Translations” is not collapsed.</li>
<li>Collapse the “Page” list.</li>
<li>Refresh the module. Both lists are now collapsed.</li>
</ol> TYPO3 Core - Bug #92906 (New): File Metadata are not editable when translation doesn't exist yethttp://forge.typo3.org/issues/929062020-11-23T13:52:03ZSebastian Michaelsenmichaelsen@t3seo.de
<p>In the backend form of sys_file_reference inline records, typically there's a link where you can edit the metadata of the selected file.</p>
<p>Since the fix for <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: \TYPO3\CMS\Backend\Form\Container\InlineRecordContainer::renderForeignRecordHeaderControl wrong e... (Closed)" href="http://forge.typo3.org/issues/82178">#82178</a> this link is removed if there is not sys_file_metadata record in the same language as sys_file_reference record.</p>
<p>However obviously editors want to edit metdata for files which have not been explicitly localized before. So I suggest that sys_file_metadata translations are created on demand in this situation.</p> TYPO3 Core - Bug #89192 (Accepted): TypoScript multi-line value syntax in is broken in Backend La...http://forge.typo3.org/issues/891922019-09-17T18:06:42ZSebastian Michaelsenmichaelsen@t3seo.de
<p>Consider the following Backend Layout:</p>
<pre><code class="text syntaxhl" data-language="text">mod.web_layout.BackendLayouts.infoPage {
title = Info Page
config.backend_layout {
colCount = 1
rowCount = 1
rows {
1.columns.1 {
name = Content Area
colPos = 0
allowed.CType (
gridelements_pi1,
list,
shortcut,
text,
)
}
}
}
}
</code></pre>
<p>The multi-line value for allowed.CType is perfectly valid and correctly parsed by TYPO3. However <code>\TYPO3\CMS\Backend\Provider\PageTsBackendLayoutDataProvider->generateBackendLayoutFromTsConfig</code> tries to reconstruct the original TSconfig from the parsed array and assumes all values are one-line values with <code>=</code> syntax.</p>
<p>The reconstructed TSconfig then looks like this (in Xdebug)</p>
<pre><code class="text syntaxhl" data-language="text">backend_layout.colCount = 1
backend_layout.rowCount = 1
backend_layout.rows.1.columns.1.name = Content Area
backend_layout.rows.1.columns.1.colPos = 0
backend_layout.rows.1.columns.1.allowed.CType = gridelements_pi1,
list,
shortcut,
text
</code></pre>
<p>Resulting in only <code>gridelements_pi1</code> to be allowed.</p>
<p>A possible solution could be to strip all line breaks while reconstructing the TSconfig.</p>
<p>Workaround: Do not use the multi-line value syntax in Backend Layouts.</p>
<p>This affects at least TYPO3 8 to 10.</p> TYPO3 Core - Bug #82784 (Accepted): DataHandler: copyRecords doesn't set sorting correctly for ne...http://forge.typo3.org/issues/827842017-10-17T15:52:35ZSebastian Michaelsenmichaelsen@t3seo.de
<p>In <code>DataHandler->copyRecord()</code> accepts a <code>$destPid</code> which (according to the phpDoc) can either contain a page id or (indicated by a negative number) a content uid after which the source record is copied to. This "convention" is also used in <code>DataHandler->moveRecord()</code>.</p>
<p>However <code>DataHandler->copyRecord()</code> does not implement the functionality. Only <code>DataHandler->moveRecord()</code> does.</p>
<p>How to reproduce:</p>
<pre>
$dataHandler = GeneralUtility::makeInstance(DataHandler::class);
$data = [
'tt_content' => [
$sourceContentUid=> [
'copy' => ($targetContentUid * -1),
],
],
];
$dataHandler->start([], $data);
$dataHandler->process_cmdmap();
</pre>
<p>The copied element will just receive the sorting value of the source element instead of being sorted after the target content element.</p> TYPO3 Core - Bug #75904 (Closed): Category Model has icon property but no database fieldhttp://forge.typo3.org/issues/759042016-04-25T11:36:39ZSebastian Michaelsenmichaelsen@t3seo.de
<p><code>\TYPO3\CMS\Extbase\Domain\Model\Category</code> has a property <code>$icon</code> without a corresponding database field. Therefore it's not usable at the moment.</p>
<p>So either the property should be removed or the database field should be added.</p>
<p>My personal experience is that this property would definitely be useful and the database field should be added.</p>
<p>Is that possible as a backport for 7 or only for master?</p> TYPO3 Core - Bug #44537 (Closed): BackendUtility::displayWarningMessages uses wrong returnUrlhttp://forge.typo3.org/issues/445372013-01-15T14:26:18ZSebastian Michaelsenmichaelsen@t3seo.de
Steps to reproduce:
<ul>
<li>create a user with the following credentials: admin/password (you're encouraged not to do so on a live system ;) )</li>
<li>open the "About Modules" module, which shows a warning about the admin user.</li>
<li>click the link to edit the admin user</li>
<li>close or save/close the form</li>
<li>404</li>
</ul> TYPO3 Core - Bug #43874 (Closed): array_merge_recursive_overrule: __UNSET can't unset array valueshttp://forge.typo3.org/issues/438742012-12-11T11:17:09ZSebastian Michaelsenmichaelsen@t3seo.de
<p>If the $enableUnsetFeature parameter is true, array_merge_recursive_overrule you can unset values from the first array.<br />The phpDoc says:<br /><pre>
* @param boolean $enableUnsetFeature If set, special values "__UNSET" can be used in the second array in order to unset array keys in the resulting array.
</pre><br />But in fact keys are only unset if they don't hold an array value. I see no reason why this should be like this. There should be the possibility to unset array values.</p> TYPO3 Core - Bug #24336 (Closed): <img> Tags are rendered with border attribute in HTML5 modehttp://forge.typo3.org/issues/243362010-12-14T12:13:54ZSebastian Michaelsenmichaelsen@t3seo.de
<p>By default <img> Tags are rendered with a border attribute in HTML5. Only with XHTML they are omitted.<br />This is a bug. in HTML5 the border attribute is not allowed.</p>
<p>You can disable the border attribute by using config.disableImgBorderAttr = 1, but it should be disabled by default when using html5 to produce valid code.<br />(issue imported from #M16740)</p> TYPO3 Core - Bug #22393 (Closed): Choose proper variable namings in tslib_cObj::getGlobal()http://forge.typo3.org/issues/223932010-04-07T12:29:03ZSebastian Michaelsenmichaelsen@t3seo.de
<p>tslib_cObj::getGlobal() uses variable names like $c, $k, $a, $var, $vars etc</p>
<p>When working on <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Simplify the code to get nested GET Parameters with TS (Closed)" href="http://forge.typo3.org/issues/22392">#22392</a> and another patch (not yet registered in bugtracker) I struggled to find out how getGlobal() actually works. Proper naming of variables would be helpful.<br />(issue imported from #M14023)</p> TYPO3 Core - Bug #22340 (Closed): Automatically hiding Option Checkboxes and search fields on "em...http://forge.typo3.org/issues/223402010-03-29T13:54:44ZSebastian Michaelsenmichaelsen@t3seo.de
<p>When you open a page in list view which has no records to display, it still shows up Checkboxes for "Extended View" and "Localization view" and a search form.<br />The functionality to hide these automatically is implemented but does not work anymore.</p>
<p>After computing the list of tables the list module checks if it has any output. If it's empty Checkboxes and searchform are hidden.</p>
<p>The problem ist that the "list of tables" output is never empty because t3lib_recordlist::writeBottom adds some Hardcoded HTML to the bottom of the table list.</p>
<p>Additionally note that rendering of the clipboard is inside the mentioned condition, so when no records are there the clipboard would also be hidden (you don't want that because you may want to paste records into an empty page). So the Clipboard rendering needs to be moved outside the if-statement<br />(issue imported from #M13942)</p>