TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-05T13:33:40ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103048 (Resolved): "this.createRenderRoot is not a function" JavaScript error i...http://forge.typo3.org/issues/1030482024-02-05T13:33:40ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Given that:<br />I am in the TYPO3 backend<br />And I open the install tool Update module<br />And trigger the "Check for Broken Extensions" or "Check TCA in ext_tables.php" I receive the following JS error within console.</p>
<p>It works fine within standalone version of the install tool. Also works fine in v12.<br />I only tested with released 13.0.0 via composer install, didn't check main.</p> TYPO3 Core - Bug #100468 (Needs Feedback): Missing assets folder when creating public folder aft...http://forge.typo3.org/issues/1004682023-04-05T13:17:01ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Given that:</p>
<ol>
<li>I've created a TYPO3 extension as composer package</li>
<li>That extension does not have a Public/ folder yet</li>
<li>The extension is installed</li>
<li>A new Public/ folder is created within that extension</li>
<li>The folder does not show up within _assets/ folder</li>
</ol>
<p>That might happen during setting up an extension, e.g. a sitepackage.</p>
<p>Workaround:</p>
<ol>
<li><code>composer dumpautoload</code> after the Resources/Public folders are added</li>
</ol>
<p>Maybe we can ease that somehow? Provide a command or maybe "fix" that by a proper 404 handling within TYPO3 itself? I fear that many people will run into that issue when starting with v12.</p> TYPO3 Core - Bug #99401 (Closed): #1381512761 TYPO3\CMS\Core\Type\Exception\InvalidEnumerationVal...http://forge.typo3.org/issues/994012022-12-21T08:14:12ZDaniel Siepmanncoding@daniel-siepmann.de
<p>This happened after updating from 11 LTS to 12.1.3.</p>
Steps to reproduce:
<ul>
<li>Have an database with pages having t3ver_state -1.</li>
<li>Switch to a workspace</li>
<li>Open Page module (Page Tree)</li>
</ul>
<p>The exception happens within the Page Tree Ajax request and is not visible within the backend. Only a red notification will be shown.</p>
<p>A workaround that seems to work is to execute:</p>
<pre><code class="sql syntaxhl" data-language="sql"><span class="k">update</span> <span class="n">pages</span> <span class="k">set</span> <span class="n">deleted</span> <span class="o">=</span> <span class="mi">1</span> <span class="k">where</span> <span class="n">t3ver_state</span> <span class="o">=</span> <span class="o">-</span><span class="mi">1</span><span class="p">;</span>
</code></pre>
<p>I had the pages twice, with -1 and 1.</p> TYPO3 Core - Bug #98337 (Closed): Undefined array key "_CURRENT_VERSION" in WorkspaceVersionReco...http://forge.typo3.org/issues/983372022-09-13T03:09:27ZDaniel Siepmanncoding@daniel-siepmann.de
<p>After updating from PHP 7.4 to 8.0 my cronjob throws this exception when calling scheduler task:</p>
<pre>
[WARNING] PHP Warning: Undefined array key "_CURRENT_VERSION" in
/typo3/sysext/workspaces/Classes/Command/WorkspaceVersionRecordsCommand.php line 304
</pre>
<p>After debugging the mentions line 304, I found the cause in a condition, which is not PHP 8 compatible, because the array key doesn't exists in some cases:</p>
<pre>
if (!$verRec['_CURRENT_VERSION']) {
</pre>
<p>To fix this issue it can just be changed to the following, since the value of this key can only be "true" or not set (see previous BackendUtility::selectVersionsOfRecord method):</p>
<pre>
if (!isset($verRec['_CURRENT_VERSION'])) {
</pre> TYPO3 Core - Bug #95078 (Closed): TypeError in MoveElementController when using sqlitehttp://forge.typo3.org/issues/950782021-09-02T11:57:56ZDaniel Siepmanncoding@daniel-siepmann.de
Steps to reproduce:
<ol>
<li>Use SQLite</li>
<li>Go to List Module</li>
<li>Click on "…" Button to open further actions</li>
<li>Click on "Display change history / Un-do"</li>
</ol>
<p>An PHP TypeError is thrown:<br /><pre>
(1/1) TypeError
Typed property TYPO3\CMS\Backend\Controller\ContentElement\MoveElementController::$page_id must be int, string used
typo3/sysext/backend/Classes/Controller/ContentElement/MoveElementController.php line 114
$assigns['makeCopyChecked'] = (bool)$this->makeCopy;
$assigns['makeCopyUrl'] = GeneralUtility::linkThisScript(['makeCopy' => !$this->makeCopy]);
// Get page record (if accessible):
if ($this->table !== 'pages' && $this->moveUid === $this->page_id) {
$this->page_id = $elRow['pid'];
}
$pageInfo = BackendUtility::readPageAccess($this->page_id, $this->perms_clause);
$assigns['pageInfo'] = $pageInfo;
if (is_array($pageInfo) && $backendUser->isInWebMount($pageInfo['pid'], $this->perms_clause)) {
</pre></p> TYPO3 Core - Bug #94710 (Under Review): Database Compare "Change fields" with SQLite shows red errorhttp://forge.typo3.org/issues/947102021-08-04T12:13:45ZDaniel Siepmanncoding@daniel-siepmann.de
<p>It doesn't work at all due to <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: TypeError for SQLite in DB Compare (Closed)" href="http://forge.typo3.org/issues/94709">#94709</a>. This can be easily hotfixed.</p>
<p>I remember there was some change back during v10 to fix the behaviour to allow:</p>
<ol>
<li>select all</li>
<li>execute</li>
</ol>
<p>And repeat as often as necessary.</p>
<p>That still works but it might result in red errors which is highly user unfriendly. Also we might add an explanation how the process works? That one should just keep executing migrations (when on sqlite)</p> TYPO3 Core - Bug #93009 (Closed): TypeError for page which was created in workspace and is hidde...http://forge.typo3.org/issues/930092020-12-07T08:50:12ZDaniel Siepmanncoding@daniel-siepmann.de
<ol>
<li>Create a new page within a Workspace.</li>
<li>Keep this new page hidden.</li>
<li>Call getTreeList() on ContentObjectRenderer to include this page.</li>
</ol>
<p>A TypeError should be raised due to the fact, that the overlay will convert $row to false as it is hidden. Later on this $row is passed in expectation it still is an array.</p>
<p>This happens if a sitemap is created via EXT:seo. Open it in preview for a workspace that includes a hidden or deleted page (deleted or hidden within the workspace).</p> TYPO3 Core - Bug #92761 (Closed): TypeError in Wizard TableController if db contains nullhttp://forge.typo3.org/issues/927612020-11-03T15:33:09ZDaniel Siepmanncoding@daniel-siepmann.de
<p>A TypeError might occur when using the TableController as wizard for an input field in TCA.<br />Given the following configuration for TCA field:<br /><pre>
'example_field' => [
'exclude' => true,
'label' => 'example field for table wizard',
'config' => [
'default' => '',
'type' => 'text',
'renderType' => 'textTable',
'cols' => 80,
'rows' => 15,
'wrap' => 'off',
],
],
</pre></p>
<p>And the following ext_tables.sql:<br /><pre>
example_field mediumtext,
</pre></p>
<p>That will result in:<br /><pre>
(1/1) TypeError
Argument 1 passed to TYPO3\CMS\Backend\Controller\Wizard\TableController::configurationStringToArray() must be of the type string, null given, called in /typo3/sysext/backend/Classes/Controller/Wizard/TableController.php on line 316
</pre></p>
<p>As the called method requires a string, but null is passed from db query result.</p>
<p>The code is the same for 9, 10 and master, the issue should exist in all three versions. We've encountered the issue in v10 LTS.</p> TYPO3 Core - Bug #90969 (Closed): Administration log broken due to unsupported type annotationhttp://forge.typo3.org/issues/909692020-04-07T12:27:54ZDaniel Siepmanncoding@daniel-siepmann.de
<p><a class="external" href="https://github.com/TYPO3/TYPO3.CMS/commit/555e116f405295edf63394b647d680a9d46de0f7">https://github.com/TYPO3/TYPO3.CMS/commit/555e116f405295edf63394b647d680a9d46de0f7</a> adjusted the type annotation for two properties in the model.<br />These are not supported by extbase and result in the following error:</p>
<blockquote>
<p>(1/1) #1579965021 TYPO3\CMS\Extbase\Persistence\Generic\Mapper\Exception\UnknownPropertyTypeException<br />The type of property TYPO3\CMS\Belog\Domain\Model\LogEntry::tableName could not be identified, therefore the desired value (0) cannot be mapped onto it. The type of a class property is usually defined via php doc blocks. Make sure the property has a valid @var tag set which defines the type.</p>
</blockquote> TYPO3 Core - Feature #90514 (Closed): Dashboard displaying top most executed redirectshttp://forge.typo3.org/issues/905142020-02-24T08:17:59ZDaniel Siepmanncoding@daniel-siepmann.de
<p>TYPO3 allows to toggle counting of triggered redirects.<br />A widget displaying the top most redirects (doughnut graph) would allow people to decide to replace redirects. E.g. if you copied old content into an "archive" section, you might want to migrate that old content if there are a lot of redirects.</p>
<p>If you think that one should not go into TYPO3 core, that would also be ok. But that one would also combine multiple features and make them more accessible.</p> TYPO3 Core - Bug #90219 (Closed): "Database name not valid" with sqlite and long path namehttp://forge.typo3.org/issues/902192020-01-27T17:21:34ZDaniel Siepmanncoding@daniel-siepmann.de
<p>I receive the following issue with my current local Setup:</p>
<blockquote>
<p>Database name not valid<br />Given database name must be shorter than fifty characters and consist solely of basic latin letters (a-z), digits (0-9), dollar signs ($) and underscores (_).</p>
</blockquote>
<p>The setup uses current TYPO3 Master (as of writing), via composer using sqlite as configured database.<br />The error is shown in "Environment Status".</p>
<p>I would guess the issue is set in <em>typo3/sysext/install/Classes/SystemEnvironment/DatabaseCheck/Platform/AbstractPlatform.php</em> and there should be a special handling for sqlite which doesn't limit to 50 characters for the sqlite file path?</p>
<p>With this bug in place, it's very hard to get a clean system report (which also executes the environment check).<br />Leading to spam like this:</p>
<blockquote>
Issues: <br />[ERR] System environment check - 1 Test(s)
<ol>
<li>Database name not valid: 2</li>
</ol>
</blockquote> TYPO3 Core - Bug #89583 (Closed): 2nd double Quote in error messagehttp://forge.typo3.org/issues/895832019-11-05T09:54:04ZDaniel Siepmanncoding@daniel-siepmann.de
<p>There is a 2nd double quote in exception 1436717266, which might lead to confusion whether it is part of the dynamic value within the exception.</p> TYPO3 Core - Task #89519 (Closed): Add missing dependencies to composer.json of extbasehttp://forge.typo3.org/issues/895192019-10-26T09:37:15ZDaniel Siepmanncoding@daniel-siepmann.de
<p>In order to allow proper static code analysis and proper documentation of dependencies.</p> TYPO3 Core - Bug #89432 (Closed): Fix Extbase redirect param type annotationhttp://forge.typo3.org/issues/894322019-10-16T15:33:20ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Right now the method accepts strings and nulls for some arguments, but only string is defined within PHPDoc.</p>
<p>This prevents static code analysis for further code using this method, e.g. inside extensions.</p> TYPO3 Core - Task #89409 (Closed): Fix Extbase getArgument return type annotationhttp://forge.typo3.org/issues/894092019-10-14T13:32:50ZDaniel Siepmanncoding@daniel-siepmann.de
<p>Right now the method can return whatever an argument is, but only string is defined within PHPDoc. E.g. arguments can be an array instead.</p>
<p>This prevents static code analysis for further code using this method, e.g. inside extensions.</p>