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 #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> TYPO3 Core - Task #91078 (Closed): Add web-animate as package for EXT:dashboardhttp://forge.typo3.org/issues/910782020-04-17T09:06:33ZRichard Haeserrichard@richardhaeser.com
<p>As there is a small difference with the original library in web-animate.js the problem needs to be fixed in the original library. After that is fixed, we will add it to TYPO3 as a package.</p>
<p>Currently talking to the library owner about this.</p> TYPO3 Core - Bug #90687 (Closed): Backend search is corrupted due to missing fields in dashboardhttp://forge.typo3.org/issues/906872020-03-09T09:42:30ZRichard Haeserrichard@richardhaeser.com
<p>When you have installed the dashboard extension and try to search in the backend, you will receive an error Unknown column 'configuration' in 'where clause'.</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 - Task #90353 (Closed): Acceptance tests for dashboardhttp://forge.typo3.org/issues/903532020-02-11T11:39:42ZRichard Haeserrichard@richardhaeser.com
<p>As the dashboard is all about the UI, we should include acceptance tests to the extension.</p> TYPO3 Core - Feature #89502 (Closed): Add possibility to set site title in Site configurationhttp://forge.typo3.org/issues/895022019-10-24T16:20:24ZRichard Haeserrichard@richardhaeser.com
<p>It should be possible to set the title of the website in the Site configuration and not in the Template record as it is now. It should be possible to set it on a language base so you could have a localized site title.</p>
<p>This information will be used for generating the page title but later on for schema.org as well.</p> TYPO3 Core - Feature #88648 (Closed): Add possibility to set Twitter card type in backendhttp://forge.typo3.org/issues/886482019-06-27T22:35:26ZRichard Haeserrichard@richardhaeser.com
<p>It should be possible to set the type of Twitter card to show from the backend of TYPO3. Now by default type summary is shown.</p> TYPO3 Core - Task #88251 (Closed): Add functional tests for hreflang generatorhttp://forge.typo3.org/issues/882512019-04-30T21:15:49ZRichard Haeserrichard@richardhaeser.com
<p>We definitely need some functional tests for the hreflang generator</p> TYPO3 Core - Task #86419 (Closed): Add default cropping ratio for social share imageshttp://forge.typo3.org/issues/864192018-09-28T13:49:08ZRichard Haeserrichard@richardhaeser.com
<p>Facebook, LindedIn and Twitter do have the same aspect ratio for images of shared URL's. So it would be great if the default aspect ratio of the cropping tool is already providing the 1.91 / 1 ratio.</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 #86061 (Closed): Add more automated tests to XML Sitemaphttp://forge.typo3.org/issues/860612018-08-31T13:59:30ZRichard Haeserrichard@richardhaeser.com
<p>The XML sitemap feature needs some more unit- and functional-tests.</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 #85679 (Closed): Add robot.txt functionalityhttp://forge.typo3.org/issues/856792018-07-29T22:02:06ZRichard Haeserrichard@richardhaeser.com
<p>TYPO3 should deliver an out-of-the-box robots.txt to prevent certain directories (like eg /typo3) to be indexed. Besides that, it should be possible by integrators to block certain parts of the website to be crawled to prevent using crawl budget while it is not needed to be in the index.</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>