TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-06-17T17:35:27ZTYPO3 Forge
Redmine TYPO3 Core - Task #91667 (New): Optimization of workspace information dialoghttp://forge.typo3.org/issues/916672020-06-17T17:35:27ZManuel Selbachmanuel_selbach@yahoo.de
<p>The workspace information dialog shows some information, that could be optimized.</p>
<p>First of all there is the "t3_origuid" shown, which could be dropped IMO.</p>
<p>Furthermore there is the field "Columns" shown with one "translated" and readable column name and one with just a number which might be not that easy to be interpreted by an editor.</p>
<p>Please find both topics in the image:</p>
<p><img src="http://forge.typo3.org/attachments/download/35312/workspace-information-dialog.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #90911 (Closed): Used package algo26-matthias/idna-convert does not support PHP 7.4http://forge.typo3.org/issues/909112020-03-31T15:40:45ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the package: algo26-matthias/idna-convert in it's current used version does not support PHP 7.4</p> TYPO3 Core - Bug #90223 (Closed): Wrong type hint in install tool typo3/sysext/install/Classes/Sy...http://forge.typo3.org/issues/902232020-01-27T22:36:30ZManuel Selbachmanuel_selbach@yahoo.de
<p>As mentioned in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/63032">https://review.typo3.org/c/Packages/TYPO3.CMS/+/63032</a> a wrong type hint was introduced by the refactoring.</p> TYPO3 Core - Task #89794 (Closed): Refactoring the database check in install toolhttp://forge.typo3.org/issues/897942019-11-28T17:41:31ZManuel Selbachmanuel_selbach@yahoo.de
<p>The current state of the check regarding database requirements is not separated properly.<br />Thus I suggest to refactor that to add platform and driver specific specification to have this maintainable.</p> TYPO3 Core - Task #89657 (Closed): Update doctrine/dbal requirement to minimum ^2.10http://forge.typo3.org/issues/896572019-11-12T18:51:47ZManuel Selbachmanuel_selbach@yahoo.de
<p>With the change in <a class="external" href="https://forge.typo3.org/issues/89614">https://forge.typo3.org/issues/89614</a> the new class Doctrine\DBAL\Types\Types is used to specify DBAL related types.</p>
<p>With that the minimum requirement has to be raised.</p> TYPO3 Core - Task #89593 (Closed): Update doctrine/dbal to 2.10.0http://forge.typo3.org/issues/895932019-11-06T11:52:36ZManuel Selbachmanuel_selbach@yahoo.de
<p>Due to new releases of doctrine/dbal, those package should be updated as it provides several bugfixes.</p>
<p><a class="external" href="https://github.com/doctrine/dbal/releases/tag/v2.10.0">https://github.com/doctrine/dbal/releases/tag/v2.10.0</a></p> TYPO3 Core - Bug #85912 (Closed): Button "Paste after this record" or "Paste into this column" is...http://forge.typo3.org/issues/859122018-08-20T18:57:24ZManuel Selbachmanuel_selbach@yahoo.de
<p>If a content element get's copied and tried to insert directly via the buttons defined in the subject, nothing happens.</p>
<p>How to reproduce:</p>
<p>- Open a page in the page module with some content on it<br />- Copy a content element<br />- try to paste it via the button "Paste after this record" or "Paste into this column"</p>
<p>Result:<br />- Nothing happens</p>
<p>This issue seems to be located in the DragDrop.js or in Paste.js</p> TYPO3 Core - Bug #83585 (Closed): "New" page tree broken in Safari Version 11.0.2http://forge.typo3.org/issues/835852018-01-16T19:02:53ZManuel Selbachmanuel_selbach@yahoo.de
<p>The new page tree displays an arrow always, even if there is no subpage or subtree (see screenshot).</p>
<p><strong>Expected:</strong><br />The arrow should only be displayed if there is a subpage or subtree.</p>
<p>Used Safari Version 11.0.2 on macOS High Sierra 10.13.2</p>
<p><strong>Screenshots:</strong></p>
<p><img src="http://forge.typo3.org/attachments/download/33031/Bildschirmfoto2018-01-16-1.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/33032/Bildschirmfoto2018-01-16-2.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #76513 (Rejected): diff-view not working for categories if default changeshttp://forge.typo3.org/issues/765132016-06-08T09:10:41ZManuel Selbachmanuel_selbach@yahoo.de
<p>Hi,</p>
<p>the diff-view of a translated record shows "N/A" if there are changes made to the default language.</p> TYPO3 Core - Task #75463 (Closed): "old fashioned" icons in category treehttp://forge.typo3.org/issues/754632016-04-08T15:07:23ZManuel Selbachmanuel_selbach@yahoo.de
<p>"Old fashioned" icons are used within the category tree in the backend. <br />This is not consistent with the other icons in the backend.</p> TYPO3 Core - Task #69038 (Closed): Move record-related entrypoints to backend routinghttp://forge.typo3.org/issues/690382015-08-14T08:18:01ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Bug #68911 (Closed): Checkbox "Display thumbnails" does not work in filebrowserhttp://forge.typo3.org/issues/689112015-08-10T19:37:51ZManuel Selbachmanuel_selbach@yahoo.de
<p>The checkbox "Display thumbnails" (see screenshot attached) in the file browser throws an Exception:</p>
<p>Invalid request for route "/wizard/record/browse".</p> TYPO3 Core - Task #68881 (Closed): Add backend routes for wizards (part 2)http://forge.typo3.org/issues/688812015-08-09T11:24:31ZManuel Selbachmanuel_selbach@yahoo.de
<p>Move all wizards to the Backend Routing.<br />Do not use the module registration for wizards in ext_tables.php<br />Use Configuration/Backend/Routes.php instead.</p>
<p>Instructions for testing the routings:</p>
<p>colorpicker wizard<br />------------------</p>
<p>To test colorpicker follow these steps:</p>
<p>- install introduction package<br />- create a bootstrap carousel element<br />- create a carousel item<br />- The wizard is located beside the "Text color" field<br />- Open the wizard. The route should now be visible in the location of the wizard window.</p>
<p>BackendLayout wizard<br />--------------------</p>
<p>- create a backend layout record per list view<br />- The wizard is located beside the field "Config" <br />- Open the wizard. The route should now be visible in the location of the wizard window.</p>
<p>Table wizard<br />------------<br />- create a content element of type "Table" <br />- save it<br />- go to tab "Table" <br />- The wizard is located beside the field "Text" <br />- Have a look at the href-attribute of the wizard link. The route should be visible there.</p>
<p>RTE wirzard<br />-----------<br />- create a text element and save it<br />- The wizard is located beside the RTE for field "Text" (Fullscreen Rich Text Editing)<br />- Have a look at the href-attribute of the wizard link. The route should be visible there.</p> TYPO3 Core - Bug #68880 (Closed): Save, save & view, save & close not working in RTE Wizardhttp://forge.typo3.org/issues/688802015-08-09T11:04:46ZManuel Selbachmanuel_selbach@yahoo.de
<p>The button Save, save & view and save & close donĀ“t work in the RTE wizard (Fullscreen Rich Text Editing).</p>
<p>JavaScript error appears:<br /><pre>
Uncaught TypeError: document.getElementsByName(...).submit is not a function
</pre></p>
<pre>
submitForm: function() {
if (TBE_EDITOR.doSaveFieldName) {
document[TBE_EDITOR.formname][TBE_EDITOR.doSaveFieldName].value=1;
}
// Set a short timeout to allow other JS processes to complete, in particular those from
// EXT:backend/Resources/Public/JavaScript/FormEngine.js (reference: http://forge.typo3.org/issues/58755).
// TODO: This should be solved in a better way when this script is refactored.
window.setTimeout(function() {
document.getElementsByName(TBE_EDITOR.formname).submit(); <----------------- here the error appears
}, 10);
},
</pre> TYPO3 Core - Bug #68860 (Closed): SelectImage Eventlistener throws execptionhttp://forge.typo3.org/issues/688602015-08-08T16:02:21ZManuel Selbachmanuel_selbach@yahoo.de