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 #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 - Task #54511 (Closed): Travis increase PHP memory_limit to 1280mhttp://forge.typo3.org/issues/545112013-12-19T13:56:58ZErnesto Baschnyeb@cron.eu
<p>Currently travis is failing due to exploded memory_limit (>1024m). Why it takes so much needs to be investigated and is planned here: <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: phpunit run in Travis: Detect and fix memory leaks (Closed)" href="http://forge.typo3.org/issues/54510">#54510</a></p>
<p>While this is not tackled, we should increase memory_limit for phpunit run a bit so that it at least works again. I.e. to 1280M.</p> TYPO3 Core - Bug #54510 (Closed): phpunit run in Travis: Detect and fix memory leakshttp://forge.typo3.org/issues/545102013-12-19T13:55:22ZErnesto Baschnyeb@cron.eu
<p>Travis with PHP 5.3 is requiring more than 1 GB of RAM in one run since some merge and then the PHP run fails.</p>
<p>Instead of constantly increase the memory_limit when this occurs, we should investigate what exactly takes so much memory and limit that so that the test-run scales better.</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 - Epic #53915 (Closed): Usability and timing issues in Pagetreehttp://forge.typo3.org/issues/539152013-11-25T00:37:06ZErnesto Baschnyeb@cron.eu
<p>The page tree has some problems when it has to deal with long running tasks:</p>
<p>- delete whole tree<br />- copy tree with lots of childs<br />- etc...</p>
<p>This umbrella-issue should try to collect these so that they can be tackled at once.</p> TYPO3 Core - Feature #53666 (Closed): One search box onlyhttp://forge.typo3.org/issues/536662013-11-15T14:39:26ZErnesto Baschnyeb@cron.eu
<p>During the UXW09 it was defined that we only want to end up with one single "search box" (the one at the top right). So the "search" below the List-module should be gone too.</p>
<p>The idea was that the "global search" and the "page specific search" should be done from this central area, and the different search results grouped in separate tabs.</p>
<p>See this screen from back then:</p>
<p><img src="http://forge.typo3.org/attachments/download/25503/typo3-search-global-uxw09.png" alt="" loading="lazy" /></p>
<p>This implementation seem to be missing or gone. Screenshot is grabbed from this page:</p>
<p><a class="external" href="http://forge.typo3.org/projects/usability/wiki/T3UXW09-Team4#The-search-result-list">http://forge.typo3.org/projects/usability/wiki/T3UXW09-Team4#The-search-result-list</a></p>
<p>Maybe you find other interesting details from the concept back then.</p> TYPO3 Core - Bug #51698 (Closed): Delete sys_file entry when a file is deletedhttp://forge.typo3.org/issues/516982013-09-03T22:22:40ZErnesto Baschnyeb@cron.eu
<p>In order to keep sys_file as much in sync with the real file system as possible we should delete the relevant sys_file entry as soon as a file is deleted.</p>
<p>This is part of the "plan" in <a class="issue tracker-4 status-5 priority-4 priority-default closed parent" title="Task: Handling of deleted files in FAL (Closed)" href="http://forge.typo3.org/issues/50876">#50876</a> and should also be backported to 6.0/6.1 to keep the API straight and uniform throughout the releases.</p> TYPO3 Core - Bug #50803 (Closed): Fatal error: "enableFields on non-object" in extension managerhttp://forge.typo3.org/issues/508032013-08-05T22:25:44ZErnesto Baschnyeb@cron.eu
<p>Extbase extensions might fail with:</p>
<p>Fatal error: Call to a member function enableFields() on a non-object in .../typo3_src/typo3/sysext/core/Classes/Resource/StorageRepository.php on line 211</p>
<p>The problem was "uncovered" with the <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Find best-matching local storage instead of default-storage (Closed)" href="http://forge.typo3.org/issues/45498">#45498</a> (the new EM fatals with this error since this patch), but could happen in other situations too.</p>
<p>Reason is that Extbase in certain situations will try to create a dummy simulated "TSFE" object to be able to use cObject stdWrap's in the backend context.</p>
<p>Now this is not a "complete TSFE" and doesn't for example include a proper sys_page property.</p>
<p>So to make sure we are in a proper FE context, we shouldn't rely on "is_object($TSFE)" but instead check if TYPO3_MODE==FE like it is done throughout other places in the core.</p> TYPO3 Core - Bug #30636 (Closed): TCA: subtypes_addlist not being processed if the subtype_value_...http://forge.typo3.org/issues/306362011-10-07T17:32:47ZErnesto Baschnyeb@cron.eu
<a name="How-to-reproduce"></a>
<h2 >How to reproduce:<a href="#How-to-reproduce" class="wiki-anchor">¶</a></h2>
<p>Install mc_googlesitemap in TYPO3 4.5 and wonder where the referred fields from the documentation are: they are not rendered. They are supposed to appear in the content element of type "Menu/Sitemap" when you choose one of the newly introduced Subtypes "Sitemaps for Contents" or "Sitemaps for Pages".</p>
<p><img src="http://forge.typo3.org/attachments/download/19013/subtype_addlist-bug.png" title="Bug in action (extension mc_googlesitemap)" alt="Bug in action (extension mc_googlesitemap)" loading="lazy" /></p>
<a name="Background"></a>
<h2 >Background:<a href="#Background" class="wiki-anchor">¶</a></h2>
<p>Extensions can add fields to an existing table depending on a certain "subtype". E.g. Content Element of type "menu" has subtype stored in "menu_type". Extension mc_googlesitemap wants to add fields depending on the menu_type:</p>
<p>$TCA["tt_content"]["types"]["menu"]["subtype_value_field"]="menu_type";<br />$TCA["tt_content"]["types"]["menu"]["subtypes_addlist"][$_EXTKEY."_pi1"]= ...</p>
<p>This used to work fine since 4.4, but in 4.5 the "menu_type" field is now inside a palette, so the new fields have <strong>no</strong> place to be positioned and so they are not rendered at all.</p>
<a name="Solution"></a>
<h2 >Solution:<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>Go through the palettes too, and add the new fields right after the palette where the field resides in. Now it looks like this:</p>
<p><img src="http://forge.typo3.org/attachments/download/19014/subtype_addlist-correct.png" title="How it looks with the proposed fix" alt="How it looks with the proposed fix" loading="lazy" /></p> TYPO3 Core - Bug #26995 (Closed): Merge CGL changes from 4.5.3http://forge.typo3.org/issues/269952011-05-23T22:11:16ZErnesto Baschnyeb@cron.eu
<p>Hi,</p>
<p>in patchset 4 of <a class="external" href="https://review.typo3.org/2288">https://review.typo3.org/2288</a> I applied CGL fixes to the <strong>new</strong> code that was changed since 4.5.2. Please consider applying that to the external repository's version also (maybe after we move to GIT).</p>
<p>There are other CGL issues in the extension still, but at least I wanted to make sure no new issues are introduced.</p> TYPO3 Core - Bug #13320 (Closed): Don't use cross-extension dependencies (e.g. em)http://forge.typo3.org/issues/133202011-02-24T08:15:08ZErnesto Baschnyeb@cron.eu
<p>Hi,</p>
<p>please apply the following change which was included in typo3_src already:</p>
<p><a class="external" href="http://forge.typo3.org/projects/typo3v4-core/repository/revisions/10615">http://forge.typo3.org/projects/typo3v4-core/repository/revisions/10615</a></p>
<p>We will release 4.5.1a with this fix included and want to make sure that it doesn't happen again.</p>
<p>Thanks!</p> TYPO3 Core - Bug #12079 (Closed): Not possible to reactivate t3editor after deactivationhttp://forge.typo3.org/issues/120792011-01-10T22:21:26ZErnesto Baschnyeb@cron.eu
<p>When I de-select the checkbox "Deactivate t3editor" which is shown below the Info/Modify form of SETUP (or CONSTANT), there is no way of getting it back "active". If I unselect that checkbox again and SAVE, it is again activated as soon as I enter that form again.</p>
<p>This happens on 4.4 and current trunk. Would be cool to have that fixed for the 4.5.0 final release.</p>