TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-09-05T09:38:24ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101848 (Resolved): PHP 8 warning in EXT:Backend\FrontendBackendUserAuthenticati...http://forge.typo3.org/issues/1018482023-09-05T09:38:24ZChristian Toffolo
<p><a class="external" href="https://github.com/TYPO3/typo3/blob/d8c1b99a34aa4d27922a66822e5c114fc5f52e12/typo3/sysext/backend/Classes/FrontendBackendUserAuthentication.php#L181">https://github.com/TYPO3/typo3/blob/d8c1b99a34aa4d27922a66822e5c114fc5f52e12/typo3/sysext/backend/Classes/FrontendBackendUserAuthentication.php#L181</a><br /><pre>
if (!$conf['onlyCurrentPid'] || $pid == $GLOBALS['TSFE']->id) {
</pre><br />should be<br /><pre>
if (!($conf['onlyCurrentPid'] ?? false) || $pid == $GLOBALS['TSFE']->id) {
</pre></p> TYPO3 Core - Bug #101847 (Resolved): PHP 8 warning in EXT:Backend\FrontendBackendUserAuthenticati...http://forge.typo3.org/issues/1018472023-09-05T09:32:39ZChristian Toffolo
<p><a class="external" href="https://github.com/TYPO3/typo3/blob/d8c1b99a34aa4d27922a66822e5c114fc5f52e12/typo3/sysext/backend/Classes/FrontendBackendUserAuthentication.php#L111">https://github.com/TYPO3/typo3/blob/d8c1b99a34aa4d27922a66822e5c114fc5f52e12/typo3/sysext/backend/Classes/FrontendBackendUserAuthentication.php#L111</a><br /><pre>
} elseif ($GLOBALS['TCA'][$table]['ctrl']['languageField']) {
</pre><br />should be<br /><pre>
} elseif ($GLOBALS['TCA'][$table]['ctrl']['languageField'] ?? false) {
</pre></p> TYPO3 Core - Bug #101319 (Closed): Impossible to not display controls in videohttp://forge.typo3.org/issues/1013192023-07-11T13:46:57ZChristian Toffolo
<p>The simplest way to not display controls in HTML5 video it to not add the "controls" attribute at all to the video element.</p>
<p>\TYPO3\CMS\Core\Resource\Rendering\VideoTagRenderer renders the "controls" attribute in any case, making it harder to not display controls.</p> TYPO3 Core - Feature #101161 (New): New access right: Show if not logged inhttp://forge.typo3.org/issues/1011612023-06-23T10:37:11ZChristian Toffolo
<p>Use case: I want to hide a page only from users in a specific user group (e.g. SpecialUsers). So the page should still be visible if a user is not logged in.</p>
<p>AFAIK, at the moment, there's no way to do this in TYPO3.</p>
I think the best solution to this problem is to implement a new default access right: "Show if not logged in" <br />This way I can put all users who are not SpecialUsers in a group "No SpecialUsers".<br />Then I will set the access right to the page as:
<ul>
<li>"Show if not logged in" </li>
<li>"No SpecialUsers"</li>
</ul>
<p>This way the page will be visible if a user is not logged in and if a user is in the "No SpecialUsers" group (i.e.: users not in the "SpecialUsers" group).</p>
<p>Another solution could be to split the access right field in two:<br />- Visible to<br />- Hidden to<br />But that is probably too complicated.</p> TYPO3 Core - Bug #100063 (New): l10n_display=hideDiff not working for pi_flexformhttp://forge.typo3.org/issues/1000632023-03-02T13:17:17ZChristian Toffolo
Setting pi_flexform:
<ul>
<li>l10n_display = hideDiff</li>
<li>l10n_mode = exclude</li>
</ul>
<p>still displays the pi_flexform fields.</p> TYPO3 Core - Bug #99444 (New): Core: Exception handler (WEB: FE): Error, code #0, file TypoScript...http://forge.typo3.org/issues/994442023-01-02T09:44:20ZChristian Toffolo
<p>Generated by Googlebot visiting a translated page that is a shortcut to another page like:<br /><a class="external" href="http://domain.ext/es/soporte/">http://domain.ext/es/soporte/</a><br />that is a shortcut to page with uid=3</p>
<p>PHP error log:<br />Mon, 02 Jan 2023 08:38:14 +0100 [WARNING] request="31bc2c162961e" component="TYPO3.CMS.Core.Error.ErrorHandler": Core: Error handler (FE): PHP Warning: Undefined array key "uid" in typo3/sysext/core/Classes/Domain/Repository/PageRepository.php line 1101<br />Mon, 02 Jan 2023 08:38:14 +0100 [WARNING] request="31bc2c162961e" component="TYPO3.CMS.Core.Error.ErrorHandler": Core: Error handler (FE): PHP Warning: Undefined array key "uid" in typo3/sysext/core/Classes/Domain/Repository/PageRepository.php line 1112<br />Mon, 02 Jan 2023 08:38:14 +0100 [CRITICAL] request="31bc2c162961e" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB: FE): Error, code #0, file typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php, line 2099: Attempt to assign property "rootLine" on null - {"mode":"WEB","application_mode":"FE","exception_class":"Error","exception_code":0,"file":"typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php","line":2099,"message":"Attempt to assign property \"rootLine\" on null","request_url":"https://domain.ext/es/soporte/","exception":null}</p> TYPO3 Core - Bug #98947 (Closed): TCEMAIN.clearCacheCmd = cacheTag not workinghttp://forge.typo3.org/issues/989472022-10-28T10:30:22ZChristian Toffolo
<p>I'm trying to make a configuration like this to work for my own Extbase extension:<br />1) TCEMAIN.clearCacheCmd = cacheTag:tx_iantest</p>
<p>Testing it, it doesn't clear the pages cache with tags like tx_iantest_123.</p>
<p>Instead this one works for tags like tx_news_123:<br />2) TCEMAIN.clearCacheCmd = cacheTag:tx_news</p>
<p>Even if I placed both config 1 & 2 in the Page TSconfig of the page with news records, where the config number 2 works, the config number 1 doesn't seem to have effect. By example: it doesn't delete records LIKE 'tx_iantest' in cache_pages_tags while config number 2 does delete records LIKE 'tx_news'.</p> TYPO3 Core - Bug #98927 (Under Review): JS async option of includeJS broke by file in includeJSFo...http://forge.typo3.org/issues/989272022-10-26T11:18:03ZChristian Toffolo
<p>To reproduce, have a Typoscript like:</p>
<pre>
page {
includeJS {
headerJSfile = EXT:example/Resources/Public/JavaScript/headerJSfile.js
headerJSfile.async = 1
}
includeJSFooter {
footerJSfile = EXT:example/Resources/Public/JavaScript/footerJSfile.js
}
}
</pre>
<p>Expected behavior it a HTML code like:<br /><code><script src="/typo3temp/assets/compressed/merged-e942e6f0ca1ee79f54a389342a8850b9-78533bc4645ca634f7c62a6bbc42edef.js?1665838235" async="async"></script></code><br />Instead <code>async="async"</code> is not present because of the file configured in includeJSFooter.</p> TYPO3 Core - Bug #98457 (New): Processed file doesn't existhttp://forge.typo3.org/issues/984572022-09-28T09:30:55ZChristian Toffolo
<p>Use case: configure TYPO3 so that f:uri.image generated files are created inside typo3temp instead of fileadmin folder.</p>
<p>Steps to reproduce:<br />1. have 'fileadmin/ (auto-created)' storage with uid=1<br />2. have 'typo3temp' storage with uid=2<br />3. setting <code>processingfolder</code> field of 'fileadmin/ (auto-created)' storage to '2:assets/_processed_'</p>
<p>This setup results in f:uri.image renders the correct path (eg: /typo3temp/assets/_processed_/e/6/959161_10151652466566963_1259477499_o_5a95879fc3.jpg) but the file doesn't exist.</p> TYPO3 Core - Bug #98231 (Closed): Can't login in BE because of 'loginLogo' pathhttp://forge.typo3.org/issues/982312022-08-30T16:15:41ZChristian Toffolo
<p>After upgrade to 11 LTS I couldn't login in BE because of error:<br />Resource paths must start with "EXT:"</p>
<p>TYPO3 is trying to send the login alert email but I set:<br />'loginLogo' => '/fileadmin/user_upload/Logo.svg'<br />that's not an public resource path and NormalizedUrlViewHelper uses PathUtility::getPublicResourceWebPath.</p>
<p>I need the logo in fileadmin so the editors can use it as image on the website.</p>
<p>Why can't NormalizedUrlViewHelper use PathUtility::getAbsoluteWebPath instead?</p> TYPO3 Core - Feature #97496 (New): Return 401 on failed loginhttp://forge.typo3.org/issues/974962022-04-28T06:51:23ZChristian Toffolo
<p>Return 401 HTTP code on failed login to the BE and felogin so an intrusion prevention software like fail2ban can be configured to detect brute force attacks.</p> TYPO3 Core - Feature #97043 (New): Replace IRRE image while retaining text and linkshttp://forge.typo3.org/issues/970432022-02-25T12:35:06ZChristian ToffoloTYPO3 Core - Feature #95447 (New): Edit file properties directly from where it is referencedhttp://forge.typo3.org/issues/954472021-10-02T12:14:47ZChristian Toffolo
<p>Allow the BE editor to edit file properties (filename; metadata; delete the file) directly from where it is referenced instead of "force" the editor to switch to the Filelist module and search for the file.</p> TYPO3 Core - Bug #95052 (Closed): BE stuck after search, in case user cannot edit recordhttp://forge.typo3.org/issues/950522021-08-31T13:10:11ZChristian Toffolo
<p>If a BE user search something in the upper/right search box and then clicks on a record that the user can't edit then the 3rd column of the BE is stuck and display only the loader.</p> TYPO3 Core - Bug #94386 (Closed): Impossible to hide "Page translation" records in list modulehttp://forge.typo3.org/issues/943862021-06-19T08:39:40ZChristian Toffolo
<p>It's not possible to hide "Page translation" records in list module using the documented config:<br />mod.web_list.hideTables = *</p>