TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-10-13T16:22:35ZTYPO3 Forge
Redmine TYPO3 Core - Bug #102167 (Resolved): Workspace Module: Icon Overlay not being displayed in table ...http://forge.typo3.org/issues/1021672023-10-13T16:22:35ZErnesto Baschnyeb@cron.eu
<p>Until TYPO3 v11 the table of the workspace module showing the changes made to tables also reflected the status of the page with it's icon.</p>
<p>Since change <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Use native icons for workspaces element (Closed)" href="http://forge.typo3.org/issues/94977">#94977</a>, you only see the icon based on the page type, so it does not reflect anymore any status changes (i.e. from Shortcut to normal page, from hidden to non-hidden, etc).</p>
<p><strong>In TYPO3 v10:</strong><br /><img src="http://forge.typo3.org/attachments/download/38016/workspace-v10.png" loading="lazy" style="width:600px;" alt="" /></p>
<p><strong>Since TYPO3 v11:</strong><br /><img src="http://forge.typo3.org/attachments/download/38017/workspace-v11.png" loading="lazy" style="width:600px;" alt="" /></p> TYPO3 Core - Bug #101640 (Resolved): PHP Warning: Undefined array key "eval" in ...core/Classes/D...http://forge.typo3.org/issues/1016402023-08-09T17:07:24ZErnesto Baschnyeb@cron.eu
<p>In case I have a TCA "slug" field without a "eval" config, PHP 8 will bail out with this exception, for example when moving a page in the backend:</p>
<pre><code>PHP Warning: Undefined array key "eval" in /srv/www/www_dhbw_de/releases/60/private/typo3/sysext/core/Classes/DataHandling/DataHandler.php line 8390</code></pre> TYPO3 Core - Bug #100707 (New): Web>List only applies list_type restriction if this column is sho...http://forge.typo3.org/issues/1007072023-04-21T14:27:30ZErnesto Baschnyeb@cron.eu
<p>The ACL <code>explicit_allowdeny</code> allows to restrict an editor to certain plugin types (field <code>list_type</code>):</p>
<p><img src="http://forge.typo3.org/attachments/download/37635/acl-list-type.png" alt="" loading="lazy" /></p>
<p>If an admin creates a plugin of a certain list_type which is not allowed by the editor, in Web>List module the editor will still see the "controls" which would allow him to edit this content element:</p>
<p><img src="http://forge.typo3.org/attachments/download/37636/web-list-buggy.png" alt="" loading="lazy" /></p>
<p>As soon as the user also shows the column <code>list_type</code>, the permission check works and he does not see the icons anymore:</p>
<p><img src="http://forge.typo3.org/attachments/download/37637/web-list-ok.png" alt="" loading="lazy" /></p>
<p>The bug most probably came from the optimizations done in Web>List in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/68666">https://review.typo3.org/c/Packages/TYPO3.CMS/+/68666</a> - the $row which is passed on to DatabaseRecordList::makeControl and then later to BackendUserAuthentication::recordEditAccessInternals() no longer is the full row, but just a basic version of it + the fields select by the user in the backend. So <code>list_type</code> is missing, and this auth-check is then no longer performed.</p> TYPO3 Core - Bug #57152 (Closed): First Install lists directory errors: confusinghttp://forge.typo3.org/issues/571522014-03-21T15:00:23ZErnesto Baschnyeb@cron.eu
<p>First installation has no directories yet. Even if they could be created there are errors shown to the user. This is ugly!</p> TYPO3 Core - Bug #57126 (Closed): Form Wizard - styling problemhttp://forge.typo3.org/issues/571262014-03-21T00:05:43ZErnesto Baschnyeb@cron.eu
<p>Since unification of UL/OL and changed styling the "raw" UL/OL to the original state (with bullet or number), the Form Wizard displays some these undesired artefacts in the TABs and in the right pane:</p>
<p><img src="http://forge.typo3.org/attachments/download/26283/form-before.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #57008 (Closed): New Installation: Could not acquire lock for ClassLoaderhttp://forge.typo3.org/issues/570082014-03-17T22:25:13ZErnesto Baschnyeb@cron.eu
<p>With the Class Loader Locking patch applied (see <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: PHP Warnings after clearing configuration cache in BE (Closed)" href="http://forge.typo3.org/issues/55099">#55099</a>) when installing a fresh new TYPO3 installation (no typo3temp directory present), I get:</p>
<p>( ! ) Fatal error: Uncaught exception 'RuntimeException' with message 'Could not acquire lock for ClassLoader cache creation.' in /www/sites/typo3-62/html/typo3_src/typo3/sysext/core/Classes/Core/ClassLoader.php on line 704<br />( ! ) RuntimeException: Could not acquire lock for ClassLoader cache creation. in /www/sites/typo3-62/html/typo3_src/typo3/sysext/core/Classes/Core/ClassLoader.php on line 704</p>
<p>This should be handled somehow.</p> TYPO3 Core - Bug #56952 (Closed): Extension checker not working anymore since PackageManagement p...http://forge.typo3.org/issues/569522014-03-16T04:11:20ZErnesto Baschnyeb@cron.eu
<p>Since merging of 64c46b918ef016bdd1d799c5ca06e868d601f692 (Package management performance improvements), TYPO3_LOADED_EXT is no longer an ArrayAccess but a regular array (like pre 6.2). This leaded to an error in the Extension Manager important action "Check Extension", causing an endless loop.</p>
<p>The error in the Ajax requests:</p>
<p>Catchable fatal error: Argument 2 passed to TYPO3\CMS\Install\Controller\Action\Ajax\ExtensionCompatibilityTester::loadExtLocalconfForExtension() must implement interface ArrayAccess, array given</p> TYPO3 Core - Bug #56950 (Closed): Additional margin on top of ExtJS context menushttp://forge.typo3.org/issues/569502014-03-16T02:06:10ZErnesto Baschnyeb@cron.eu
<p>In the page tree, the context menu got an additional wrong top margin due to the removal of the ExtJS normalization (<a class="issue tracker-1 status-5 priority-4 priority-default closed parent" title="Bug: Missing margin/padding on content element fields (Closed)" href="http://forge.typo3.org/issues/56418">#56418</a>).</p> TYPO3 Core - Bug #56554 (Closed): OpCache XCACHE cannot be cleared if xcache.admin.enable_auth is...http://forge.typo3.org/issues/565542014-03-04T21:15:10ZErnesto Baschnyeb@cron.eu
<p>Error:</p>
<pre>
Fatal error: xcache_clear_cache(): xcache.admin.user and/or xcache.admin.pass settings is not configured. Make sure you've modified the correct php ini file for your php used in webserver. in /var/www/git/master/typo3/sysext/core/Classes/Utility/OpcodeCacheUtility.php on line 123
[21:02:00] Christian Kuhn: calling install toll on fresh instance
</pre>
<p>Solution is to check for xcache.admin.enable_auth.</p>
<p>References in other projects:</p>
<p><a class="external" href="https://github.com/owncloud/core/blob/master/lib/private/util.php#L1103">https://github.com/owncloud/core/blob/master/lib/private/util.php#L1103</a><br /><a class="external" href="https://github.com/sugarcrm/sugarcrm_dev/blob/master/include/SugarCache/SugarCache.php#L124">https://github.com/sugarcrm/sugarcrm_dev/blob/master/include/SugarCache/SugarCache.php#L124</a></p>
<p>We then should add a hint in the install tool about this.</p> TYPO3 Core - Task #54883 (Closed): Document that TYPO3 CMS is not compatible with MySQL strict modeshttp://forge.typo3.org/issues/548832014-01-09T18:00:11ZErnesto Baschnyeb@cron.eu
<p>TYPO3 is not currently compatible with MySQL configured with "STRICT_TRANS_TABLES" or "STRICT_ALL_TABLES" enabled.</p>
<p>There are currently several issues with this: <a class="issue tracker-1 status-6 priority-4 priority-default closed child" title="Bug: SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW499d21cdec168) (Rejected)" href="http://forge.typo3.org/issues/20052">#20052</a>, <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Unable to create a page (Closed)" href="http://forge.typo3.org/issues/21212">#21212</a>, <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Unable to login into BE when using MySQL 5+ (Closed)" href="http://forge.typo3.org/issues/15295">#15295</a>, <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: Installer will not create any be_users if unsupported sql_mode is used (Closed)" href="http://forge.typo3.org/issues/18821">#18821</a> and probably many more.</p>
<p>So while this is not solved (if even possible...) we should document how to configure MySQL to avoid this situation, because several "mysql installation documentation" (i.e. on Windows) recommend setting "STRICT_ALL_TABLES" by default.</p> TYPO3 Core - Bug #53975 (Closed): BeLog: Exception when time input fields are emptyhttp://forge.typo3.org/issues/539752013-11-26T11:20:41ZErnesto Baschnyeb@cron.eu
<p>If you go to "Info>Log" or "Admin>Log" and select "Userdefined" time range and then leave one of the input fields (start or stop) empty and click "Set", you end up with this exception:</p>
<p>Exception while property mapping at property path "":PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Belog\Domain\Model\Constraint::setManualDateStop() must be an instance of DateTime, null given, called in .../html/typo3_src/typo3/sysext/extbase/Classes/Reflection/ObjectAccess.php on line 215 and defined in .../html/typo3_src/typo3/sysext/belog/Classes/Domain/Model/Constraint.php line 273</p>
<p>When you are in this situation and go to the module again, even changing the Time Select Box to "Undefined" you still get this error (probably because the empty input fields are hidden but submitted again).</p>
<p>And empty input field in start/stop should remove this specific limit.</p> TYPO3 Core - Task #53745 (Closed): Update README/INSTALL/NEWS file in the Core packagehttp://forge.typo3.org/issues/537452013-11-18T21:18:49ZErnesto Baschnyeb@cron.eu
<p>We need to update the *.txt files that are shipped with the TYPO3 Core.</p>
<p>Considering that we won't have separate "packages" being released (blank, introduction, dummy, government), we should include the README which was previously only shipped with these. Which also makes it easier to maintain as they are more tightly tied to a specific release.</p> TYPO3 Core - Bug #53692 (Closed): Backend background color is limited to height:100%http://forge.typo3.org/issues/536922013-11-16T13:27:25ZErnesto Baschnyeb@cron.eu
<p>In several backend screens where there is need to scroll, the background color stops at 100% height. This can be seen for example in the Login screen (dark gray ends abruptly when scrolling down), the Element browser (gray background) and others.</p>
<p>This is a regression introduced with <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Integrate normalize css reset (Closed)" href="http://forge.typo3.org/issues/47920">#47920</a> (adding the normalizer.css) and needs to be fixed until 6.2 release.</p>
<p>The UX team noted that also: <a class="external" href="https://projects.invisionapp.com/share/H2IU7YVE#/screens/10263303/comments/6159625">https://projects.invisionapp.com/share/H2IU7YVE#/screens/10263303/comments/6159625</a></p> TYPO3 Core - Bug #53684 (Closed): Pagetree Context menu has an unwanted bottom marginhttp://forge.typo3.org/issues/536842013-11-15T22:02:45ZErnesto Baschnyeb@cron.eu
<p>This is how it looks now (since <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: CSS vertical spacing (Closed)" href="http://forge.typo3.org/issues/48540">#48540</a> = "CSS: Default vertical spacing for blocks"):</p>
<p><img src="http://forge.typo3.org/attachments/download/25508/context-menu-before.png" alt="" loading="lazy" /></p>
<p>But it needs to look like this:</p>
<p><img src="http://forge.typo3.org/attachments/download/25509/context-menu-after.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #53683 (Closed): Don't underline the whole preview text in Web>Page content elem...http://forge.typo3.org/issues/536832013-11-15T21:55:21ZErnesto Baschnyeb@cron.eu
<p>Since we underline links in the backend, the Web>Page also renders all preview text inside content element boxes in underline on mouse over, because those are also links (to the edit windows). This is cluttery and ugly. So get rid of the underline of the preview text!</p>
<p>Reported and wished by the UX team.</p>