TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-09-05T16:18:57ZTYPO3 Forge
Redmine 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 - Task #86123 (Closed): Cleanup of PageTitle APIhttp://forge.typo3.org/issues/861232018-09-03T21:17:59ZRichard Haeserrichard@richardhaeser.com
<p>See <a class="external" href="https://review.typo3.org/#/c/57881/">https://review.typo3.org/#/c/57881/</a></p> TYPO3 Core - Task #86121 (Closed): Deprecate AltPageTitleProviderhttp://forge.typo3.org/issues/861212018-09-03T21:12:31ZRichard Haeserrichard@richardhaeser.com
<p>Because the usage of $GLOBALS['TSFE']->altPageTitle is deprecated<br />since version 9 and will be removed in version 10, the whole class<br />can be deprecated.</p> TYPO3 Core - Bug #85720 (Closed): config.noPageTitle = 2 not working in masterhttp://forge.typo3.org/issues/857202018-08-01T23:41:54ZRichard Haeserrichard@richardhaeser.com
<p>If you sate a website title in your template record and you set config.noPageTitle = 2, you still get the website title as your title tag. This is because of missing type casting.</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 #84798 (Closed): Add some extra SEO fields to corehttp://forge.typo3.org/issues/847982018-04-19T16:11:02ZRichard Haeserrichard@richardhaeser.com
<p>Every websites benefits from a good SEO and therefor I think it is good to have some extra options in the core. At the moment there are several extensions adding properties to pages to make it possible to set some meta tags for Search Engine Optimization. By adding this to core, we help TYPO3 to provide more SEO options out of the box.</p>
The fields that should be added to TCA (without a "special" function)
<ul>
<li>SEO title => just an input field</li>
<li>robot instructions => two fields: on "Index this page" and "Follow this page". This should be the new toggle feature</li>
<li>OpenGraph-tags => 1 input field title, a textarea for description and a image field</li>
<li>Twitter-tags => 1 input field title, a textarea for description and a image field</li>
</ul>
<p>This should be done in page properties on a new tab called SEO. Also the description field (that is now on the Metadata tab) needs to be moved to the SEO tab.</p>
<p>If you have any question, please ask <a class="user active user-mention" href="http://forge.typo3.org/users/5127">@Richard Haeser</a></p>
<p>See <a class="external" href="https://decisions.typo3.org/t/include-some-basic-seo-options-to-core/289">https://decisions.typo3.org/t/include-some-basic-seo-options-to-core/289</a></p> TYPO3 Core - Feature #83668 (Closed): Make list of files paginatable in file selector popuphttp://forge.typo3.org/issues/836682018-01-24T10:36:37ZRichard Haeserrichard@richardhaeser.com
<p>When you have a lot of files in 1 directory and want to add a file to for example a page resource, the popup is showing all results in 1 page. It should be great if this list is paginated just like the File list module.</p> TYPO3 Core - Bug #83479 (Closed): Minimal install of CMS9 causes warning in backendhttp://forge.typo3.org/issues/834792018-01-05T11:40:56ZRichard Haeserrichard@richardhaeser.com
<p>When you do not install any extensions, but just composer require typo3/minimal, you get a warning:<br /><pre>
PHP Warning: Invalid argument supplied for foreach() in /var/www/cms9/Web/typo3/sysext/backend/Classes/Domain/Repository/Module/BackendModuleRepository.php line 192
</pre></p>
<p>This is because the variable <pre>$GLOBALS['TBE_MODULES_EXT']</pre> might not be set yet.</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> TYPO3 Core - Bug #25117 (Closed): Error on upgrading workspaces 4.4.6 => 4.5.0http://forge.typo3.org/issues/251172011-02-21T12:30:22ZRichard Haeserrichard@richardhaeser.com
<p>I just upgraded an environment from 4.4.6 to 4.5.0. When trying to update the workspaces in the install-tool, I get an error:</p>
<p>Fatal error: Call to a member function includeLLFile() on a non-object in [.....]/typo3_src-4.5.0/typo3/sysext/em/classes/install/class.tx_em_install.php on line 72</p>
<p>(issue imported from #M17688)</p> TYPO3 Core - Bug #24458 (Closed): Installing extension: Dependency Window has a Back Button which...http://forge.typo3.org/issues/244582011-01-03T13:50:12ZRichard Haeserrichard@richardhaeser.com
<p>If you try to import an extension that depends on an extension that's not installed yet, you have the "import now" option.<br />After opening the popup and installing the needed extension, you have the link to close the popup. This link is working. But in the top left corner of that window there is the button "Back". This one is not working. If you click that option, the popup will not close, but it shows the content of the extension manager in the popup.</p>
<p>(issue imported from #M16897)</p>