TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-08-09T17:07:24ZTYPO3 Forge
Redmine 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 - 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 - Feature #53685 (Closed): Add edit icons to Backend User "Compare" viewhttp://forge.typo3.org/issues/536852013-11-15T22:14:24ZErnesto Baschnyeb@cron.eu
<p>The Backend Users "Compare" view lack some sort of "action buttons".</p>
<p>UX team noted that here:</p>
<p><a class="external" href="https://projects.invisionapp.com/share/H2IU7YVE#/screens/481308/10259907/comments/6169317">https://projects.invisionapp.com/share/H2IU7YVE#/screens/481308/10259907/comments/6169317</a></p>
<p>An improvement would be to have "Edit User" pen icons on the header row besides the usernames to be able to edit them directly from here if desired.</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 - Feature #24850 (Rejected): After the last Upgrade Wizard, a link to "COMPARE" should...http://forge.typo3.org/issues/248502011-01-27T11:27:34ZErnesto Baschnyeb@cron.eu
<p>After the last Upgrade Wizard is through, we should present a last Next button which links to the "COMPARE" screen.</p>
<p>This could even be integrated in a standalone "Wizard" so that the DB compare is done cleanly in the Upgrade Wizard path, so that after that the user is presented with a "Congratulation" message and some other nice words.</p>
<p>(issue imported from #M17354)</p> TYPO3 Core - Bug #23799 (Closed): Add IfModule mod_rewrite.c to misc/advanced.htaccesshttp://forge.typo3.org/issues/237992010-10-20T09:42:15ZErnesto Baschnyeb@cron.eu
<p>The introduction package creates its own .htaccess file which contains <IfModule mod_rewrite.c>.</p>
<p>I would like to have that IfModule in misc/advanced.htaccess so that the introduction package could ship with our misc/advanced.htaccess, instead of creating its own .htaccess file.</p>
<p>The usage of misc/advanced.htaccess will be then added to the intro-package packaging script.</p>
<p>I would like to commit this also for 4.4, so that we can also use this in the 4.4 introduction packaging script.<br />(issue imported from #M16075)</p> TYPO3 Core - Bug #23798 (Closed): Add new API t3lib_befunc::helpTextArray and use it in the ExtDi...http://forge.typo3.org/issues/237982010-10-20T09:30:50ZErnesto Baschnyeb@cron.eu
<p>Currently the ExtDirect which fetches the tooltip fetches the information on its own from the $TCA_DESCR array. It will also render "TYPO3 Inline Help" as a default header if none is given and will not render an "arrow" which used to symbolize a link to a popup in its content.</p>
<p>This patch adds a new API function t3lib_befunc::helpTextArray which is then used by t3lib_befunc::helpText and also the new ExtDirect call to fetch the information. The tooltips now won't have a title anymore if there is no "alttitle" defined.</p>
<p>Almost none CSH uses "alttile", so usually you won't see any. There are some examples in the Extension manager (e.g. the main titles "Loaded Extensions" etc).<br />(issue imported from #M16074)</p> TYPO3 Core - Bug #22235 (Closed): "Show" clickmenu in page tree generates wrong URLhttp://forge.typo3.org/issues/222352010-03-04T09:19:32ZErnesto Baschnyeb@cron.eu
<p>If we don't have any sys_domain record in our page tree, the clickmenu "Show" will generate a link like:</p>
<p><a class="external" href="http://example.com//index.php?id=xx">http://example.com//index.php?id=xx</a></p>
<p>Note the double "//" before index.php. This won't work if you have realurl installed (it doesn't even need to be enabled for your site):</p>
<p>"Error!</p>
<p>Reason: "index.php" could not be found, closest page matching is<br />"</p>
<p>(issue imported from #M13740)</p> TYPO3 Core - Bug #22234 (Closed): "Show" clickmenu in page tree does not work for mount pageshttp://forge.typo3.org/issues/222342010-03-04T09:08:14ZErnesto Baschnyeb@cron.eu
<p>Clicking the "Show" on a page which is a mount point to somewhere else brings the error:</p>
<p>"The requested page didn't have a proper connection to the tree-root! (Illegal Mount Point found in rootline)"</p>
<p>(issue imported from #M13739)</p> TYPO3 Core - Bug #15989 (Closed): Alignment of text in Text w/ images and "nowrap" is wrong (FF)http://forge.typo3.org/issues/159892006-04-05T16:38:32ZErnesto Baschnyeb@cron.eu
<p>In RC3, creating an content element of type "Text with images" and setting the position of images to be "in text, left" or "in text, right" (NOWRAP!), the text is misaligned if its longer than the image-block height. Right after the image-block ends, the text flows 10px to the left (or right) in the default setup (or "x"px, if the textMargin constant was changed).</p>
<p>This seem to be the problem reported by Franz Koch in the Content Rendering Group.</p>
<p>Please check the attached patch if the problems were solved, Franz Koch. If there are any other problems that aren's solved by this patch, please give more feedback on steps to reproduce the problem.<br />(issue imported from #M3138)</p>