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
In the CMS we use StructuralPage create branches/folders in the page tree. These StructuralPages do not have content but allow us to structure URL paths as we need, including matching some routes that already exist in the page tree as static/Django-only paths
However, we've spotted a bug: if there's a static path for foo/ and a StructuralPage for foo/, the static path is dropped from the page tree, as can be seen here: mozmeao/www-sitemap-generator@bdd1cc0
Expected result
Paths for StructuralPages should not steamroll over static Django-view paths - only add to them
Actual result
Paths for StructuralPages did steamroll over static Django-view paths - leaving only /en-US/about/ in the sitemap, rather than /<all the other locales>/about/
Note that the /about/ page is still available in all the locales it was originally -- this is just about sitemap generation
The text was updated successfully, but these errors were encountered:
The clearest solution, as discussed with @alexgibson, is simply to ensure that StructuralPages are not included in the lookup of pages used for the sitemap - we never want to send anyone to them directly, after all, and visiting a StructuralPage just 302s to the parent path.
Description
In the CMS we use
StructuralPage
create branches/folders in the page tree. TheseStructuralPage
s do not have content but allow us to structure URL paths as we need, including matching some routes that already exist in the page tree as static/Django-only pathsHowever, we've spotted a bug: if there's a static path for
foo/
and aStructuralPage
forfoo/
, the static path is dropped from the page tree, as can be seen here: mozmeao/www-sitemap-generator@bdd1cc0Expected result
Paths for
StructuralPage
s should not steamroll over static Django-view paths - only add to themActual result
Paths for
StructuralPage
s did steamroll over static Django-view paths - leaving only/en-US/about/
in the sitemap, rather than/<all the other locales>/about/
Note that the /about/ page is still available in all the locales it was originally -- this is just about sitemap generation
The text was updated successfully, but these errors were encountered: