TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-03-31T15:40:45ZTYPO3 Forge
Redmine TYPO3 Core - Bug #90911 (Closed): Used package algo26-matthias/idna-convert does not support PHP 7.4http://forge.typo3.org/issues/909112020-03-31T15:40:45ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the package: algo26-matthias/idna-convert in it's current used version does not support PHP 7.4</p> TYPO3 Core - Bug #90223 (Closed): Wrong type hint in install tool typo3/sysext/install/Classes/Sy...http://forge.typo3.org/issues/902232020-01-27T22:36:30ZManuel Selbachmanuel_selbach@yahoo.de
<p>As mentioned in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/63032">https://review.typo3.org/c/Packages/TYPO3.CMS/+/63032</a> a wrong type hint was introduced by the refactoring.</p> TYPO3 Core - Task #89657 (Closed): Update doctrine/dbal requirement to minimum ^2.10http://forge.typo3.org/issues/896572019-11-12T18:51:47ZManuel Selbachmanuel_selbach@yahoo.de
<p>With the change in <a class="external" href="https://forge.typo3.org/issues/89614">https://forge.typo3.org/issues/89614</a> the new class Doctrine\DBAL\Types\Types is used to specify DBAL related types.</p>
<p>With that the minimum requirement has to be raised.</p> TYPO3 Core - Task #89593 (Closed): Update doctrine/dbal to 2.10.0http://forge.typo3.org/issues/895932019-11-06T11:52:36ZManuel Selbachmanuel_selbach@yahoo.de
<p>Due to new releases of doctrine/dbal, those package should be updated as it provides several bugfixes.</p>
<p><a class="external" href="https://github.com/doctrine/dbal/releases/tag/v2.10.0">https://github.com/doctrine/dbal/releases/tag/v2.10.0</a></p> TYPO3 Core - Task #89592 (Closed): Update doctrine/dbalhttp://forge.typo3.org/issues/895922019-11-06T11:38:07ZManuel Selbachmanuel_selbach@yahoo.de
<p>Due to new releases of doctrine/dbal, those packages should be updated.</p>
<p><a class="external" href="https://github.com/doctrine/dbal/releases/tag/v2.10.0">https://github.com/doctrine/dbal/releases/tag/v2.10.0</a></p> TYPO3 Core - Task #88579 (Closed): Update doctrine/dbal to ^2.9http://forge.typo3.org/issues/885792019-06-18T09:44:17ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Bug #88081 (Closed): Timestamp in replace dialog of file list is brokenhttp://forge.typo3.org/issues/880812019-04-04T17:55:10ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the timestamp in the replace dialog of a file shows incorrect information.</p>
<p><img src="http://forge.typo3.org/attachments/download/34223/replace_dialog.png" alt="" loading="lazy" /></p>
<p>This is also valid for version 9.5 LTS and 8.7 LTS.</p>
<p>How to reproduce:</p>
<p>- Upload a file via file module<br />- manipulate the file and drag&drop it to upload it again with the same file name<br />- the replace dialog should show wrong timestamp information</p> TYPO3 Core - Bug #87768 (Closed): Missing language in DocHeader in document edit modehttp://forge.typo3.org/issues/877682019-02-21T21:57:50ZManuel Selbachmanuel_selbach@yahoo.de
<p>If a document e.g. a textmedia element gets edited by a user that has a limited access to some languages, the select in the DocHeader shows the wrong languages, if the language overlay is hidden.</p> TYPO3 Core - Bug #85911 (Closed): Not working "Paste after this record" buttonhttp://forge.typo3.org/issues/859112018-08-20T18:25:13ZManuel Selbachmanuel_selbach@yahoo.de
<p>NOTICE: Parent issue has to be fixed before</p>
<p>In mode "languages" of the page module, the button "Paster after this record" is broken.</p>
<p>How to reproduce:</p>
<p>- Open a page with some content on it in the page module<br />- Choose "Languages" in the top selection<br />- Copy a content element<br />- Paste it somewhere between some content elements with the button "Paste after this record"</p>
<p>Result: The pasted content element will be at the top of all content elements in the specific column.</p>
<p>This needs also to be fixed in TYPO3 8.7</p> TYPO3 Core - Bug #84588 (Closed): Int values for field will be converted to unix timestamp in mod...http://forge.typo3.org/issues/845882018-04-03T18:55:42ZManuel Selbachmanuel_selbach@yahoo.de
<p>With the change in <a class="external" href="https://forge.typo3.org/issues/83675">https://forge.typo3.org/issues/83675</a> every value will be converted into a unix timestamp even if you specify e.g. a UID or PID.</p>
<p>Example:</p>
<p>PID: 5134</p>
<p>This will bring back 99854182152 and the if condition is true in the introduced code:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="k">if</span> <span class="p">(</span><span class="nb">strtotime</span><span class="p">(</span><span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue'</span><span class="p">]))</span> <span class="p">{</span>
<span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue'</span><span class="p">]</span> <span class="o">=</span> <span class="nb">strtotime</span><span class="p">(</span><span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue'</span><span class="p">]);</span>
<span class="k">if</span> <span class="p">(</span><span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue1'</span><span class="p">]</span> <span class="o">&&</span> <span class="nb">strtotime</span><span class="p">(</span><span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue1'</span><span class="p">]))</span> <span class="p">{</span>
<span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue1'</span><span class="p">]</span> <span class="o">=</span> <span class="nb">strtotime</span><span class="p">(</span><span class="nv">$conf</span><span class="p">[</span><span class="s1">'inputValue1'</span><span class="p">]);</span>
<span class="p">}</span>
<span class="p">}</span>
</code></pre> TYPO3 Core - Bug #84071 (Closed): Exception Call to a member function getTreeList() on nullhttp://forge.typo3.org/issues/840712018-02-27T18:15:48ZManuel Selbachmanuel_selbach@yahoo.de
<p>If there is a DataProcessor used in a FLUIDTEMPLATE object which tries to resolve storagePids from the configuration with recursion set,<br />the following exception occurs:</p>
<pre><code class="text syntaxhl" data-language="text">Call to a member function getTreeList() on null
Error thrown in file
typo3/cms/typo3/sysext/extbase/Classes/Configuration/FrontendConfigurationManager.php in line 258.
30 TYPO3\CMS\Extbase\Configuration\FrontendConfigurationManager::getRecursiveStoragePids("-8", 3)
typo3/cms/typo3/sysext/extbase/Classes/Configuration/AbstractConfigurationManager.php:
00198: $frameworkConfiguration['persistence']['storagePid'] = $this->getRecursiveStoragePids(
00199: implode(',', $storagePids),
00200: (int)$frameworkConfiguration['persistence']['recursive']
00201: );
00202: }
</code></pre>
<p>This is, because the running order has changed with this change <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/commit/5c048a4c8017e4d50ab5f2343970a0fd33e4aaed">https://github.com/TYPO3/TYPO3.CMS/commit/5c048a4c8017e4d50ab5f2343970a0fd33e4aaed</a> in TYPO3\CMS\Frontend\ContentObject\FluidTemplateContentObject::render.</p>
<p>If you follow into TYPO3\CMS\Fluid\View\StandaloneView::construct (which was previously executed before the execution of dataProcessors were called) the method TYPO3\CMS\Extbase\Configuration\ConfigurationManager::setContentObject is called.</p>
<p>As this is not valid now, the method TYPO3\CMS\Extbase\Configuration\FrontendConfigurationManager::getRecursiveStoragePids tries to retrieve data from "null" which throws the mentioned exception.</p> TYPO3 Core - Task #80317 (Closed): Deprecate BackendUtility::getRecordRawhttp://forge.typo3.org/issues/803172017-03-17T10:04:10ZManuel Selbachmanuel_selbach@yahoo.de
<p>Since we follow the principel of "prepared statement", the method getRecordRaw will break this behaviour.<br />Within the "where" parameter of the function it is possible to inject malicious code.</p>
<p>Thus we should remove it, as the queryBuilder should be used everywhere in the future<br /> to increase visiblity of which query will be processed at a concrete point of code and to<br /> force the concept of prepared statements.</p> TYPO3 Core - Task #79509 (Closed): Add group feature to functional testshttp://forge.typo3.org/issues/795092017-01-26T20:51:59ZManuel Selbachmanuel_selbach@yahoo.de
<p>To increase the performance of functional tests (as excluded groups would not be processed at all, not even be listed) and to ignore tests for certain DBMS the option "@group" should be used in the annotation of a test.</p>
<p>Example:</p>
<pre>
/**
* @test
*
* @group mysql
*/
public function collectGarbageWorksWithEmptyTableWithMysql()
{
$subject = $this->getSubjectObject(true);
$subject->collectGarbage();
}
</pre>
<p>To exclude a group follow the these examples:</p>
<pre>
// to exclude tests for MySQL
bin/phpunit -c ./components/testing_framework/core/Build/FunctionalTests.xml --exclude-group mysql
// to exclude tests for MySQL and PostgreSQL
bin/phpunit -c ./components/testing_framework/core/Build/FunctionalTests.xml --exclude-group mysql postgresql
</pre> TYPO3 Core - Bug #79447 (Closed): Unify usage of fe_group in tables of TYPO3 corehttp://forge.typo3.org/issues/794472017-01-24T17:29:27ZManuel Selbachmanuel_selbach@yahoo.de
<p>The column "fe_group" is defined as varchar everywhere in the core except in table "sys_collection".<br />This will cause some problems with some DBMS (e.g. PostgreSQL) as the FrontendGroupRestriction::class will generate a query which will e.g. check against empty string.<br />Thus the column "fe_group" should be unified to varchar.</p>
<p>Example:<br />The following tests fail with the column "fe_group" defined as integer: <br />- RecordCollectionRepositoryTest::doesFindByUidReturnAnObjectInFrontendMode<br />- RecordCollectionRepositoryTest::doesFindByUidRespectEnableFieldsInFrontendMode</p> TYPO3 Core - Task #79382 (Closed): Cleanup ActionService::getVersionedIdhttp://forge.typo3.org/issues/793822017-01-18T22:44:15ZManuel Selbachmanuel_selbach@yahoo.de
<p>Within the refactoring process the optional parameter $useDeleteClause was missed<br />to remove from the parameter list of the method, as it is not implemented in the body and<br />not used anywhere in the core.</p>