TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-04-21T07:03:17ZTYPO3 Forge
Redmine TYPO3 Core - Bug #93961 (Closed): Images not converting to webp in image viewhelpershttp://forge.typo3.org/issues/939612021-04-21T07:03:17ZRichard Haeserrichard@richardhaeser.com
<p>By default the images viewhelpers (f:image and f:uri.image) are not converted to webp if you specify webp as the target file extension.</p>
<pre><code class="html syntaxhl" data-language="html"><span class="nt"><f:image</span> <span class="na">src=</span><span class="s">"{fileLocation}"</span> <span class="na">fileExtension=</span><span class="s">"webp"</span> <span class="nt">/></span>
</code></pre>
<p>This will not do anything and just returning the original image. This is because webp is not seen as a "valid" image extension as defined by <code>$GLOBALS['TYPO3_CONF_VARS'][GFX][imagefile_ext]</code></p> TYPO3 Core - Bug #93831 (Closed): Failing unit tests after update of symfony/mailerhttp://forge.typo3.org/issues/938312021-03-30T08:04:09ZRichard Haeserrichard@richardhaeser.com
<p>In symfony/mailer 5.2.6 and 4.4.21 symfony/mime is updated as well which has a change that will escape the name of the recipient of emails which cause our tests to fail.</p>
<p>See <a class="external" href="https://github.com/symfony/mime/compare/v5.2.5...v5.2.6">https://github.com/symfony/mime/compare/v5.2.5...v5.2.6</a></p> TYPO3 Core - Bug #93796 (Closed): Tree element doesn't hide overflowhttp://forge.typo3.org/issues/937962021-03-22T10:17:02ZRichard Haeserrichard@richardhaeser.com
<p>In current master, the select tree element is showing all nodes without an overflow which causes some nasty screens.</p>
<p><img src="http://forge.typo3.org/attachments/download/35964/Screenshot2021-03-22at10.59.39.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #93709 (Closed): User settings not accessible when no language packs are installedhttp://forge.typo3.org/issues/937092021-03-11T19:32:24ZRichard Haeserrichard@richardhaeser.com
<p>When accessing the user settings of the current backend user and when no language packs are installed, you get the following error:</p>
<pre><code class="php syntaxhl" data-language="php"><span class="no">PHP</span> <span class="nc">Warning</span><span class="o">:</span> <span class="nb">in_array</span><span class="p">()</span> <span class="n">expects</span> <span class="n">parameter</span> <span class="mi">2</span> <span class="n">to</span> <span class="n">be</span> <span class="k">array</span><span class="p">,</span> <span class="kc">null</span> <span class="n">given</span> <span class="n">in</span> <span class="o">/</span><span class="k">var</span><span class="o">/</span><span class="n">www</span><span class="o">/</span><span class="n">html</span><span class="o">/</span><span class="n">typo3</span><span class="o">/</span><span class="n">sysext</span><span class="o">/</span><span class="n">setup</span><span class="o">/</span><span class="nc">Classes</span><span class="o">/</span><span class="nc">Controller</span><span class="o">/</span><span class="nc">SetupModuleController</span><span class="mf">.</span><span class="n">php</span> <span class="n">line</span> <span class="mi">727</span>
</code></pre>
<p>This is introduced with change <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/68192">https://review.typo3.org/c/Packages/TYPO3.CMS/+/68192</a></p> TYPO3 Core - Bug #93515 (Closed): Show system news when only 1 item is availablehttp://forge.typo3.org/issues/935152021-02-15T09:30:17ZRichard Haeserrichard@richardhaeser.com
<p>Show system news when only 1 item is available</p> TYPO3 Core - Bug #93408 (Closed): Localization wizard styling issueshttp://forge.typo3.org/issues/934082021-02-02T09:32:32ZRichard Haeserrichard@richardhaeser.comTYPO3 Core - Bug #93300 (Closed): Canonical wrong with mountpointhttp://forge.typo3.org/issues/933002021-01-16T16:08:52ZRichard Haeserrichard@richardhaeser.com
<p>Issue originally from <a class="external" href="https://stackoverflow.com/questions/65732474/typo3-render-correct-canonical-of-selected-mountpoint">https://stackoverflow.com/questions/65732474/typo3-render-correct-canonical-of-selected-mountpoint</a></p>
<p>When I set the doktype of a page to Mount Point enter image description here and then set mount_pid_ol to Show the mounted page the canonical-tag of the current, site is rendered. Not the canonical of the site selected in mount_pid.</p>
<p>Is that Mount Point option somehow limited with the core SEO plugin since also the whole SEO-Tab is missing after selecting Mount Point?</p>
<p>Testing instructions to see how it should be:<br />- Create a mount point (lets call it page x) with mount_pid_ol set to 1<br />- Set the target of the mountpoint to another page (we will call it page y for now)<br />- If you visits page x in frontend, you should see a canonical pointing to page y</p>
<p>You can also create subpages on page y, which should be available below page x as well (in frontend). All those pages should point towards their page y url structure.</p>
<p>If you have set mount_pid_ol to 0, the subpages should still point towards their targets ( they y variant ). The mount page itself should have a canonical to the page x itself.</p> TYPO3 Core - Bug #93185 (Closed): Modal when deleting file in filelist is not showing correct texthttp://forge.typo3.org/issues/931852020-12-29T14:53:09ZRichard Haeserrichard@richardhaeser.com
<p>When I want to delete a file in the filelist, a modal shows up to let you confirm the delete. This modal is showing the wrong text. It is showing the text: "No content provided, please check your <code>Modal</code> configuration." now.</p> TYPO3 Core - Bug #92830 (New): Preserve selected page after filter reset in pagetreehttp://forge.typo3.org/issues/928302020-11-13T08:13:16ZRichard Haeserrichard@richardhaeser.com
<p>If I choose to use the filter function in the page tree to find a page by page id, the page is shown in the page tree and all parent pages is shown. If I then click on the page in the page tree and disables the filter focus one of two things happens.</p>
<blockquote>
<p>Focus is preserved - if the page was a visible part of the page tree before filtering</p>
</blockquote>
<p>or</p>
<blockquote>
<p>Focus is lost - if the page was not visible in the page tree before filtering</p>
</blockquote>
<p>It would be great if focus is preserved..</p> TYPO3 Core - Bug #92800 (Closed): Redirects not working correctly in redirectfinisher of EXT:formhttp://forge.typo3.org/issues/928002020-11-08T21:38:07ZRichard Haeserrichard@richardhaeser.com
<p>With the change of <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/commit/3dc902eeab54fcc2608dbcbe43f2d2c685ec1457#diff-ae5223ac59f428ebacf5b23f1885d433c37c2b3b4da2daa6747817b0c0327998R69">https://github.com/TYPO3/TYPO3.CMS/commit/3dc902eeab54fcc2608dbcbe43f2d2c685ec1457#diff-ae5223ac59f428ebacf5b23f1885d433c37c2b3b4da2daa6747817b0c0327998R69</a> it seems that when you enter a pageUid as a integer (which should be perfectly fine) is not working anymore resulting in a pageUid = 0.</p>
<p>Found this issue with the comment form of EXT:blog which returns to the homepage after submitting a comment.</p> TYPO3 Core - Bug #92191 (New): Page tree not showing in workspace renamed page title after movehttp://forge.typo3.org/issues/921912020-09-04T08:19:48ZRichard Haeserrichard@richardhaeser.com
<p>The page tree is not showing the correct name after moving a renamed record in a non-live workspace.</p>
<p>How to reproduce:<br />- Create page in live workspace<br />- Go to other workspace<br />- Rename a page<br />- You will see the new name in the page tree<br />- Move the renamed page to another parent<br />- You will now see the old name again</p> TYPO3 Core - Bug #92027 (Closed): Reset page tree filter after deletion of page recordhttp://forge.typo3.org/issues/920272020-08-17T09:18:25ZRichard Haeserrichard@richardhaeser.com
<p>The patch in <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/65208">https://review.typo3.org/c/Packages/TYPO3.CMS/+/65208</a> has 1 minor issue: when you delete a page that was matching your current filter, it will not reset the page tree to the state before filtering. As this was the old behaviour in previous TYPO3 versions, we should make sure this will be back.</p> TYPO3 Core - Bug #92001 (Closed): Unable to get property 'define' of undefined or null reference ...http://forge.typo3.org/issues/920012020-08-13T21:25:13ZRichard Haeserrichard@richardhaeser.com
<p>In every backend request in v10 and master, you get the error above in your console in Microsoft Edge (non-chromium). I'm not sure though if that version of the browser is supported in v10 and 11-dev as you can discuss if this is a "modern browser".</p>
<p>Microsoft Edge 44.17763.1.0<br />TYPO3: master / 10.3 / 10.4</p> TYPO3 Core - Bug #89848 (Under Review): Database Analyzer crashes with undefined enum fieldshttp://forge.typo3.org/issues/898482019-12-04T15:45:23ZRichard Haeserrichard@richardhaeser.com
<p>When you have a field in a column of type enum that is not specified in a sql file in the installation, the Database Analyzer in the install tool will crash and throws the error "array_map(): Argument #2 should be an array in /var/www/html/typo3/sysext/core/Classes/Database/Schema/Types/EnumType.php line 38". When you have the definition in a sql file of an extension, this won't cause an issue.</p>
<p>How to reproduce:<br />- Create a new field in tt_content with type enum and some values and a random name<br />- Go to Database Analyzer in install tool and run it</p> TYPO3 Core - Bug #87399 (New): Wrong default cropping when adding new cropVarianthttp://forge.typo3.org/issues/873992019-01-11T10:13:29ZRichard Haeserrichard@richardhaeser.com
<p>Situation:<br />You have for example a page and in the resources field you have configured 2 cropVariants already. The editors added content and have set their specific crops for all cropVariants.</p>
<p>After a while they decide they want a third cropVariant for the same field. When you add this configuration something strange happens. If you don't open the page properties in the backend, the frontend will correctly render the image with the new cropVariant and will be cropped from the center of the image. But when someone is checking the page properties and for example open the IRRE field for the already added images, the cropping of the new image is based on the first cropVariant instead of the original image. This only occurs with already connected images. When you add a new image, this is working as expected.</p>
<p>Tested and is "wrong" in v8 and v9.</p>