#101045ext:seo sitemap ignores the fact that pages doktype is localizable
Description
By default, a page’s doktype can change upon translation; thus, a default page can be an external link on any translation and vice versa. For example:
Page A lang: default, doktype: standard page translation: fr, doktype: external link to www.foo.de Page B lang: default, doktype: standard page translation: fr, doktype: external link to www.foo.de Page C lang: default, doktype: external link to www.bar.de translation: fr, doktype: standard page
On the FR sitemap, this leads to:
Page A (visible) (Entry: www.foo.de)
Page B (visible) (Entry: www.foo.de)
Page C (not visible)
Problem
- duplicate links in the sitemap
- inconsistent behavior (some external links are visible, some are not; some default pages are visible, some are not)
The sitemap should respect doktype filters (and other localizable ones) properly in all languages.
I understand that TYPO3 does filtering on the default language level only at many places, but this is inconsistent behavior.
This is true for TYPO3 10–12.
Reviews 1
Related issues 1
History 36
-
Markus Klein changed subject
ext:seo sitmap ignores the fact that pages doktype is localizableext:seo sitemap ignores the fact that pages doktype is localizable <span data-processor="relativetime" data-value="2023-07-10T11:29:23+00:00" > 07/10/23, 11:29 </span> -
Guido Schmechel commented <span data-processor="relativetime" data-value="2023-08-09T15:36:46+00:00" > 08/09/23, 15:36 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 80535 status
NewUnder Review <span data-processor="relativetime" data-value="2023-08-12T20:06:21+00:00" > 08/12/23, 20:06 </span> -
Gerrit Code Review pushed patch set 2 for main to change 80535 <span data-processor="relativetime" data-value="2023-08-12T20:27:45+00:00" > 08/12/23, 20:27 </span>
-
Markus Klein changed Related to #91670 <span data-processor="relativetime" data-value="2024-09-03T14:35:27+00:00" > 09/03/24, 14:35 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 80535 <span data-processor="relativetime" data-value="2025-01-19T15:31:53+00:00" > 01/19/25, 15:31 </span>
The same problem concerns the canonical field.
Example:
We have a client (SingleNode) with the languages DE and EN. For an EN page we now specify a canonical.
Result:
The page is still output in the sitemap.xml because of the DE canonical_link = ‘’ query.
Background:
Using the query in getPages() in PagesXmlSitemapDataProvider we get all DE pages. Via generateItems the overlays are fetched and all filter methods (canonical, doktype and more) are ignored.
Possible solution v13:
- We first fetch all pages of the default language and filter the result afterwards
- Remove TypoScript Condition for the canonical field
- Introduce a new constant for canonical fields (excldueCanonicalPages = 1 / Default on)
- Introduce PSR-14 events (separate issue) to change pages results
Workaround:
Use a custom provider via TypoScript