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 - Feature #93619 (Closed): New record wizardhttp://forge.typo3.org/issues/936192021-03-01T13:27:58ZRichard Haeserrichard@richardhaeser.comTYPO3 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 #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 #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 #86157 (Closed): Pages with no_index,follow shouldn't be in XML sitemaphttp://forge.typo3.org/issues/861572018-09-05T16:18:57ZRichard Haeserrichard@richardhaeser.com
<p>Only pages with no_index = 0 should be in XML sitemap. Pages with follow = 1 shouldn't show up.</p> TYPO3 Core - Feature #85678 (Closed): Optimize handling title taghttp://forge.typo3.org/issues/856782018-07-29T21:51:12ZRichard Haeserrichard@richardhaeser.com
<p>There are a lot of ways setting the title tag of a page in frontend resulting in sometimes even multiple title tags. We should make a feature that is able to control the title tag and where it is easy to set defaults and that it easy to override the title tag by an extension.</p> TYPO3 Core - Feature #85147 (Closed): Render SEO meta tags in frontendhttp://forge.typo3.org/issues/851472018-06-03T20:57:42ZRichard Haeserrichard@richardhaeser.com
<p>The SEO meta tags that can be set in the page properties, should be rendered in frontend by default. In this way no additional configuration is needed to set those very important, basic SEO tags.</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 - Feature #82004 (Closed): Missing hooks in PageLayoutViewhttp://forge.typo3.org/issues/820042017-07-30T14:18:17ZRichard Haeserrichard@richardhaeser.com
<p>I want to make it possible to render some content on several places within the page module in the backend. Therefor it is needed to add some hooks in the PageLayoutView class.</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> TYPO3 Core - Bug #73444 (Closed): newContentElementWizard override not working in PageLayoutViewhttp://forge.typo3.org/issues/734442016-02-15T20:03:54ZRichard Haeserrichard@richardhaeser.com
<p>There is a possibility to override the newContentElementWizard by setting <code>mod.newContentElementWizard.override</code>. This is not working for the PageLayoutView. In this module the link is hard-coded to <code>BackendUtility::getModuleUrl('new_content_element', $urlParameters)</code></p>
<p>As a developer I would like to override this link as well so I can implement my own wizard for adding new content elements.</p>