Have the issues been resolved ??

Still not resolved for me, even after clearing all caches. Still getting 404s when clicking on post and page links in sitemap. Had to revert back to 4.1.13.

I dont bother updating the plugin. I just stay at v4.1.13 for the time being.

I have the same problem, sitemaps are showing 404 errors. On our sites we also use WPS hide login plugin. Deactivating that plugin has fixed the 404 issue for sitemap pages for us. Not ideal long term, but a short term fix.

I have the 404 problem, but don’t use the WPS hide login plugin; could be multiple plugins causing the issue but I’m using 4.1.13 and have been in touch with support directly.

There is a saying: don’t touch what works well.

The developer decided to introduce some new functionality, without which it was already fine – we have been using the plugin for many years.

But the desire to redo everything ruined what worked perfectly.

It is sad.

Thanks to all for sharing your feedback and concern. The latest release (v4.1.18) resolves recent issues and functionality regressions.

For those interested in how we arrived here, changes to the development team, handling the deprecation of the Ping Protocol, which was replaced by the IndexNow Protocol, along with long-requested support of localization and e-commerce plugins required changes to code that’s nearly ten years old. The project also lacks a testing suite, making changes and improvements riskier.

We would prefer that the forum topics consist of edge cases and feature requests. Unfortunately, that has not been the case recently. So, while everyone has the right to their frustrations, we remain committed to providing the best indexation plugin available and will do our best to ensure that security, improvements, and new features arrive with no frustration in the future.

And, of course, if issues remain or are identified. Please let us know. We remain vigilant!

I just updated to the version 4.1.18 and post-sitemap.xml and page-sitemap.xml have 404 error.
The issue is still not solved.

I think some plugins might conflict.

• This reply was modified 1 year, 2 months ago by kiraqqq0.

@kiraqqq0, I think you’re right. To start, can you email the results of the debug tool, so that we can start the troubleshooting process?

@auctollo, I created a new site locally and installed all plugins of my actual site. but the new site doesn’t have the issue.

I get confused….

@kiraqqq0, using the exact same theme or a default theme locally? You can compare the debug results on both installations yourself as well.

I tested again in the actual site and it works fine without issues.

Something went wrong in the previous test. Thank you.

Ok, great. Thanks for your patience.

When so many users say there are issues, why do you persist ? return your code to version 4.1.13 (cancel all next upgrades) and start the upgrades on that code from there, the plugin is old and tested, no major interventions are needed, it is not a security plugin or anything so critical .Nobody wants to risk their website being indexed by google or possible algorithmic penalty

Did you try the latest version @giorgos_d2? I’ve tried all the releases since 4.1.13 that had the issues and always check my sitemap after updating and when I noticed the issues, I just went back to the previous version. I always check every plugin for functionality after updating. I don’t create WP plugins but I imagine its complicated dealing with so many different configurations and plugins available that there will be issues arising from plugin conflicts.

I actually prefer the XML Sitemap Generator 4.1.18 now that it doesn’t have the 404 issues as all the pages and posts have only a single sub-sitemap instead of one for each year & month like the 4.1.13 and previous versions.

As @auctollo mentioned in a previous post on this topic, there were depreciated protocols, new requests for more support and new features which required code changes to make the plugin function and be more maintainable than the code that was previously used (~10 years old). It’s no different than other companies (like Facebook and Google) making changes to their services…why do they make changes when everything is working?

Thanks for your understanding and support @joeparadis2!

@giorgos_d2, security, caching, SEO, and nearly any plugin that generates front-end code for your site all risk creating issues. Until either WordPress has a staging/testing mode or hosts provide staging/test environments for all users or all plugin developers, there are not enough resources to test all permutations of our software, especially when combined with others.

More importantly, the value of our software working without issue is so important to us. The only analogy I can think of is to imagine every bug report was like finding out a family member was in a hospital. Then imagine the only thing you could do to help them was work harder because you can’t go see them and help them directly. Then imagine that there’s a distant family you do not hear from that is also in the hospital. And finally, consider the fact that our family has millions of members. It simply is not possible to take our job/role more seriously, and we’re honored to play this role in your website’s success.

Having said that, there could have been a shorter bug-free path (we don’t want to waste anyone’s time) to the required security, 3rd party support issues, and other changes that we don’t control and must respond to (or risk the project being labeled abandoned and frustrate users through negligence rather than attempted improvement). If this were easier, more developers would do it. What I do know for certain is that search engines do allow sites to recover from mistakes. What they don’t allow is recovery from black hat (intended abuse) of their service.

We will still care about your success even if we’re disliked while we persevere. Everyone who participates in the forums is playing a role in ensuring WordPress adds value to the world for everyone else. We appreciate your sacrifice and efforts.