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 #101809 (Resolved): Ensure minimal dependency order in PackageManagerhttp://forge.typo3.org/issues/1018092023-08-31T10:23:22ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #101753 (Closed): DDEV & Traefic substitute semi-colon to ampersand in URLshttp://forge.typo3.org/issues/1017532023-08-25T13:23:39ZOliver Haderoliver.hader@typo3.org
<p>With v1.22+ DDEV recently started to use Traefic as routing service - and Traefic has an issue with substituting ";" to "&" in URLs:</p>
<ul>
<li><a class="external" href="https://ddev.readthedocs.io/en/stable/users/extend/traefik-router/">https://ddev.readthedocs.io/en/stable/users/extend/traefik-router/</a></li>
<li><a class="external" href="https://github.com/traefik/traefik/issues/9164">https://github.com/traefik/traefik/issues/9164</a></li>
<li><a class="external" href="https://github.com/traefik/traefik/pull/9131/files#diff-f7d7f0e8fef165ce3ca78be8f4d887b323d564a29b25d416a6a7d2b0e9ff7df7R50">https://github.com/traefik/traefik/pull/9131/files#diff-f7d7f0e8fef165ce3ca78be8f4d887b323d564a29b25d416a6a7d2b0e9ff7df7R50</a></li>
</ul>
<p>Traeffic offers the option <a href="https://doc.traefik.io/traefik/routing/entrypoints/#encodequerysemicolons" class="external"><code>encodeQuerySemicolons</code></a> to actually control the behavior, however I was not able to adjust the corresponding configuration in DDEV.</p>
<p>For the time being, Traeffic can be disabled in general, by using <code>ddev poweroff && ddev config global --router=nginx-proxy</code>.</p>
<p>This affects how URLs in the TYPO3 backend scope are handled, e.g (this list is probably not complete, yet):</p>
<ul>
<li>/typo3/wizard/record/browse?token=[...]&mode=file&bparams=|||allowed=gif,jpg,jpeg,tif,tiff,bmp,pcx,tga,png,pdf,ai,svg <code>;</code> disallowed=|data-138-tt_content-1850-background_image-sys_file_reference&contentOnly=1&expandFolder=1%3A%2Ft3con23%2Fimages%2F
<ul>
<li>will be interpreted as<br /> /typo3/wizard/record/browse?token=[...]&mode=file&bparams=|||allowed=gif,jpg,jpeg,tif,tiff,bmp,pcx,tga,png,pdf,ai,svg <code>&</code> disallowed=|data-138-tt_content-1850-background_image-sys_file_reference&contentOnly=1&expandFolder=1%3A%2Ft3con23%2Fimages%2F</li>
<li>causes a failure in <code>\TYPO3\CMS\Filelist\ElementBrowser\FileBrowser::initialize</code></li>
</ul></li>
</ul>
<hr />
<p>Long-term, these URLs (especially the semi-colon "&") should be correctly URL-encoded.</p> TYPO3 Core - Bug #101705 (Resolved): Update composer.lock for typo3/html-sanitizer:2.1.3http://forge.typo3.org/issues/1017052023-08-17T11:03:20ZOliver Haderoliver.hader@typo3.org
<p>see <a class="external" href="https://stackoverflow.com/questions/76920144/typo3-11-5-30-error-after-bootstrap-update-undefined-function-mb-split">https://stackoverflow.com/questions/76920144/typo3-11-5-30-error-after-bootstrap-update-undefined-function-mb-split</a></p> TYPO3 Core - Bug #101460 (Resolved): Allow strict-dynamic only for applicable CSP directiveshttp://forge.typo3.org/issues/1014602023-07-27T10:56:06ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #101253 (Resolved): Normalize filename of uploaded fileshttp://forge.typo3.org/issues/1012532023-07-05T18:12:07ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #100012 (Closed): Skip numeric cookie names in RequestTokenMiddlewarehttp://forge.typo3.org/issues/1000122023-02-22T10:08:57ZOliver Haderoliver.hader@typo3.org
<p>Using an HTTP header like <code>Cookie: 1=string</code> results in having a numeric key in the super-global <code>$_COOKIE</code> array.</p> TYPO3 Core - Bug #99358 (Closed): Provide signed storage folders for legacy frontend loginhttp://forge.typo3.org/issues/993582022-12-13T14:07:15ZOliver Haderoliver.hader@typo3.org
<p>Security fix for TYPO3-CORE-SA-2022-013 in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/77084">https://review.typo3.org/c/Packages/TYPO3.CMS/+/77084</a> did not consider legacy frontend login plugin.</p> TYPO3 Core - Bug #23287 (Closed): Clearing caches in backend only displays empty framehttp://forge.typo3.org/issues/232872010-07-28T14:52:00ZOliver Haderoliver.hader@typo3.org
<p>Clearing caches in backend only displays empty frame - applies for the typo3conf and the frontend cache.</p>
<p>(issue imported from #M15263)</p> TYPO3 Core - Bug #21168 (Closed): Improve the error and exception handlinghttp://forge.typo3.org/issues/211682009-10-01T14:24:37ZOliver Haderoliver.hader@typo3.org
<p>Problem:<br />The new errorhandling in TYPO3 is way too unflexible.<br />- Errors are "converted" to exceptions. This is not very useful because every php warning will be turned into an exception. and will stop the script execution.<br />- DIsplayed error break the backend layout and make forms unusable<br />- Errors and exceptions are only displayed, but there's no build-in possibility to write errors and exception to a log.</p>
<p>Solution(s):<br />- introduce a new parameter for errors which should be handled by the error handler. The already existing parameter "exceptionalErrors" is used only for the error which should throw exceptions.<br />- Display the errors as flashmessages in the BE and as TsLog messages in FE (in the adminpanel)<br />- implement logging of errors and exceptions to the different logging systems TYPO3</p>
<p>Documentation:<br /><a class="external" href="http://wiki.typo3.org/index.php/File:Error_and_exception_handling.odt">http://wiki.typo3.org/index.php/File:Error_and_exception_handling.odt</a></p>
<p>(issue imported from #M12093)</p> TYPO3 Core - Bug #21078 (Closed): Optimize disposal of t3lib_PageRendererhttp://forge.typo3.org/issues/210782009-09-17T17:08:41ZOliver Haderoliver.hader@typo3.org
<p>t3lib_PageRenderer is currently used in the TYPO3 backend and frontend. There the classes template and tslib_fe inherit from t3lib_PageRenderer. However, in frontend disposal it's not required to have the feature set of the page renderer loaded if a request gets served by the cache and nothing is rendered at all.</p>
<p>Thus, instead of using "tslib_fe extends t3lib_PageRenderer", an aggreation shall be used.<br />Extension can then access the page renderer e.g. by $TSFE->getPageRenderer()->addJsFile()</p>
<p>(issue imported from #M11985)</p> TYPO3 Core - Bug #19530 (Closed): Store OpenID information in database instead of using the files...http://forge.typo3.org/issues/195302008-10-30T11:11:28ZOliver Haderoliver.hader@typo3.org
<p>The OpenID information currently gets stored in the filesystem. Due to security reasons it's preferred to have that sensible data in the database.</p>
<p>The file to be changed is class.tx_openid_sv1.php</p>
<p>(issue imported from #M9683)</p> TYPO3 Core - Bug #19496 (Closed): Flexform sections are not working anymore since script.aculo.us...http://forge.typo3.org/issues/194962008-10-22T16:41:47ZOliver Haderoliver.hader@typo3.org
<p>Due to a change of loading JavaScript resources between TYPO3 4.2.1 and 4.2.2 the script.aculo.us JavaScript framework now only gets loaded when it is required (before it was always loaded).</p>
<p>The solution is to explicitely load script.aculo.us when flexform sections are being rendered.</p>
<p>(issue imported from #M9623)</p> TYPO3 Core - Bug #17001 (Closed): config.linkVars check doesn't allow negative rangeshttp://forge.typo3.org/issues/170012007-02-17T11:05:42ZOliver Haderoliver.hader@typo3.org
<p>The newly introduced linkVars check in TYPO3 4.1 doesn't allow negative ranges.</p>
<p>Example:<br />config.linkVars = my_variable(1-5) is valid<br />config.linkVars = my_variable(-1-5) doesn't work<br />config.linkVars = my_variable(-1--3) doesn't work and looks very ugly</p>
<p>I suggest to use ".." as delimiter, e.g.<br />config.linVars = my_variable(-1..-3)</p>
<p>Possibly it is allowed in TYPO3 4.2 to use config.linkVars = tx_myext_pi1[var](<del>1..-3), but we should change the delimiter from "</del>" to ".." now.<br />(issue imported from #M5009)</p> TYPO3 Core - Bug #16875 (Closed): Wrong character encoding in new child records created via AJAX ...http://forge.typo3.org/issues/168752007-01-21T15:05:47ZOliver Haderoliver.hader@typo3.org
<p>If a new child record was created dynamically using an AJAX call. Umlauts like "äöüß" were not displayed correctly due to a missing character encoding.</p>
<p>(issue imported from #M4820)</p>