Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
These are the fringe cases that need to be handled right now:
1. User enables/disables a module that provides XML sitemap context: ?
2. User edits an individual sitemap and changes its context: delete files and queue sitemap for updating.
Comments
Comment #1
Dave ReidThese are essential to ensure smooth operations for the end-users of the module.
Comment #2
klonos...coming from #789026: sitemap.xml returns "page not found"
Comment #3
Dave ReidComment #4
Dave ReidCommitted initial work on this to make sure directories get renamed when context changes.
Comment #5
pcambraSubscribe.
Will be this backported to drupal 6 version? Whenever I enable xmlsitemap_i18n I get page not found as here is reported: #789026: sitemap.xml returns "page not found"
Comment #6
Dave ReidIt was already backported.
Comment #7
pcambraHi Dave,
I'm still getting a page not found if I enable the xmlsitemap_i18n submodule, which version of xmlsitemap fixes this problem?
I've installed elements module and recreated sitemaps.
Comment #8
Dave ReidYou currently can't just enable the xmlsitemap_i18n module and expect everything to work the same. Right now you have to go and re-edit all of your sitemaps (making sure to select a language) and then make sure to regenerate the files.
Comment #9
mgiffordWhat needs to be done to close this issue?
Comment #11
dodge CreditAttribution: dodge commentedI'm currently experiencing this issue using the Locale module to provide different languages.
Not really sure what #8 above is referring to. If I click "Edit", I just get a message "There are currently no XML sitemap contexts available." and an option to save (no opportunity to select a language).
Either way http://mysite/en/sitemap.xml gives a "not found" error.