TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-03-22T10:17:02ZTYPO3 Forge
Redmine 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 - 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 - 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 - Task #91035 (Closed): Wrong height of Type of Users Dashboard widgethttp://forge.typo3.org/issues/910352020-04-14T22:39:20ZRichard Haeserrichard@richardhaeser.com
<p>The widget is now to high. Should me height: medium</p> TYPO3 Core - Bug #91028 (Closed): Startup module option: First module in menu not working anymorehttp://forge.typo3.org/issues/910282020-04-14T15:20:49ZRichard Haeserrichard@richardhaeser.com
<p>The option "First module in menu" as the startup module in user settings is not working anymore. When choosing this option, you just got forwarded to the About modules module.</p> TYPO3 Core - Bug #90453 (Closed): Unused variable in dashboard controllerhttp://forge.typo3.org/issues/904532020-02-20T21:37:54ZRichard Haeserrichard@richardhaeser.com
<p>An unused parameter is passed to the Fluid template</p> TYPO3 Core - Feature #90354 (Closed): Status report widget for dashboardhttp://forge.typo3.org/issues/903542020-02-11T12:20:52ZRichard Haeserrichard@richardhaeser.com
<p>As a system administrator I would like to have the option to see if my current installation has any issues so I know if I have to check more specific things.</p>
<p>Status report just like it is in the About modules page. Showing a red widget with text when there are issues and a normal widget when everything is fine.</p> TYPO3 Core - Task #89477 (Closed): Switch to named keys in generateMetaTags hookhttp://forge.typo3.org/issues/894772019-10-22T12:38:03ZRichard Haeserrichard@richardhaeser.com
<p>EXT:seo is adding scripts to the $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['TYPO3\CMS\Frontend\Page\PageGenerator']['generateMetaTags'] hook. It is using automatic numeric keys because we use `$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['TYPO3\CMS\Frontend\Page\PageGenerator']['generateMetaTags'][]`. We should change that to named keys so it is more easy to disable specific generators.</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> TYPO3 Core - Bug #86526 (Closed): Wrong type is returned when no enhancers are configuredhttp://forge.typo3.org/issues/865262018-10-01T21:18:12ZRichard Haeserrichard@richardhaeser.com
<p>If you have a setup without page enhancers, the type parameter is not working anymore.</p>
<p>For example if you want to access the XML sitemap with ?type=1533906435 you will get the page-type 0.</p> TYPO3 Core - Bug #85126 (Closed): Subproperties of TwitterCardMetaTagManager not acceptedhttp://forge.typo3.org/issues/851262018-05-30T22:47:25ZRichard Haeserrichard@richardhaeser.com
<p>You can't set subproperties of TwitterCardMetaTagManager properties like e.g. twitter:image:alt because in the TwitterCardMetaTagManager the definition of the subProperties is not done correctly.</p> TYPO3 Core - Bug #77979 (Closed): Setting [SYS][dbClientCompress] resolves in an errorhttp://forge.typo3.org/issues/779792016-09-17T13:43:56ZRichard Haeserrichard@richardhaeser.com
<p>In the install-tool it is possible to set <code>[SYS][dbClientCompress]</code> but after enabling it, and going back to the install-tool again, this option is migrated by the <code>SilentConfigurationUpgradeService</code>. This service sets <code>[DB][Connections][Default][driverOptions]</code> to <code>true</code>, but in <code>Doctrine\DBAL\Driver\Mysqli\Driver::connect()</code> the argument for driverOptions should be an array and not a boolean.</p>