TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-28T09:22:02ZTYPO3 Forge
Redmine TYPO3 Core - Task #103496 (Under Review): Use ISO date format by defaulthttp://forge.typo3.org/issues/1034962024-03-28T09:22:02ZMathias Brodalambrodala@pagemachine.de
<p>The configuration option <code>SYS/ddmmyy</code> is set to <code>d-m-y</code> which has issues:</p>
<p>1. Date display can be ambiguous if a 2-digit year could also be a day in a month, e.g. <em>21-04-23</em> could be <em>2021-04-23</em> or <em>2023-04-21</em><br />2. Date display can be unclear for dates in a different century, e.g. <em>21-04-71</em> could be <em>2071-04-21</em> or <em>1971-04-21</em><br />3. The current format is kind-of-German where <code>d.m.y</code> or <code>d.m.Y</code> would be used. Given that TYPO3 targets an internal audience, a bias like this should be removed.</p>
<p>For these reasons the usual ISO date format <code>Y-m-d</code> should be used by default to solve these issues.</p>
<p>Also see <a class="external" href="https://en.wikipedia.org/wiki/List_of_date_formats_by_country">https://en.wikipedia.org/wiki/List_of_date_formats_by_country</a> where basically all countries prefer a 4-digit year to avoid the above mentioned ambiguities.</p> TYPO3 Core - Task #93246 (Closed): Check maximum PHP version in entrypointshttp://forge.typo3.org/issues/932462021-01-08T15:01:17ZMathias Brodalambrodala@pagemachine.de
<p>The entrypoints for FE, BE and CLI should not only check for a minimum PHP version but also a maximum PHP version. This reflects the <code>composer.json</code> which contains e.g. <code>"php": "^7.4"</code> and thus disallows installation with PHP 8.x.</p>
<p>However, this can accidentally be bypassed if a local development environment uses PHP 7.4 and a remote server uses PHP 8.0.</p>
<p>For this reason an additional check should be added to all entrypoints as safeguard.</p> TYPO3 Core - Task #89747 (Closed): Allow custom tables in record browserhttp://forge.typo3.org/issues/897472019-11-22T17:35:33ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #89746 (Closed): Make icon for record browser configurablehttp://forge.typo3.org/issues/897462019-11-22T17:34:51ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #89742 (Closed): Deprecate form mixinshttp://forge.typo3.org/issues/897422019-11-22T15:29:30ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-2 status-5 priority-4 priority-default closed child" title="Feature: Restructure ext:form setup files (Closed)" href="http://forge.typo3.org/issues/84221">#84221</a> the form setup has been restructured and inheritances have been resolved. Thus EXT:form does not use its own mixins anymore so they should be deprecated in TYPO3v10 and removed in TYPO3v11.</p> TYPO3 Core - Task #88172 (Rejected): Add scalar/return type hints in CommandMaphttp://forge.typo3.org/issues/881722019-04-18T11:13:08ZMathias Brodalambrodala@pagemachine.de
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Exception on sendToStage with User TsConfig option "options.workspaces.changeStageMode = pages" (Closed)" href="http://forge.typo3.org/issues/87046">#87046</a> was caused by a type mismatch which should be prevented with <code>strict_types</code> and scalar/return type hints.</p> TYPO3 Core - Task #87157 (Closed): TYPO3v8 should declare compatibility with PHP 7.3http://forge.typo3.org/issues/871572018-12-14T09:27:37ZMathias Brodalambrodala@pagemachine.de
<p>PHP 7.3 was released recently and all tests in TYPO3v8 are running just fine with this version, thus we should declare compatibility with PHP 7.3 in TYPO3v8.</p> TYPO3 Core - Task #85620 (Closed): Add hint about missing pages to Site Configuration modulehttp://forge.typo3.org/issues/856202018-07-23T14:46:00ZMathias Brodalambrodala@pagemachine.de
<p>If there are no pages, the Site <em>Configuration</em> module only shows some table headers without any hint, that first at least one page needs to be added through the <em>Page</em> module. There should be a hint similar to the <em>Redirects</em> module.</p> TYPO3 Core - Task #85549 (Closed): Improve message if localization fails due to existing recordhttp://forge.typo3.org/issues/855492018-07-13T15:26:12ZMathias Brodalambrodala@pagemachine.de
<p>Currently when trying translating a record and a translation already exists the following message is shown:</p>
<pre>
Localization failed; There already was a localization for this language of the record!
</pre>
<p>This message should be improved to include the following:</p>
<ul>
<li>Name of the translation table (mostly for <code>pages_language_overlay</code> for TYPO3 < v8)</li>
<li>UID of the translation record found</li>
</ul>
<p>This make it a lot easier to fix the broken translation state and is essential for cases where a record cannot be translated properly because translations of its related records already exist. See <a class="issue tracker-1 status-5 priority-7 priority-highest closed" title="Bug: Localization failed; There already was a localization for this language of the record! (Closed)" href="http://forge.typo3.org/issues/31812">#31812</a> for this.</p> TYPO3 Core - Task #85358 (Rejected): Privately declare deprecated public methods/propertieshttp://forge.typo3.org/issues/853582018-06-23T10:57:48ZMathias Brodalambrodala@pagemachine.de
<p>There are two traits <code>PublicMethodDeprecationTrait</code> and <code>PublicPropertyDeprecationTrait</code>. These require defining a property map which methods/properties should be handled.</p>
<p>To ensure deprecations continue to work even in classes extending these and overwriting the property map the property map must be declared <code>private</code>:</p>
<p><a class="external" href="https://3v4l.org/Ejdue">https://3v4l.org/Ejdue</a></p> TYPO3 Core - Task #85344 (Closed): Use trait for public method access deprecationhttp://forge.typo3.org/issues/853442018-06-22T17:43:56ZMathias Brodalambrodala@pagemachine.de
<p>There are a few locations which use <code>debug_backtrace()</code> to determine whether a method was called internally or by 3rd party.</p>
<p>This should be replaced by the <code>PublicMethodDeprecationTrait</code>.</p> TYPO3 Core - Task #85119 (Closed): Remove tests from subtree split Composer packageshttp://forge.typo3.org/issues/851192018-05-30T16:27:47ZMathias Brodalambrodala@pagemachine.de
<p>All <code>typo3/cms-*</code> subtree split Composer packages contain the <code>Tests</code> directory. These should be excluded from the Composer packages.</p> TYPO3 Core - Task #85034 (Closed): Log message when typolink failshttp://forge.typo3.org/issues/850342018-05-17T15:39:14ZMathias Brodalambrodala@pagemachine.de
<p><code>ContentObjectRenderer::typoLink()</code> catches the <code>UnableToLinkException</code> from link builders and only returns the link text. Additionally the exception details should be logged to simplify debugging.</p> TYPO3 Core - Bug #84580 (Closed): "Stop page tree" icon/label unclearhttp://forge.typo3.org/issues/845802018-04-03T12:24:52ZMathias Brodalambrodala@pagemachine.de
<p>The option <strong>Stop page tree</strong> which can be enabled for any page has an unclear icon/label.</p>
<p>The icon is a very simple red "+" and the label only reads <strong>Stop page tree</strong>. There is no clear indication that this option prevents the page tree to render the subtree of the page where this option was enabled.</p>
<p>A better icon/label/indication could be added here.</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>