TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-26T13:26:18ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103205 (Under Review): Add hint to EXT:redirects documentationhttp://forge.typo3.org/issues/1032052024-02-26T13:26:18ZPeter Kraumepeter.kraume@gmx.de
<p>The usage of constants in the linkhandler TSConfig doesn't work in the redirects module.<br />It would be useful to add a link to the documentation.</p> TYPO3 Core - Task #102999 (Resolved): Remove obsolete method resolveResourcePaths() from EXT:formhttp://forge.typo3.org/issues/1029992024-01-31T07:58:18ZPeter Kraumepeter.kraume@gmx.de
<p>With <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: file_exists(): open_basedir restriction in effect (Resolved)" href="http://forge.typo3.org/issues/98545">#98545</a> a problem with open_basedir has been fixed. Now it's time to finally remove the obsolete method resolveResourcePaths() because it's no longer used anywhere in the core.</p> TYPO3 Core - Bug #102772 (Resolved): Typo in CSP Modulehttp://forge.typo3.org/issues/1027722024-01-08T08:35:39ZPeter Kraumepeter.kraume@gmx.de
<p>There is a "s" missing in the CSP module description:</p>
<blockquote>
<p>Allows to manage content-security-policy settings.</p>
</blockquote> TYPO3 Core - Bug #102694 (Under Review): Shortcuts do not respect different settings in alternati...http://forge.typo3.org/issues/1026942023-12-19T08:33:43ZPeter Kraumepeter.kraume@gmx.de
<p>The TYPO3 Core does not respect different settings for shortcut target and shortcut mode in alternative languages.</p>
<strong>Szenario:</strong>
<ul>
<li>Setup with multiple languages</li>
<li>Shortcut page with default language and shortcut target page A</li>
<li>Translation of the above mentioned page with target page B</li>
<li>Menu containing the above mentioned shortcut page</li>
</ul>
<p><strong>Current behaviour:</strong><br />TYPO3 tries to link the shortcut page to the shortcut target from the default language. If that page isn't translated, <code>doNotLinkIt = 1</code> is applied to that link and the menu shows only the link text but unlinked.</p>
<p>Attached is a simple demo site (t3d export and site configuration) to reproduce the problem.</p>
<p>All this applies to TYPO3 v11. In v12 the PageRepository was reworked and there I was not able to reproduce the error.</p> TYPO3 Core - Bug #102404 (Resolved): Field scope in sys_csp_resolution is too smallhttp://forge.typo3.org/issues/1024042023-11-19T19:43:28ZPeter Kraumepeter.kraume@gmx.de
<p>In frontend context the field scope in table sys_csp_resolution is filled with a concatenation of "frontend." and the site configuration identifier.<br />When the site identifier is too long, new entries in sys_csp_resolution fail for frontend requests:</p>
<pre>
Uncaught TYPO3 Exception: #1406: An exception occurred while executing a query: Data too long for column 'scope' at row 1
</pre>
<p>This can happen e.g. in a fresh TYPO3 installation where there was no manual site configuration. Then the site identifiert looks like this:<br /><code>autogenerated-1-c4ca4238a0b923820dcc509a6f75849b</code></p>
<p>The scope would then be <code>frontend.autogenerated-1-c4ca4238a0b923820dcc509a6f75849b</code> which is tool long.</p>
<p>To mitigate the problem we need to double the field size at least. This will solve the problem for the above mentioned case.</p>
<p>But since the site identifier has a TCA configuration for max. 255 chars I'd go for varchar(264).</p>
<p>Possible implication: the scope is used in the CSP backend module in a table view. A very long field value might break the design of the table.</p> TYPO3 Core - Bug #99256 (Closed): Little typo in EXT:reactionshttp://forge.typo3.org/issues/992562022-12-02T14:24:45ZPeter Kraumepeter.kraume@gmx.de
<pre>
<trans-unit id="palette.config.description" resname="palette.config.description">
<source>Generel configuration of the reaction.</source>
</trans-unit>
</pre> TYPO3 Core - Bug #98183 (Closed): Typo in several placeshttp://forge.typo3.org/issues/981832022-08-19T16:59:45ZPeter Kraumepeter.kraume@gmx.de
<p>The word "occurred" is missing an "r" in several places:</p>
<p>Build/Sources/TypeScript/backend/clipboard-panel.ts<br />typo3/sysext/backend/Resources/Public/JavaScript/clipboard-panel.js<br />typo3/sysext/install/Classes/Controller/SettingsController.php</p> TYPO3 Core - Bug #93952 (New): Backend Login with new credentials doesn't trigger password safe a...http://forge.typo3.org/issues/939522021-04-20T07:12:31ZPeter Kraumepeter.kraume@gmx.de
<p>Since TYPO3 v11.1 the login to the TYPO3 backend with new credentials or on a new domain doesn't trigger the password safe, e.g. 1Password, anymore to store the new credentials in the password safe.<br />With TYPO3 v10 this still works fine.<br />Interestingly, however, the password safe is triggered when incorrect credentials are entered.</p> TYPO3 Core - Bug #86714 (New): Upgrade Wizard in Install Tool shows HTML tag <warning>http://forge.typo3.org/issues/867142018-10-22T23:43:39ZPeter Kraumepeter.kraume@gmx.de
<p>If a upgrade wizard fails in the Install Tool, this error message is show:</p>
<pre>
Update failed!
<warning>The extension adminpanel can not be downloaded since Composer is used for package management. Please require this extension as package via Composer: "composer require typo3/cms-adminpanel:^9.2"</warning>
</pre>
<p>I'm not sure about the intended behaviour but I assume that the HTML tag <warning> should be replaced in a later step.</p>
<p>The the affected code is in <code>typo3/sysext/install/Classes/Updates/AbstractDownloadExtensionUpdate.php</code>, line 113.</p>
<p>In the same file, in lines 94 and 99 there is the HTML tag <error> used. But I haven't tested if these messages are affected as well.</p> TYPO3 Core - Bug #86266 (Closed): Since TYPO3 9.4 /typo3/install is gone and redirects to the fro...http://forge.typo3.org/issues/862662018-09-15T16:38:15ZPeter Kraumepeter.kraume@gmx.de
<p>Until now I was used to access the install tool with /typo3/install/<br />This is not possible with TYPO3 9.4 any more. Instead it should be /typo3/install.php<br />I assume that this change will lead to some confusion.<br />Maybe it's possible to redirect /typo3/install/ to /typo3/install.php</p> TYPO3 Core - Bug #86264 (Accepted): Trusted hosts pattern mismatch with Nginx and HTTP_X_FORWARDE...http://forge.typo3.org/issues/862642018-09-15T16:03:45ZPeter Kraumepeter.kraume@gmx.de
<p>When the frontend is called via https, there is this error message in the log:<br /><pre>
PHP Fatal error: Uncaught UnexpectedValueException: The current host header value does not match the configured trusted hosts pattern! Check the pattern defined in $GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern'] and adapt it, if you want to allow the current host header 'ddev105.ddev.local' for your installation. in /var/www/html/public/typo3/sysext/core/Classes/Utility/GeneralUtility.php:2803"
</pre></p>
<p>Install Tools says:<br /><pre>
The trusted hosts pattern will be configured to allow all header values. This is because your $SERVER_NAME:[defaultPort] is "ddev105.ddev.local:443" while your HTTP_HOST:SERVER_PORT is "ddev105.ddev.local:80". Check the pattern defined in Admin Tools -> Settings -> Configure Installation-Wide Options -> System -> trustedHostsPattern and adapt it to expected host value(s).
</pre></p>
<p>The problem seems to be that the DDEV configuration has no extra SSL configuration and thus there is a mismatch between SERVER_PORT and HTTP_X_FORWARDED_PORT which needs an additional check.</p>
Test environment:
<ul>
<li>DDEV 1.2.0</li>
<li>TYPO3 9.4 composer based</li>
</ul> TYPO3 Core - Bug #82879 (Closed): Add .tsconfig files to .editorconfighttp://forge.typo3.org/issues/828792017-10-29T13:04:17ZPeter Kraumepeter.kraume@gmx.de
<p>Add missing definition for .tsconfig files to .editorconfig file.<br />Decision was made on July 17th, 2017:<br /><a class="external" href="https://decisions.typo3.org/t/file-endings-for-typoscript-and-tsconfig-files-results/71/3">https://decisions.typo3.org/t/file-endings-for-typoscript-and-tsconfig-files-results/71/3</a></p> TYPO3 Core - Bug #78490 (Closed): file_get_contents fail prevents page tree to renderhttp://forge.typo3.org/issues/784902016-10-28T20:26:49ZPeter Kraumepeter.kraume@gmx.de
<p>This bug report was sent to <a class="email" href="mailto:info@typo3.org">info@typo3.org</a> by an anonymous person:</p>
<p>I have no Forge account and do not want to register, but since 8.4 (up to current master) I am getting the folliwng error in the backend:</p>
<p>Core: Error handler (BE): PHP Warning: file_get_contents(/var/www/test/typo3//test/typo3/sysext/backend/Resources/Public/JavaScript/extjs/components/pagetree/javascript/app.js): failed to open stream: No such file or directory in /var/www/test/typo3_src/typo3/sysext/core/Classes/Resource/ResourceCompressor.php line 285</p>
<p>This prevents the page tree from rendering because all the Javascript from loadorder.txt is missing.</p>
<p>The problem seems to be that an relativ path is concatenated to a absolute path. Probably related to making "EXT:" available in Backend modules.</p> TYPO3 Core - Bug #73591 (Closed): Page Module: Click menu in content elements missing if editor h...http://forge.typo3.org/issues/735912016-02-22T09:46:42ZPeter Kraumepeter.kraume@gmx.de
<p>How to reproduce:<br />- give editor only read access to page<br />- open page module and navigate to page with only read access<br />- try to open click menu of a content element</p>
<p>Expected behaviour:<br />- the click menu opens and shows only possible entries like show, info, copy, t3d export</p> TYPO3 Core - Bug #73477 (Closed): Saving edited bookmark with Enter reloads complete backendhttp://forge.typo3.org/issues/734772016-02-16T11:15:05ZPeter Kraumepeter.kraume@gmx.de
<p>How to reproduce:<br />- create bookmark<br />- edit the bookmark and change the label<br />- hit enter key to save changes<br />=> complete backend is reloaded but changed label isn't saved</p>
<p>Expected behaviour: changed label can be saved with enter key</p>