Upgrading to 4.1.15 Causes Sitemap 404

  • Resolved inspiredtaste

    (@inspiredtaste)


    11 months, 1 week ago

    I upgraded from 4.1.13 to 4.1.15 and it was a complete disaster. My sitemap completely changed it’s structure from what it was before and all of the sitemaps went to a 404 page. I had to roll back immediately.

Viewing 9 replies - 1 through 9 (of 9 total)

  • The Issue was reported.

    @Auctollo thx for your fast reaction. <3

    After updating to the new version (4.1.16), the problem with the 404 page not found errors persists.

    After calling up domain.com/sitemap.xml, for example, post-sitemap.xml or page-sitemap.xml leads to the 404 error.

    Thread Starter inspiredtaste

    (@inspiredtaste)

    I can also confirm that the 404 issue persists after updating to 4.1.16. All of the sub sitemaps lead to a 404. I would suggest that everyone does not update until the next version.

    Just tried the 4.1.16 and still got 404 errors, went back to 4.1.13.

    The “sitemap.xml” works, and the sub sitemap “sitemap-misc.xml”, all others are 404.

    same problem here.

    Same as @cecke123

    Only the sitemap.xml and sitemap-misc.xml works.

    Others like post-sitemap.xml or page-sitemap.xml gives 404 error.

    We had the same issue. Are you also using WPS Hide Login plugin? We deactivated that, and the sitemap/404 issue disappeared.

    Plugin Author Auctollo

    (@auctollo)

    Thanks for reporting this. The latest release (v4.1.18) resolves this issue.

    I just installed 4.1.8 and no longer have the 404 error. Additionally no plugin conflicts for my install and not further issues so far.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Upgrading to 4.1.15 Causes Sitemap 404’ is closed to new replies.