TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-07-25T18:53:46ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101443 (Closed): Exception 'Undefined array key "pid"' after moving content in ...http://forge.typo3.org/issues/1014432023-07-25T18:53:46ZErnesto Baschnyeb@cron.eu
<a name="Preconditions"></a>
<h2 >Preconditions:<a href="#Preconditions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Any TYPO3 v11 (or later) installation</li>
<li>PHP 8.x</li>
<li>Workspaces extension enabled</li>
<li>no further extensions or configuration required</li>
</ul>
<a name="How-to-reproduce"></a>
<h2 >How to reproduce:<a href="#How-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>Create a Workspace</li>
<li>Create a page</li>
<li>Add two content elements (in LIVE mode)</li>
<li>Switch to the workspace</li>
<li>Drag & drop the first element after the second element - page will be marked as "modified" in the page tree</li>
<li>Try to add a new content element between or after these elements</li>
</ul>
<p>You get this exception:</p>
<pre><code>PHP Warning: Undefined array key "pid" in /app/packages/typo3/typo3/sysext/backend/Classes/Utility/BackendUtility.php line 3445</code></pre>
<a name="Background"></a>
<h2 >Background<a href="#Background" class="wiki-anchor">¶</a></h2>
<p>This bug was introduced with <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/65797">https://review.typo3.org/c/Packages/TYPO3.CMS/+/65797</a></p>
<p>A potential workaround is to add the "pid" field to the list of `BackendUtilities::getCommonSelectFields` (see attached patch, which we will deploy in production to our customer to get around the problem for now). But maybe this is just hiding the real "problem". The @todos in `BackendUtilities::workspaceOL` give me a vibe that something could be fishy around here.</p> TYPO3 Core - Bug #65646 (Closed): Scheduler misses the "stop" icon when a task is running (6.2 only)http://forge.typo3.org/issues/656462015-03-10T20:21:27ZErnesto Baschnyeb@cron.eu
<p>Since <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Deleted scheduler task groups selectable (Closed)" href="http://forge.typo3.org/issues/63973">#63973</a> was backported to 6.2 the "stop.png" icon is missing when a task is running and therefor a "broken image" appears in the scheduler instead.</p>
<p>The path of the stop.png changed from 6.2 to master and this was not considered in the backport.</p>
<p>Solution is to fix the backport with a follow-up.</p> TYPO3 Core - Bug #57262 (Closed): Install Tool: getFolderStatus ajax also being called in Step In...http://forge.typo3.org/issues/572622014-03-25T01:23:42ZErnesto Baschnyeb@cron.eu
<p>The Ajax calls to getFolderStatus and getEnvironmentStatus are useful to add the badges in the left menu of the Install Tool.</p>
<p>But they are also being fired when the Step Installer is running (no Left Menu).</p>
<p>It would be more stable if we would only fire these ajax calls when the Left Menu is indeed loaded and not regardless of the page you are in.</p> TYPO3 Core - Bug #57257 (Closed): EM: Extracting t3x tries to do a "writeFile" on directorieshttp://forge.typo3.org/issues/572572014-03-24T22:45:29ZErnesto Baschnyeb@cron.eu
<p>If you choose the "Development Preset", E_WARNING will be turned into Exceptions.</p>
<p>If you try to install an extension with this setting, you will end up seeing that when extracting extensions, it tries to use writeFile on directories (and not only files).</p>
<p>Get rid of this by checking if the file ends with an "/" before trying to write to it.</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 #57025 (Closed): Install Tool: "Default File and Directory permissions" should b...http://forge.typo3.org/issues/570252014-03-18T11:29:50ZErnesto Baschnyeb@cron.eu
<p>The recommended setup is still "group writeable" (0660 and 2770), which is why the default permission check will still output is as a notice with this text:</p>
<blockquote>
<p>Currently configured as 0660.. Recommended: 0660. Make sure that your server environment supports this before changing it.</p>
</blockquote>
<p>Change that so that if configured as recommended it is green.</p>
<p>Adds a text in case of group write/readable, that the group the webserver is in should only contain trusted local users.</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 #56951 (Closed): New page wizard broken tree lineshttp://forge.typo3.org/issues/569512014-03-16T02:16:07ZErnesto Baschnyeb@cron.eu
<p>The new page wizard (URL like /typo3/db_new.php?id=xx&pagesOnly=1) looks ugly.</p>
<p>Reas is because there is a mix of new styled t3-tree 30px high tree lines, and not yet reworked "halfline.gif".</p>
<p>Solution would be to include also a higher "halfline.gif" in the new t3-treeline sprite (typo3/sysext/t3skin/images/icons/treeline/) and make use of this new markup in this wizard.</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 #56786 (Closed): Index on sys_file_processedfile is too largehttp://forge.typo3.org/issues/567862014-03-11T20:30:25ZErnesto Baschnyeb@cron.eu
<p>Since <a class="issue tracker-4 status-5 priority-3 priority-lowest closed child" title="Task: Prevent creation of FileObjects for ProcessedFiles (Closed)" href="http://forge.typo3.org/issues/54234">#54234</a> a SQL error in the Upgrade Wizard / Database Compare is left open:</p>
<pre><code>ALTER TABLE sys_file_processedfile ADD KEY identifier (storage,identifier); <br /> Specified key was too long; max key length is 1000 bytes</code></pre>
<p>"identifier" is varchar(512) but on utf8 charset every character needs 3 bytes of space. So the index is "too large" (for MyISAM).</p>
<p>Solution would be to limit the key to the first 332 chars.</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 #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 #42890 (Rejected): Regression: Javascript error in Backend (jumpToUrl)http://forge.typo3.org/issues/428902012-11-12T17:50:56ZErnesto Baschnyeb@cron.eu
<p>All checkboxes in the Backend that contain a "onclick" pointing to "jumpToUrl" seem to be broken in the latest release of TYPO3. The Javascript pops up an error:</p>
<p>Uncaught ReferenceError: Invalid left-hand side in assignment</p>
<p>To test, go to the list module and try to select "Extended View" or "Localization View" from the options beneath the list.</p>
<p>Or in Extension Manager (the old-old one), try to select "Display shy extensions"</p>
<p>Tested on 4.5.x, but should affect also the latest security releases of the other branches as well.</p>