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 #86966 (Closed): pages_language_overlay do not get the appendix from prependAtCo...http://forge.typo3.org/issues/869662018-11-21T16:23:39ZManuel Selbachmanuel_selbach@yahoo.de
<p>If a page is translated those records are not respected regarding the appendix from the "prependAtCopy" on the "label field" like it is done for pages during the copy process.</p>
<p>In combination of using e.g. realurl this could lead to serious problems, as it will create the same path for the page as for the original page and thus the original page doesn't get shown as there is a conflict regarding the path.</p>
<p><strong>Current behavior</strong></p>
<p>1. copy a page with some translations on<br />2. paste it via the page tree</p>
<p>Result:<br />1. page (default language, table "pages"): title gets the suffix that is written in "prependAtCopy" <br />2. translated pages (table "pages_language_overlay"): title is the same as on the original page</p>
<p><strong>Expected result</strong></p>
<p>Translated pages should also get the "suffix" written in $GLOBALS['TCA']['pages_language_overlay']['ctrl']['prependAtCopy'] during the copy process.</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 - Task #79378 (Closed): Unused code in LocalizationController::process foundhttp://forge.typo3.org/issues/793782017-01-18T21:30:28ZManuel Selbachmanuel_selbach@yahoo.de
<p>Within the method TYPO3\CMS\Backend\Controller\Page\LocalizationController::process unused code was found.<br />Additionally the for loop should be refactored as it counts the array every loop.</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 - Bug #68880 (Closed): Save, save & view, save & close not working in RTE Wizardhttp://forge.typo3.org/issues/688802015-08-09T11:04:46ZManuel Selbachmanuel_selbach@yahoo.de
<p>The button Save, save & view and save & close don´t work in the RTE wizard (Fullscreen Rich Text Editing).</p>
<p>JavaScript error appears:<br /><pre>
Uncaught TypeError: document.getElementsByName(...).submit is not a function
</pre></p>
<pre>
submitForm: function() {
if (TBE_EDITOR.doSaveFieldName) {
document[TBE_EDITOR.formname][TBE_EDITOR.doSaveFieldName].value=1;
}
// Set a short timeout to allow other JS processes to complete, in particular those from
// EXT:backend/Resources/Public/JavaScript/FormEngine.js (reference: http://forge.typo3.org/issues/58755).
// TODO: This should be solved in a better way when this script is refactored.
window.setTimeout(function() {
document.getElementsByName(TBE_EDITOR.formname).submit(); <----------------- here the error appears
}, 10);
},
</pre> TYPO3 Core - Bug #68860 (Closed): SelectImage Eventlistener throws execptionhttp://forge.typo3.org/issues/688602015-08-08T16:02:21ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Task #68814 (Closed): remove of base constant TYPO3_URL_ORGhttp://forge.typo3.org/issues/688142015-08-07T09:49:42ZManuel Selbachmanuel_selbach@yahoo.de
<p>Base constant TYPO3_URL_ORG defined in SystemEnvironmentBuilder::defineBaseConstants() can be removed.<br />It´s only for internal usage only and defined at 2 places in the core.</p>
<p>Use TYPO3_URL_GENERAL instead.</p>