TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-09-28T09:21:37ZTYPO3 Forge
Redmine 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 #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 #30088 (Closed): Wrong content element rendering in system extension formhttp://forge.typo3.org/issues/300882011-09-20T13:53:13ZOliver Haderoliver.hader@typo3.org
<p>The ability to render custom content elements in the system extension form fails.</p> TYPO3 Core - Bug #29769 (Closed): Parse error in t3lib/class.t3lib_parsehtml.phphttp://forge.typo3.org/issues/297692011-09-14T10:21:00ZOliver Haderoliver.hader@typo3.org
<p>There is a syntax error in t3lib/class.t3lib_parsehtml.php.</p> TYPO3 Core - Bug #28955 (Rejected): Flushing database caches truncates table before dropping ithttp://forge.typo3.org/issues/289552011-08-12T21:38:37ZOliver Haderoliver.hader@typo3.org
<p>The database backend of the caching framework first truncates tables before dropping them.<br />This happens on calling the flush() method there and seems not to be required at all.</p> TYPO3 Core - Bug #28625 (Closed): ImageMagick path detection fails on Mac OS Xhttp://forge.typo3.org/issues/286252011-07-31T23:49:30ZOliver Haderoliver.hader@typo3.org
<p>The ImageMagick path detection fails on Mac OS X.<br />If MacPorts is used the additional folder /opt/local/bin should be checked.</p>
<p>Since the path could only be modified in the launchd script, it's worth to statically add it in the install tool.<br />see also <a class="external" href="http://stackoverflow.com/questions/6833939/path-environment-variable-for-apache2-on-mac">http://stackoverflow.com/questions/6833939/path-environment-variable-for-apache2-on-mac</a></p> TYPO3 Core - Bug #25431 (Closed): Pagetree uses wrong setting for limiting number of rendered pag...http://forge.typo3.org/issues/254312011-03-29T17:57:21ZOliver Haderoliver.hader@typo3.org
<p>The pagetree uses a wrong setting for limiting the number of rendered page nodes. The result is, that there are many AJAX requests on rendering the ExtJS pagetree.</p>
<p>$GLOBALS['BE']['pageTree']['preloadLimit'] should be $GLOBALS['TYPO3_CONF_VARS']['BE']['pageTree']['preloadLimit']</p> TYPO3 Core - Bug #24777 (Closed): SQL error in Update Wizard of workspaceshttp://forge.typo3.org/issues/247772011-01-24T16:55:27ZOliver Haderoliver.hader@typo3.org
<p>On using the Update Wizard in the Install Tool, the following SQL error appears:<br />SELECT parentid FROM sys_workspace_stages WHERE parenttable="sys_workspace"</p>
<p>Solution: The stages table must be written in singular (sys_workspace_stage)</p>
<p>(issue imported from #M17274)</p> TYPO3 Core - Bug #21821 (Closed): treeLevel in TSconfig conditions should consider the creation o...http://forge.typo3.org/issues/218212009-12-08T11:41:17ZOliver Haderoliver.hader@typo3.org
<p>The TSconfig condition [treeLevel = 2] counts the level of nestification in the pagetree. However, in the backend new pages could be created and the mentioned condition should consider that situation as well.<br />PIDupinRootline behaves similar in the backend.</p>
<p>(issue imported from #M12977)</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> TYPO3 Core - Bug #17838 (Closed): Files with extension xml are ignored as resource of a templatehttp://forge.typo3.org/issues/178382007-11-23T19:00:19ZOliver Haderoliver.hader@typo3.org
<p>Uploading a xml file to a template (sys_template) is denied by TCEmain since the extension xml isn't part of the allowed file extensions. A possibility would be to define "xml" in the imagefile_ext, but XML isn't an image... ;-)</p>
<p>(issue imported from #M6817)</p>