TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-03-21T15:00:23ZTYPO3 Forge
Redmine 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 - 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 - Bug #53940 (Rejected): Extension name is not case insensitive in anymorehttp://forge.typo3.org/issues/539402013-11-25T15:30:01ZErnesto Baschnyeb@cron.eu
<p>The extension "abaticker" for example contains something like:</p>
<pre>
t3lib_extMgm::addPlugin(Array("LLL:EXT:abaTicker/locallang_db.php:tt_content.list_type_pi1", $_EXTKEY."_pi1"),"list_type");
</pre>
<p>In 6.2 this now fails with:</p>
<p>"TYPO3 Fatal Error: Extension key "abaTicker" is NOT loaded" (Exception 1365429656)</p>
<p>So the ExtensionManagementUtil API doesn't seem to be backwards compatible yet (i.e. extPath() etc), as it doesn't seem to expect different CaSe for the passed extension key.</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> TYPO3 Core - Bug #53652 (Closed): New element wizard broken tree lineshttp://forge.typo3.org/issues/536522013-11-15T00:24:08ZErnesto Baschnyeb@cron.eu
<p>In <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="Task: Replace table structure in new element wizard (Closed)" href="http://forge.typo3.org/issues/49603">#49603</a> the html and css of the "new element wizard" was refactored (Web>List, "Create New Record"). This broke the tree lines layout because it added some gaps between the segments.</p>
<p>Before:</p>
<p><img src="http://forge.typo3.org/attachments/download/25500/db_new-tree-orig.png" alt="" loading="lazy" /></p>
<p>Now:</p>
<p><img src="http://forge.typo3.org/attachments/download/25501/db_new-tree-buggy.png" alt="" loading="lazy" /></p>
<p>This needs to be fixed</p> TYPO3 Core - Bug #53075 (Closed): Do not auto-load SC_* classeshttp://forge.typo3.org/issues/530752013-10-23T14:41:55ZErnesto Baschnyeb@cron.eu
<p>The SC_* classes contain runnable code, and thus cannot be "auto-loaded". This was discovered due to crashes in the phpunit tests for 4.7 (by travis).</p>
<p>So fixing this will also fix broken travis.</p> TYPO3 Core - Bug #52812 (Rejected): Installing extension bringes 'Package "xy" is not available'http://forge.typo3.org/issues/528122013-10-14T19:09:26ZErnesto Baschnyeb@cron.eu
<p>If I copy an extension directory to typo3conf/ext/ and try to install it using the Extension Manager (it is listed already), I get:</p>
<pre><code>#1166546734: Package "xy" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive). (More information)</code></pre>
<p>The problem is that the PackageStates file is not up-to-date: it does not include this new package which was just copied there without the knowledge of the Package Management.</p>
<p>Since this is not so uncommon, I would propose to re-create the PackageStates.php file as soon as the Extension Manager tries to do something with packages to make sure it is in sync with the reality - just like it behaved before.</p> TYPO3 Core - Bug #52779 (Closed): Exception if uninstalled extension has "wrong key"http://forge.typo3.org/issues/527792013-10-14T12:01:03ZErnesto Baschnyeb@cron.eu
<p>I know of tons of installations where some <strong>deinstalled</strong> extension in typo3conf/ext/ gets renamed to "tt_news.old" or "news.bak" etc. This was no problem before.</p>
<p>With the new package management feature, this now throws an exception on first hit:</p>
<pre><code>InvalidPackageKeyException('"' . $packageKey . '" is not a valid package key.', 1217959510)</code></pre>
<p>Solution:</p>
<p>The loop that scans for packages should skip those who's key is not invalid, in order to avoid an exception later down the road.</p>