TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-11-23T09:57:29ZTYPO3 Forge
Redmine TYPO3 Core - Feature #96055 (Closed): Let the command "language:update" issue warningshttp://forge.typo3.org/issues/960552021-11-23T09:57:29ZMathias Brodalambrodala@pagemachine.de
<p>Currently the CLI command <code>language:update</code> fails hard if translations could not be fetched. (No matter if for a private extension or a public extension without translations, see <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: CLI command language:update fails due to packages without translation packs (Closed)" href="http://forge.typo3.org/issues/95700">#95700</a>)</p>
<p>It would be useful if these where warnings instead by default since failed translations are updates are usually not that important and low priority.</p>
<p>An optional CLI option could be added to turn these warnings into errors again which would be useful for CI systems.</p> TYPO3 Core - Bug #96054 (Closed): Command "language:update" does not log error on missing transla...http://forge.typo3.org/issues/960542021-11-23T09:53:47ZMathias Brodalambrodala@pagemachine.de
<p>The CLI command <code>language:update</code> invokes <code>LanguagePackService::languagePackDownload()</code> for each active extension. Here a HTTP request is performed on the translation server which can fail with an exception on 404.</p>
<p>The <code>RequestFactory::request()</code> call here should be adjusted to include <a href="https://docs.guzzlephp.org/en/stable/request-options.html#http-errors" class="external"><code>['http_errors' => false]</code></a> to have Guzzle return the 404 response instead of throwing an exception. This would allow for logging this as a regular warning.</p> TYPO3 Core - Bug #96053 (Closed): Command "language:update" succeeds on missing translations but ...http://forge.typo3.org/issues/960532021-11-23T09:50:25ZMathias Brodalambrodala@pagemachine.de
<p>The CLI command <code>language:update</code> is supposed to always fail if translations could not be fetched for an extension. But the behavior is different if <code>--no-progress</code> (or <code>--verbose</code>) is passed.</p>
<p>To reproduce:</p>
<ol>
<li>Install any extension without translations on the TYPO3 translation server (private or public), e.g. <code>container</code></li>
<li>Run <code>language:update</code>: succeeds</li>
<li>Run <code>language:update --no-progress</code>: fails</li>
<li>Run <code>language:update --verbose</code>: fails</li>
</ol>
<p>(Notice that the order of <code>language:update</code> invocations doesn't matter here.)</p> TYPO3 Core - Bug #94816 (Closed): Missing "View" button on pages with doktype > 200http://forge.typo3.org/issues/948162021-08-11T13:17:38ZMathias Brodalambrodala@pagemachine.de
<p>When editing a content element on a page with <code>doktype</code> > 200 the view button will not render this page in the frontend.</p> TYPO3 Core - Bug #94815 (Closed): Cannot link to pages with doktype > 200http://forge.typo3.org/issues/948152021-08-11T13:16:54ZMathias Brodalambrodala@pagemachine.de
<p>Pages with <code>doktype</code> > 200 will be muted in the page tree, just as Sysfolders. Thus you cannot set links to pages with <code>doktype</code> > 200 or content elements on these pages.</p> TYPO3 Core - Bug #94814 (Closed): Cannot use page with doktype > 200 as shortcut targethttp://forge.typo3.org/issues/948142021-08-11T13:16:20ZMathias Brodalambrodala@pagemachine.de
<p>A shortcut to a page with a <code>doktype</code> > 200 does not work in Shortcut Mode <strong>First subpage of selected/current page</strong>.</p>
<p>Subpages of the current page with a @doktypeq > 200 will not be considered and thus not called in the frontend, even if they clearly are the first subpage of the shortcut.</p> TYPO3 Core - Bug #92454 (Closed): Invalid colPos/language UID used in "Languages" view with defLa...http://forge.typo3.org/issues/924542020-09-30T14:25:00ZMathias Brodalambrodala@pagemachine.de
<p>Given the "Languages" view is used in the Page module with <code>mod.web_layout.defLangBinding</code> enabled, when reordering content elements in a custom section (<code>colPos</code> > 0) via drag and drop, invalid values for <code>colPos</code> and <code>sys_language_uid</code> are sent to the backend and eventually the <code>DataHandler</code>:</p>
<pre>
cmd[tt_content][13][move]: -10
data[tt_content][13][colPos]: false
data[tt_content][13][sys_language_uid]: NaN
</pre>
<p>Here <code>13</code> is the UID of the dragged content element and <code>10</code> is the UID of the content element after which the dragged element should be sorted.</p>
<p>This affects sorting to positions anywhere else but the beginning of the section. The "Columns" view is fine however.</p>
<p>This make it impossible to move the record:</p>
<blockquote>
<p>2: SQL error: 'Incorrect integer value: 'false' for column 'colPos' at row 1' (tt_content:13)</p>
</blockquote>
<p>This can be observed in TYPO3v8 and TYPO3v9. Probably also TYPO3v10 with the classic Page module but this cannot be checked ATM due to <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: Page Module: No content elements displayed with mod.web_layout.defLangBinding (Closed)" href="http://forge.typo3.org/issues/90617">#90617</a>.</p> TYPO3 Core - Task #89866 (Closed): Use new Typo3Copyright API everywherehttp://forge.typo3.org/issues/898662019-12-05T17:08:33ZMathias Brodalambrodala@pagemachine.de
<p>After <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Move Copyright information generation out of TYPO3 Backend (Closed)" href="http://forge.typo3.org/issues/89756">#89756</a> there are still some locations which directly use e.g. the <code>TYPO3_copyright_year</code> constant and should be migrated to the <code>Typo3Copyright</code> class.</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 #89481 (Closed): Add security reporting procedure to READMEhttp://forge.typo3.org/issues/894812019-10-23T09:08:10ZMathias Brodalambrodala@pagemachine.de
<p>The current README does not have a single mention how security issues should be reported. This can lead to public reports which violates the <a href="https://en.wikipedia.org/wiki/Responsible_disclosure" class="external">responsible disclosure</a> principle.</p> TYPO3 Core - Bug #89169 (Closed): Redirects indey key too long after source path increasehttp://forge.typo3.org/issues/891692019-09-13T17:00:04ZMathias Brodalambrodala@pagemachine.de
<p>Due to <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: redirects: longer URL strings are stripped in source_path (Closed)" href="http://forge.typo3.org/issues/88336">#88336</a> redirect URLs can now be longer. However, this also affects the <code>index_source</code> index which includes <code>source_host</code> and <code>source_path</code> which now easily extends regular index limits:</p>
<pre>
$ typo3cms d:u -vvv
No schema updates were performed for update types:
"field.add", "field.change", "table.add", "table.change"
The following errors occurred:
+---------------+-------------------------------------------------+-----------------------------+
| Type | SQL Statement | Message |
+---------------+-------------------------------------------------+-----------------------------+
| Change fields | ALTER TABLE `sys_redirect` CHANGE `source_path` | Specified key was too long; |
| | `source_path` VARCHAR(2048) DEFAULT '' NOT NULL | max key length is 3072 |
| | | bytes |
| | | |
+---------------+-------------------------------------------------+-----------------------------+
</pre>
<p>The collation is <code>utf_general_ci</code> for the mentioned fields and table.</p>
<p>After manually dropping the <code>index_source</code> index the change can be applied however:</p>
<pre>
$ typo3cms d:u -vvv
The following database schema updates were performed:
+---------------+-------------------------------------------------+
| Type | SQL Statements |
+---------------+-------------------------------------------------+
| Add fields | CREATE INDEX `index_source` ON `sys_redirect` |
| | (source_host(80), source_path(80)) |
| Change fields | ALTER TABLE `sys_redirect` CHANGE `source_path` |
| | `source_path` VARCHAR(2048) DEFAULT '' NOT NULL |
+---------------+-------------------------------------------------+
</pre> 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 #84462 (Rejected): RSA encryption hook should be moved from EXT:rsaauth to EXT:...http://forge.typo3.org/issues/844622018-03-18T10:08:32ZMathias Brodalambrodala@pagemachine.de
<p>The <code>rsaauth</code> extension currently registers a hook for the <code>felogin</code> extension for RSA encrypted login form submission.</p>
<p>This should be moved to the <code>felogin</code> extension instead.</p> TYPO3 Core - Task #76766 (Rejected): Enable Recycler by defaulthttp://forge.typo3.org/issues/767662016-06-24T09:14:51ZMathias Brodalambrodala@pagemachine.de
<p>One part of a good user experience is the safety of undoing destructive operations. Within TYPO3 this can be achieved for a lot of locations with the Recycler module.</p>
<p>Thus I suggest to enable it by default for new installations.</p>