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 #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 - 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 #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 #83176 (Closed): Cannot move page to the end of the treehttp://forge.typo3.org/issues/831762017-11-30T15:05:48ZMathias Brodalambrodala@pagemachine.de
<p>With the new page tree pages cannot be moved to the end anymore, only between other pages.</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 - 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 - 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 #66411 (Closed): New locking API exceptions too generichttp://forge.typo3.org/issues/664112015-04-14T09:57:35ZMathias Brodalambrodala@pagemachine.de
<p>The new locking API currently only uses <code>RuntimeException</code> to hint at errors during lock acquisition.</p>
<p>While this already has the disadvantage of catching other @RuntimeException@s the issue becomes rather clear with the non-blocking example:</p>
<pre>
try {
$result = $locker->acquire(LockingStrategyInterface::LOCK_CAPABILITY_SHARED | LockingStrategyInterface::LOCK_CAPABILITY_NOBLOCK);
catch (\RuntimeException $e) {
if ($e->getCode() === 1428700748) {
// some process owns the lock, let's do something else meanwhile
}
}
</pre>
<p>This requires knowing about this special case and knowing the magic number here. A dedicated exception would make this clearer.</p> TYPO3 Core - Task #66323 (Closed): Test more edge cases for trimExplodehttp://forge.typo3.org/issues/663232015-04-08T12:32:18ZMathias Brodalambrodala@pagemachine.de
<p>There are a few more edge cases in light of <a class="issue tracker-4 status-5 priority-4 priority-default closed behind-schedule" title="Task: Performance: improve trimExplode 2nd try (Closed)" href="http://forge.typo3.org/issues/66317">#66317</a> which should be tested with the current code base first.</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 #65488 (Closed): TimeTracker not set for eID scriptshttp://forge.typo3.org/issues/654882015-03-03T15:43:45ZMathias Brodalambrodala@pagemachine.de
<p>With the recent request handler refactoring some breaking changes where introduced, among others the global TimeTracker <code>$GLOBALS['TT']</code> not being set for eID scripts anymore:</p>
<pre>
( ! ) Fatal error: Call to a member function push() on null in /var/www/typo3_src/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php on line 1206
Call Stack
# Time Memory Function Location
1 0.0719 240072 {main}( ) .../index.php:0
2 0.0790 639632 TYPO3\CMS\Core\Core\Bootstrap->run( ??? ) .../index.php:33
3 0.1116 2472944 TYPO3\CMS\Frontend\EidRequestHandler->handleRequest( ) .../Bootstrap.php:195
4 0.1249 2482888 require( '/var/www/typo3conf/ext/routing/Classes/Controller/RoutingController.php' ) .../EidRequestHandler.php:61
5 0.2003 2609712 Causal\Routing\Controller\RoutingController->dispatch( ) .../RoutingController.php:332
6 0.2108 2650536 Causal\Routing\Controller\RoutingController->initTSFE( ) .../RoutingController.php:114
7 0.8588 4934936 TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->determineId( ) .../RoutingController.php:314
</pre> 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> 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>