TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-11-15T09:10:28ZTYPO3 Forge
Redmine TYPO3 Core - Bug #102374 (Resolved): Missing null check in redirect slug update hookhttp://forge.typo3.org/issues/1023742023-11-15T09:10:28ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Unneeded pseudo-uncertain instanceof usage (Closed)" href="http://forge.typo3.org/issues/102140">#102140</a> various <code>instanceof</code> checks where removed. In case of the <code>DataHandlerSlugUpdateHook</code> of EXT:redirects this check also did ensure that unprocessable items are skipped. This is not the case anymore which can cause an error like this:</p>
<p><a class="external" href="https://github.com/pagemachine/typo3-flat-urls/actions/runs/6874052335/job/18695061932#step:3:476">https://github.com/pagemachine/typo3-flat-urls/actions/runs/6874052335/job/18695061932#step:3:476</a></p>
<blockquote>
<p>Error: Call to a member function withChanged() on null</p>
</blockquote> TYPO3 Core - Bug #94922 (Closed): Missing HTTP status 308 for redirectshttp://forge.typo3.org/issues/949222021-08-18T10:48:59ZMathias Brodalambrodala@pagemachine.de
<p>TYPO3 redirects do not offer the HTTP status code <code>308 Permanent Redirect</code> as counterpart to the <code>307 Temporary Redirect</code> by default. This is essential to provide a modern equivalent to the legacy <code>302 Found</code> status code.</p>
<p>Thus <code>308 Permanent Redirect</code> should be added as status code for redirects.</p> TYPO3 Core - Bug #89720 (Closed): TypoScript import from directory loads all fileshttp://forge.typo3.org/issues/897202019-11-21T10:31:48ZMathias Brodalambrodala@pagemachine.de
<p>The "documentation of the TypoScript <code>@import</code> feature"https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/TypoScriptSyntax/Syntax/Includes.html#includes claims that importing from a directory will automatically only load <code>.typoscript</code> files in that directory:</p>
<pre>
# The filename extension can be omitted and defaults to .typoscript
@import 'EXT:myproject/Configuration/TypoScript/'
</pre>
<p>However, this is not true. If a directory is imported like this, <strong>all</strong> files in that directory are imported as TypoScript and then parsed as such, leading to various errors in the Object Browser / Template Analyzer.</p>
<p>Here <code>fileadmin/form_definitions</code> is imported and a form definition exists in this directory:</p>
<p><img src="http://forge.typo3.org/attachments/download/34716/2019-11-21_10-29.png" alt="" loading="lazy" /></p>
<p>The Template Analyzer then clearly reveals that the form definition has been imported, too:</p>
<p><img src="http://forge.typo3.org/attachments/download/34717/2019-11-21_10-30.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #88806 (Closed): "Test Mail Setup" broken: Too few arguments to function EventDi...http://forge.typo3.org/issues/888062019-07-19T16:29:10ZMathias Brodalambrodala@pagemachine.de
<p>Using <strong>Test Mail Setup</strong> in the <strong>Environment</strong> module currently fails with an error which can be found in the TYPO3 logfile:</p>
<code>
Fri, 19 Jul 2019 16:25:30 +0200 [CRITICAL] request="262570147be62" component="TYPO3.CMS.Core.Error.DebugExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Too few arguments to function TYPO3\CMS\Core\EventDispatcher\EventDispatcher::__construct(), 0 passed in /.../typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 3450 and exactly 1 expected | ArgumentCountError thrown in file /.../typo3/sysext/core/Classes/EventDispatcher/EventDispatcher.php in line 35. Requested URL: http://.../typo3/install.php?install[controller]=environment&install[context]=backend - {"TYPO3_MODE":"BE","exception":{}}
</code>
<p>For some reason dependency injection does not seem to be working properly here.</p> TYPO3 Core - Bug #86917 (Closed): Missing support for options in "Execute console commands" sched...http://forge.typo3.org/issues/869172018-11-13T14:44:14ZMathias Brodalambrodala@pagemachine.de
<p>The <strong>Execute console commands</strong> scheduler task added in <a class="issue tracker-2 status-5 priority-5 priority-high3 closed" title="Feature: Symfony CLI executable via scheduler task (Closed)" href="http://forge.typo3.org/issues/79462">#79462</a> only supports command arguments. Command options (aka "flags") are currently not supported.</p>
<p>These should be supported and rendered as checkboxes to provide a full replacement for the legacy Extbase CommandController task.</p> TYPO3 Core - Bug #86544 (Closed): Installation acceptance tests failhttp://forge.typo3.org/issues/865442018-10-02T15:09:34ZMathias Brodalambrodala@pagemachine.de
<p>The acceptance tests use the introduction package and wait for the text <em>Let us introduce you to TYPO3</em> in the frontend after the installation. This text has been removed with version 4.0.0 of the introduction package, thus all tests need to be updated accordingly to look for a different text.</p> TYPO3 Core - Bug #84973 (Closed): Cannot delete invalid Scheduler taskhttp://forge.typo3.org/issues/849732018-05-11T17:39:24ZMathias Brodalambrodala@pagemachine.de
<p>When trying to delete an invalid Scheduler task (e.g. due to the related code being removed) an error occurs:</p>
<pre>
Fatal error: TYPO3\CMS\Scheduler\Scheduler::isValidTaskObject(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition &quot;<Task>&quot; of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /.../typo3/sysext/scheduler/Classes/Scheduler.php on line 449
</pre> TYPO3 Core - Bug #84580 (Closed): "Stop page tree" icon/label unclearhttp://forge.typo3.org/issues/845802018-04-03T12:24:52ZMathias Brodalambrodala@pagemachine.de
<p>The option <strong>Stop page tree</strong> which can be enabled for any page has an unclear icon/label.</p>
<p>The icon is a very simple red "+" and the label only reads <strong>Stop page tree</strong>. There is no clear indication that this option prevents the page tree to render the subtree of the page where this option was enabled.</p>
<p>A better icon/label/indication could be added here.</p> TYPO3 Core - Bug #83177 (Closed): State not immediately updated after enabling/disabling pagehttp://forge.typo3.org/issues/831772017-11-30T15:07:58ZMathias Brodalambrodala@pagemachine.de
<p>When enabling/disabling pages, the new page tree quickly refreshes but no change is visible. Only explicitly refreshing the tree or TYPO3 backend makes the change visible.</p> TYPO3 Core - Bug #81709 (Closed): Multiple INCLUDE_TYPOSCRIPT extensions with spaces not workinghttp://forge.typo3.org/issues/817092017-06-27T12:18:53ZMathias Brodalambrodala@pagemachine.de
<p>The following TypoScript snippet won't include files with anything but the first file extension:</p>
<pre>
<INCLUDE_TYPOSCRIPT: source="DIR: ./Library" extensions="ts, setupts, tx">
</pre>
<p>The reason is the space after the comma which in the end lets <code>TypoScriptParser::includeDirectory()</code> (more specifically <code>GeneralUtility::getFilesInDir()</code> handle them as "<code>ts</code>", "<code> setupts</code>" and "<code> tx</code>" (mind the leading space).</p>
<p>This should probably cleaned up with <code>GeneralUtility::trimExplode()</code>.</p> TYPO3 Core - Bug #80436 (Closed): Linkhandler record browsing not working with CKEditorhttp://forge.typo3.org/issues/804362017-03-24T18:01:00ZMathias Brodalambrodala@pagemachine.de
<p>Apparently the linkhandler record browsing introduced with <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Integrate linkhandler into core (Closed)" href="http://forge.typo3.org/issues/79626">#79626</a> is not working with CKEditor.</p>
<p>Internally CKEditor always passes <code>tt_content</code> as table in <code>BrowseLinksController::getUrlParameters</code> which in turn prevents record listing due to a check in <code>AbstractDatabaseRecordList::generateList()</code> which disallows tables aside from <code>$this->table</code> filled from <code>$_GET['table']</code>.</p> TYPO3 Core - Bug #79277 (Rejected): Main typo3.org repository check shown in Composer modehttp://forge.typo3.org/issues/792772017-01-11T15:41:17ZMathias Brodalambrodala@pagemachine.de
<p>The check against an outdated typo3.org extension repository is shown in Composer mode which doesn't make sense. It should be skipped in Composer mode.</p> TYPO3 Core - Bug #66834 (Closed): Numeric suffix (0) added to unique fields in workspace recordshttp://forge.typo3.org/issues/668342015-05-07T14:21:17ZMathias Brodalambrodala@pagemachine.de
<p>Upon saving a record outside of the LIVE workspace all fields marked as <code>'eval' => 'unique'</code> have <code>0</code> appended to their value. This suffix can be removed just fine afterwards thus only affects the first creation of a new record version.</p> TYPO3 Core - Bug #65867 (Closed): Ignore typo3/cms package requirementhttp://forge.typo3.org/issues/658672015-03-20T15:05:10ZMathias Brodalambrodala@pagemachine.de
<p>Packages may depend on <code>typo3/cms</code> to refer to the TYPO3 CMS core.</p>
<p>But trying to install such a package in the Extension Manager fails:</p>
<blockquote>
<p>#1382276561: The package "<extension>" depends on "typo3/cms" which is not present in the system.</p>
</blockquote>
<p>This should be fixed until full Composer support is added to the core.</p> TYPO3 Core - Bug #63973 (Closed): Deleted scheduler task groups selectablehttp://forge.typo3.org/issues/639732014-12-18T09:54:46ZMathias Brodalambrodala@pagemachine.de
<p>When adding a new scheduler task the task group selector box also lists already deleted task groups, these should be ignored instead.</p>