Help debugging Google Sitemap "Page not found"

Questions
1

Silverstripe Version: SS5.4

I’ve got GitHub - wilr/silverstripe-googlesitemaps: Google Sitemaps module for the SilverStripe CMS installed and recently upgraded from SS5.3->5.4. I also installed the SilverStripe blog module and proceeded to make some changes to the blog pages via extensions.

I then noticed that mysite/sitemap.xml in my dev site no longer works - it simply shows a blank white page with “Page not found”. I rolled back the composer.lock in a copy of my dev site to the previous version (which is the same as in my live site, where sitemap.xml is working) and reverted all changes made since my last git push. This was done on a new blank database. The sitemap still doesn’t work - this does not make sense to me, as the dev site should now be the same as the live site (which works)?

I also started with a new blank SilverStripe project and installed all the same modules - sitemap.xml works. I then copied over all my project files and themes, but still can’t reproduce the bug in the fresh install.

To summarise:

  • copy of dev site with composer.lock as per live site (pre SS5.4 and no blog module), new blank database used: sitemap.xml not working on dev, working on live
  • new SilverStripe project with all the same modules and project files installed: sitemap.xml working
  • There’s no errors logged when trying to access sitemap.xml

I’m thinking it’s some sort of artefact in the dev site causing issues. I’ve tried deleting the vendor folder and running composer update multiple times, still no luck.

Any tips or ideas of how to step though the sitemap code to find out why it’s not generating would be very helpful!

2

It sounds like you’ve done a thorough job isolating the issue—especially by testing a fresh SilverStripe project. One possible direction is to inspect environment-specific configs or any lingering cache/data artifacts that may not reset with composer update. You might also find it helpful to check your dev environment’s .htaccess or routing rules for conflicts.

1 Like
4

Got to the bottom of it eventually. When I thought I’d copied the dev site over and created a blank database, it somehow still had artefacts from testing (multiple unpublished Blogs with the same name - these should’ve been deleted when I created a new database in DDEV, but somehow did not). Once I’d loaded in a copy of the database from the live site, the sitemap worked again on the dev site.