TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-06-17T17:35:27ZTYPO3 Forge
Redmine TYPO3 Core - Task #91667 (New): Optimization of workspace information dialoghttp://forge.typo3.org/issues/916672020-06-17T17:35:27ZManuel Selbachmanuel_selbach@yahoo.de
<p>The workspace information dialog shows some information, that could be optimized.</p>
<p>First of all there is the "t3_origuid" shown, which could be dropped IMO.</p>
<p>Furthermore there is the field "Columns" shown with one "translated" and readable column name and one with just a number which might be not that easy to be interpreted by an editor.</p>
<p>Please find both topics in the image:</p>
<p><img src="http://forge.typo3.org/attachments/download/35312/workspace-information-dialog.png" alt="" loading="lazy" /></p> 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 - 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 #87938 (Closed): Avoid superfluous cast and creation of instances DocumentTypeEx...http://forge.typo3.org/issues/879382019-03-16T22:12:38ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the implementation uses multiple cast to integer and multiple instances of DocumentTypeExclusionRestriction are created.</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 - Feature #85369 (New): Proper YAML configuration APIhttp://forge.typo3.org/issues/853692018-06-24T10:04:06ZManuel Selbachmanuel_selbach@yahoo.de
<p>In the core there should be a proper API to register, validate the definition and retrieve the parsed YAML configuration.</p>
<p>Things that should be covered:<br />- register YAML configuration files at one central place<br />- define a definition for YAML files to validate that the configuration provided is correct<br />- proper override / combining / extending of a YAML configuration by registering another file (useful if an extension extends some yaml configuration)</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 - 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 - Bug #79131 (Closed): Wrong type in PageRepository::getDomainStartPage for column fe_...http://forge.typo3.org/issues/791312017-01-02T15:10:32ZManuel Selbachmanuel_selbach@yahoo.de
<p>Use of incorrect type for column fe_group in the method PageRepository::getDomainStartPage.<br />If a DBMS with strict usage of types is used (e.g. Postgres), the method will throw an exception, as the 0 is of type integer and not of type string as the column is defined in the database and thus a comparison will fail.</p> TYPO3 Core - Bug #78925 (Closed): PageLayoutController::renderQuickEdit() will throw exception fo...http://forge.typo3.org/issues/789252016-12-08T23:05:57ZManuel Selbachmanuel_selbach@yahoo.de
<p>If there is an empty page (no content elements on it) the method PageLayoutController::renderQuickEdit() will throw an exception on certain DBMS (depends on it's configuration), as the parameter $this->eRParts<sup><a href="#fn1">1</a></sup> will hold e.g. /new/1 which will be use in the Query as integer to get a sys_history record. As it is a "new" element there couldn't be a history entry at all, so let's skip that Query if the parameter $this->eRParts<sup><a href="#fn1">1</a></sup> can not be interpreted as integer.</p> TYPO3 Core - Task #77817 (Closed): Doctrine: wrong escaping of table fields in schemaMigratorhttp://forge.typo3.org/issues/778172016-09-03T00:33:41ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Task #77812 (Closed): Doctrine: ensure unique index keys for postgreSQLhttp://forge.typo3.org/issues/778122016-09-02T22:45:52ZManuel Selbachmanuel_selbach@yahoo.de
<p>PostgreSQL requires unique index name within the database not only on tables.<br />Creating indexes like parent fails on creation of second table with the same index name.</p>
<p>The issue is visible in the installTool by creating tables after database compare.</p>