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 - 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 #91113 (Closed): Fix paths to AJAX urls of Dashboardhttp://forge.typo3.org/issues/911132020-04-18T14:47:40ZRichard Haeserrichard@richardhaeser.com
<p>/Build/Sources/TypeScript/dashboard/Resources/Public/TypeScript/Grid.ts<br />86:46 error ["dashboard_save_widget_positions"] is better written in dot notation dot-notation</p>
<p>/Build/Sources/TypeScript/dashboard/Resources/Public/TypeScript/WidgetContentCollector.ts<br />32:68 error ["dashboard_get_widget_content"] is better written in dot notation dot-notation</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 - Feature #90521 (Closed): AdminOnly widgetshttp://forge.typo3.org/issues/905212020-02-24T14:46:23ZRichard Haeserrichard@richardhaeser.com
<p>It should be possible to add widgets that should only be shown to admins to prevent information disclosure.</p> TYPO3 Core - Feature #90333 (Closed): Dashboard backend modulehttp://forge.typo3.org/issues/903332020-02-05T20:43:59ZRichard Haeserrichard@richardhaeser.com
<p>The dashboard will be a backend module to show the widgets to the user.</p>
<p>It should be possible to:<br />- Create one or more dashboards. A dashboard is personal (so everyone gets its own dashboards and dashboard are not shared between users)<br />- Select a widget from the available widgets and add it to the current dashboard<br />- Reorder the widgets<br />- Register new widgets by PHP<br />- Register new dashboardTemplates by PHP<br />- Register new widgetGroups by PHP</p>
<p>Widgets that will be available within this task:<br />- RSS widget with latest news about TYPO3<br />- CTA to the TYPO3 Documentation<br />- Text widget with general information about TYPO3 (top of output in About module)</p>
<p>More widgets and abstracts will come in separate tasks / patches.</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 - 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 - 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 - 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>