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
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
I am using numerical IDs for items on a static site. One of the items (a store location) has an ID of "404". Its getting stripped from the sitemap, since 404 pages are a somewhat special identifier to be used as a not found page in some cases for astro.
It seems that perhaps the exclusionary logic is a little too strict. Can this be made to instead only match this type of pattern?
/404
/500
/[locale]/404
/[locale]/500
In my case the page follows this pattern
/store/[state]/[city]/[store-id]
What's the expected result?
Not all pages that end in 404 should be excluded from the site map
@matthewp@ascorbic I think this can actually be closed? I had an PR (#10779) that was merged last month. The updated sitemap plugin is working correctly for my use case now
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
I am using numerical IDs for items on a static site. One of the items (a store location) has an ID of "404". Its getting stripped from the sitemap, since 404 pages are a somewhat special identifier to be used as a not found page in some cases for astro.
It seems that perhaps the exclusionary logic is a little too strict. Can this be made to instead only match this type of pattern?
In my case the page follows this pattern
What's the expected result?
Not all pages that end in 404 should be excluded from the site map
Link to Minimal Reproducible Example
https://github.com/adrianlyjak/astro/tree/404-fix/packages/integrations/sitemap/test/fixtures/static
Participation
The text was updated successfully, but these errors were encountered: