TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-08-18T10:48:59ZTYPO3 Forge
Redmine 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 - Task #93246 (Closed): Check maximum PHP version in entrypointshttp://forge.typo3.org/issues/932462021-01-08T15:01:17ZMathias Brodalambrodala@pagemachine.de
<p>The entrypoints for FE, BE and CLI should not only check for a minimum PHP version but also a maximum PHP version. This reflects the <code>composer.json</code> which contains e.g. <code>"php": "^7.4"</code> and thus disallows installation with PHP 8.x.</p>
<p>However, this can accidentally be bypassed if a local development environment uses PHP 7.4 and a remote server uses PHP 8.0.</p>
<p>For this reason an additional check should be added to all entrypoints as safeguard.</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 #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 - Feature #82019 (New): Accept array instead of CSV in TCAhttp://forge.typo3.org/issues/820192017-08-01T14:14:26ZMathias Brodalambrodala@pagemachine.de
<p>There are various locations in TCA which require a CSV string of values, e.g. <code>ctrl/searchFields</code> or <code>types/N/showitem</code>.</p>
<p>To make it easer to handle this e.g. in Git one can use a multi-line string or the <code>implode()</code> function to convert an array of strings back to an CSV string.</p>
<p>Arrays of strings should be supported natively here to streamline TCA config.</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 - Task #76673 (Closed): Update PHPUnit to version 5.4http://forge.typo3.org/issues/766732016-06-17T10:49:45ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #74491 (Closed): Add Travis check for file path lengthhttp://forge.typo3.org/issues/744912016-03-08T10:20:22ZMathias Brodalambrodala@pagemachine.de
<p>A check should be added to Travis to check the file path lengths in the core repository.</p>
<p>The <a href="https://review.typo3.org/46357" class="external">limit has been set to 130</a> which reduces the risk of not being able to create all files/directories on Windows hosts when cloning the core/fetching it via Composer as source.</p> TYPO3 Core - Task #69786 (Closed): Remove eval() from BackendUtility testhttp://forge.typo3.org/issues/697862015-09-14T15:08:17ZMathias Brodalambrodala@pagemachine.de
<p>The <code>BackendUtility</code> test uses <code>eval()</code> to create a mocked class at runtime for testing. This should be replaced with a proper fixture.</p> TYPO3 Core - Task #69762 (Closed): Enable color output for unit/functional testshttp://forge.typo3.org/issues/697622015-09-13T17:01:15ZMathias Brodalambrodala@pagemachine.de
<p>It would be nice if the color output of PHPUnit was enabled for unit/functional tests. Both manual as well as automated execution on Travis can handle this just fine.</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 - Feature #61066 (Rejected): Configuration per application contexthttp://forge.typo3.org/issues/610662014-08-19T15:00:14ZMathias Brodalambrodala@pagemachine.de
<p>TYPO3 Flow allows for different configuration per application context (even subcontexts). The same should be supported in CMS, too.</p> TYPO3 Core - Task #56177 (Closed): Windows issues with long CSV file name from commit 2db3d30http://forge.typo3.org/issues/561772014-02-21T11:49:53ZMathias Brodalambrodala@pagemachine.de
<p>The commit 2db3d30 added the following file:</p>
<blockquote>
<p>typo3/sysext/workspaces/Tests/Functional/DataHandling/InlineRelationalRecordEditing/CommaSeparatedValue/DataSet/Assertion/createAndLocalizeParentContentRecordWithHotelAndOfferChildRecordsAndDiscardLocalizedParentRecord.csv</p>
</blockquote>
<p>It seems like this file path is too long for either Windows or Git on Windows. If you pull/merge this commit, the file cannot be created, if you do a clean clone, this file is deleted immediately and cannot be restored.</p>
<p>Suggestion: use a shorter file name.</p>