You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not so much a problem as a critique of the method followed by GoogleSitemapExtension::canIncludeInSitemap(). This code seems to explicitly exclude items that may be visible under a different hostname.
Why is it necessary to limit to a single domain if the specification doesn't prohibit it?
The text was updated successfully, but these errors were encountered:
It does seem a bit contradictory, but it seems from the documentation that this only becomes an issue if only a single domain is verified (www.example.com and not example.com), but it isn't an issue if two domains are each verified under the same account (www.example.com and www.example.co.uk).
So my next question is, can we raise this as an issue with the googlesitemap module? A potential solution would be to make the single-domain restriction configurable.
It could also be argued that alterCanIncludeInGoogleSitemap hook allows users to override this behaviour, but it's still abit awkward.
I feel a change in behaviour would be acceptable, but I don't feel strongly that it's urgent. Would you mind if I submit a PR with a suggested fix?
I am investigating multiple-domain based localisation for a single site, and have been following the google sitemap guide at https://support.google.com/webmasters/answer/75712?hl=en
This is not so much a problem as a critique of the method followed by
GoogleSitemapExtension::canIncludeInSitemap()
. This code seems to explicitly exclude items that may be visible under a different hostname.Why is it necessary to limit to a single domain if the specification doesn't prohibit it?
The text was updated successfully, but these errors were encountered: