TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-02-03T08:26:50ZTYPO3 Forge
Redmine TYPO3 Core - Task #93414 (Closed): Functional tests TypoScript settings page titlehttp://forge.typo3.org/issues/934142021-02-03T08:26:50ZRichard Haeserrichard@richardhaeser.comTYPO3 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 - Feature #93188 (Closed): Possibility to disable hreflang per pagehttp://forge.typo3.org/issues/931882020-12-30T10:27:05ZRichard Haeserrichard@richardhaeser.com
<p>Although it should not be needed to disable the hreflang generation, people might have a reason to disable the hreflang generation. On <a class="external" href="https://www.richardhaeser.com/blog/how-to-disable-the-hreflang-tags-in-typo3">https://www.richardhaeser.com/blog/how-to-disable-the-hreflang-tags-in-typo3</a> I described how to do this in v10, but it is quite some work to do so. To make it a bit easier, a TypoScript configuration should help with this.</p> TYPO3 Core - Bug #89878 (Closed): Hreflang links not using canonical urlshttp://forge.typo3.org/issues/898782019-12-06T15:56:29ZRichard Haeserrichard@richardhaeser.com
<p>If you have set a canonical URL manually, this URL won't be used in hreflang tags. If a page or translation has a manual canonical, don't include that page in the hreflang tags.</p> TYPO3 Core - Epic #89797 (Closed): HrefLang / Canonical issueshttp://forge.typo3.org/issues/897972019-11-28T19:57:18ZRichard Haeserrichard@richardhaeser.com
<p>All related HrefLang issues</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 - 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 #88994 (Closed): Pages with set canonical field should be removed from sitemaphttp://forge.typo3.org/issues/889942019-08-21T22:19:29ZRichard Haeserrichard@richardhaeser.com
<p>Pages with a canonical set in the page properties, should not be shown in the XML sitemap.</p> TYPO3 Core - Feature #88771 (New): Page Title Templateshttp://forge.typo3.org/issues/887712019-07-15T21:44:05ZRichard Haeserrichard@richardhaeser.com
<p>In stead of using TypoScript options `config.noPageTitle`, `config.pageTitleFirst`, `config.pageTitleSeparator` and `config.pageTitle` to define how your title tags will look like in frontend, we should work with a template for page titles.</p>
<p>This template is bound to a site language so you can be as flexible as possible.</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 #88644 (Closed): Remove last parts of altPageTitleProviderhttp://forge.typo3.org/issues/886442019-06-27T21:10:20ZRichard Haeserrichard@richardhaeser.com
<p>Remove last leftovers of altPageTitleProvider</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 - Feature #88140 (Closed): Possibility to disable rendering hreflang tagshttp://forge.typo3.org/issues/881402019-04-12T20:47:29ZRichard Haeserrichard@richardhaeser.com
<p>In some cases, you don't want TYPO3 to render the hreflang tags. For example when you have a paginated overview and the amount of pages differs per language. In those cases, it is best to not have a hreflang tag.</p> TYPO3 Core - Feature #87826 (Accepted): Render og:locale and og:locale:alternate by defaulthttp://forge.typo3.org/issues/878262019-03-03T16:13:35ZRichard Haeserrichard@richardhaeser.com
<p>It would be really cool if the og:locale and og:locale:alternate are rendered by default. As you can see on <a class="external" href="http://ogp.me/">http://ogp.me/</a> the og:locale is giving information about in which locale the og tags are set. It is done in the format language_TERRITORY and the default is en_US.</p>
<p>See:<br />- <a class="external" href="http://ogp.me/">http://ogp.me/</a><br />- <a class="external" href="https://developers.facebook.com/docs/sharing/webmasters/">https://developers.facebook.com/docs/sharing/webmasters/</a></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>