TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-09-08T14:54:31ZTYPO3 Forge
Redmine TYPO3 Core - Task #95154 (Closed): Add tests for redirect modulehttp://forge.typo3.org/issues/951542021-09-08T14:54:31ZRichard Haeserrichard@richardhaeser.com
<p>Checking for response-codes</p> TYPO3 Core - Feature #94190 (Rejected): Configurable widgetshttp://forge.typo3.org/issues/941902021-05-25T07:21:15ZRichard Haeserrichard@richardhaeser.com
<p>It would be awesome if a user can do a couple of settings for a widget. Think about number of items you want to view from a RSS feed or for example the period you want to view of errors in the log.</p> TYPO3 Core - Task #94182 (Closed): Missing titles for backend moduleshttp://forge.typo3.org/issues/941822021-05-20T20:22:09ZRichard Haeserrichard@richardhaeser.com
<p>As the new backend module web component router is showing the title of the main iframe as the title of the window, modules should set a proper title to the iframe to avoid getting a wrong title as the title of the previous window will remain.</p> 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 - Task #93715 (Closed): Stabilize acceptance testshttp://forge.typo3.org/issues/937152021-03-12T08:39:19ZRichard Haeserrichard@richardhaeser.com
<p>The install tool login is directly checking if the text "The<br />Install Tool is locked" while this text comes from an<br />async request which might take some time to show.</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 - Feature #93619 (Closed): New record wizardhttp://forge.typo3.org/issues/936192021-03-01T13:27:58ZRichard Haeserrichard@richardhaeser.comTYPO3 Core - Feature #93531 (Closed): Content status notificationshttp://forge.typo3.org/issues/935312021-02-17T10:53:57ZRichard Haeserrichard@richardhaeser.com
<p>It would be great if we could have a unified way of sending status messages to an editor about the content of the current page in the page module. This can be useful to give an editor information about things that might be wrong within the page.</p>
<p>You can think about:<br />- Warnings that the content is using broken links<br />- Results of SEO analysis<br />- Warning about accessibility issues<br />etc</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 - Task #93471 (Closed): Stabilize Page Tree Acceptance testshttp://forge.typo3.org/issues/934712021-02-09T10:47:41ZRichard Haeserrichard@richardhaeser.comTYPO3 Core - Task #93414 (Closed): Functional tests TypoScript settings page titlehttp://forge.typo3.org/issues/934142021-02-03T08:26:50ZRichard Haeserrichard@richardhaeser.comTYPO3 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>