TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-14T17:36:06ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103400 (Under Review): Avoid mapping route values that are out of scopehttp://forge.typo3.org/issues/1034002024-03-14T17:36:06ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #103097 (Resolved): Avoid calling LogDataTrait::formatLogDetails in non-static c...http://forge.typo3.org/issues/1030972024-02-10T17:01:06ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #102942 (Resolved): Show language name in "Manage Language Packs" modalhttp://forge.typo3.org/issues/1029422024-01-26T11:59:15ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #102668 (Resolved): Consider empty or invalid password policy referencehttp://forge.typo3.org/issues/1026682023-12-13T18:08:30ZOliver Haderoliver.hader@typo3.org
<p>In case <code>$GLOBALS['TYPO3_CONF_VARS']['BE']['passwordPolicy']</code> is disabled or set to a preset that actually does not exist, the backend editing view should not issue JavaScript errors on the missing <code>#password-policy-info</code> element. Currently the following error appears in the browser console:</p>
<pre>
Uncaught TypeError: Cannot read properties of null (reading 'classList')
at HTMLInputElement.<anonymous> (password-element.js?bust=2e5226ec73ecf48bcbde72dd5fdea0b0252fc4ee:13:647)
</pre> TYPO3 Core - Bug #102386 (Resolved): Consider URL encoded values for addQueryString.excludehttp://forge.typo3.org/issues/1023862023-11-16T13:57:22ZOliver Haderoliver.hader@typo3.org
<pre>
typolink {
parameter = 1
addQueryString = 1
addQueryString {
exclude = param%,param%25
}
}
</pre>
<p>URL: <code>?keep=1&param%2525=2</code></p>
<p>Result: The params to be excluded are not removed - the TypoScrip property probably(?!) refers to the internal URL-decoded representation.</p> TYPO3 Core - Bug #102136 (Resolved): Revert: Enable configuration passthrough for custom CKEditor...http://forge.typo3.org/issues/1021362023-10-10T09:38:08ZOliver Haderoliver.hader@typo3.org
<p>ext:bootstrap_package v14.0.7 does not work anymore with change of issue <a class="issue tracker-1 status-3 priority-4 priority-default closed child parent" title="Bug: CKEditor 5 - Configuration of custom CKeditor 5 plugin via RTE.editor.config.{customPlugin} not p... (Resolved)" href="http://forge.typo3.org/issues/100784">#100784</a> since <code>extraPlugins</code> is handled differently.</p> TYPO3 Core - Bug #102058 (New): Meta tags rendered as XHTMLhttp://forge.typo3.org/issues/1020582023-09-28T10:21:50ZOliver Haderoliver.hader@typo3.org
<pre>
<meta name="generator" content="TYPO3 CMS" />
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
<meta name="robots" content="index,follow" />
...
<meta property="og:image:type" content="image/png" />
<meta property="og:title" content="IN.DIE.musik e.V." />
<meta name="twitter:card" content="summary" />
<meta name="twitter:site" content="@InDieMusik" />
</pre>
<p><a class="external" href="https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/MetaTag/AbstractMetaTagManager.php#L226-L239">https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/MetaTag/AbstractMetaTagManager.php#L226-L239</a></p>
<pre>
$metaTags[] = '<meta ' .
htmlspecialchars($nameAttribute) . '="' . htmlspecialchars($property) . '" ' .
htmlspecialchars($contentAttribute) . '="' . htmlspecialchars($propertyItem['content']) . '" />';
</pre> TYPO3 Core - Bug #102057 (New): W3C validator complains about base64 values in CSPhttp://forge.typo3.org/issues/1020572023-09-28T09:21:37ZOliver Haderoliver.hader@typo3.org
<p>From <a class="external" href="https://validator.w3.org/nu/">https://validator.w3.org/nu/</a></p>
<blockquote>
<p>Warning: Content-Security-Policy HTTP header: Bad content security policy: Invalid base64-value (should be multiple of 4 bytes: 54)</p>
</blockquote>
<p>From the specs at <a class="external" href="https://www.w3.org/TR/CSP3/#framework-directive-source-list">https://www.w3.org/TR/CSP3/#framework-directive-source-list</a></p>
<blockquote>
<p>; Nonces: 'nonce-[nonce goes here]'<br />nonce-source = "'nonce-" base64-value "'"</p>
<p>The base64-value grammar allows both base64 and base64url encoding. These encodings are treated as equivalant when processing hash-source values. Nonces, however, are strict string matches: we use the base64-value grammar to limit the characters available, and reduce the complexity for the server-side operator (encodings, etc), but the user agent doesn’t actually care about any underlying value, nor does it do any decoding of the nonce-source value.</p>
</blockquote>
<hr />
<p>For context, the used nonce value was <code>'nonce-GFsVtSG1EzqppYEFujbWjoMJS2r8FDH_Y8mRjRl-sKg9L0sLpQqsrA'</code></p>
<ul>
<li>that's <code>GFsVtSG1EzqppYEFujbWjoMJS2r8FDH_Y8mRjRl-sKg9L0sLpQqsrA</code> in base64web</li>
<li>that's <code>GFsVtSG1EzqppYEFujbWjoMJS2r8FDH/Y8mRjRl+sKg9L0sLpQqsrA</code> in base64 (shortened)</li>
<li>that's <code>GFsVtSG1EzqppYEFujbWjoMJS2r8FDH/Y8mRjRl+sKg9L0sLpQqsrA==</code> in base64 (complete, 56 chars, 56 mod 4 = 0)</li>
</ul> TYPO3 Core - Bug #101809 (Resolved): Ensure minimal dependency order in PackageManagerhttp://forge.typo3.org/issues/1018092023-08-31T10:23:22ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #61719 (Closed): Warnings on flushing whole workspace with localizationshttp://forge.typo3.org/issues/617192014-09-18T15:46:45ZOliver Haderoliver.hader@typo3.org
<p>Flushing a whole workspace in the workspace, which contains record localizations, shows warnings like this in the workspace module:<br /><cite>Attempt to reset workspace for record failed: No record</cite></p>
<p>The reason for that is simple, the record already has been flushed since it's a localization.</p>
<p>Thus, either the warning can be omitted by tracking already processed elements or record localizations need to be processed before the default record.</p> TYPO3 Core - Bug #59851 (Closed): Image thumbnails sometimes in backend not shownhttp://forge.typo3.org/issues/598512014-06-24T15:41:39ZOliver Haderoliver.hader@typo3.org
<p>Sometime the image thumbnails in the page module are not shown in the TYPO3 backend.<br />The reason for that could be missing reference count values in tt_content.image.</p>
<p>A work-around is to update those counters in SQL (don't use if workspaces are enabled and used):<br /><code><br />UPDATE tt_content<br />SET image=(SELECT COUNT(*) FROM sys_file_reference<br />WHERE uid_foreign = tt_content.uid) WHERE uid IN (SELECT uid_foreign FROM sys_file_reference);<br /></code></p> TYPO3 Core - Bug #55454 (Closed): Buttons for explicit translation are not shownhttp://forge.typo3.org/issues/554542014-01-30T13:19:39ZOliver Haderoliver.hader@typo3.org
Steps:
<ul>
<li>enable $GLOBALS['TYPO3_CONF_VARS']['BE']['explicitConfirmationOfTranslation'] in Install Tool</li>
<li>e.g. create or modify a record in the backend</li>
<li>the additional translation buttons are not rendered correctly</li>
</ul>
<p><img src="http://forge.typo3.org/attachments/download/25925/translation_buttons.png" alt="" loading="lazy" /></p>
<p>I'm not sure whether this feature is used or documented at all.<br />It seems, that the original commit for this feature was this:<br /><a class="changeset" title="* Feature added to disable automatic update of diff data for translation when saving records. Ins..." href="http://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/a19fb26a51243b4a74d2f8d13f882900fc12df99">a19fb26a51243b4a74d2f8d13f882900fc12df99</a></p> TYPO3 Core - Bug #50531 (Closed): Deleted state is not persisted in file objectshttp://forge.typo3.org/issues/505312013-07-29T18:53:05ZOliver Haderoliver.hader@typo3.org
<p>The deleted state of file objects of the file abstraction layer is not persisted and thus to carried to the database.<br />Since the concept of using the deleted flag is not used at all, additional checks and processors to set and unset the state need to be integrated.</p> TYPO3 Core - Bug #48451 (Closed): Backend Layouts not visualizedhttp://forge.typo3.org/issues/484512013-05-22T14:16:21ZOliver Haderoliver.hader@typo3.org
<p>Backend Layouts columns are not shown in the Web>Page view.</p> TYPO3 Core - Bug #21726 (Closed): Updating translations from repository in extension manager fail...http://forge.typo3.org/issues/217262009-11-28T15:53:33ZOliver Haderoliver.hader@typo3.org
<p>Updating translations from repository in extension manager fails in Safari 4.0.4 on Mac OS X. Just a white page is shown - after a while, when all packages have been downloaded, suddenly the full status appears. Thus, showing the process dynamically does not work.</p>
<p>In Firefox everything works as expected.</p>
<p>(issue imported from #M12822)</p>