• Resolved doffine

    (@doffine)


    Hello Yoast team,

    we just noticed quite a bad behaviour of the Yoast plugin regarding WordPress’ own sitemap.

    Here is how to reproduce it:

    1. Take a WordPress installation that never has seen the Yoast plugin and head to DOMAIN.TLD/sitemap.xml or if you wish DOMAIN.TLD/wp-sitemap.xml: You will see WordPress’ own sitemap structure.
    2. Then install and activate Yoast. You will see that it replaces the sitemap with its own one – as it should be. Everything ok until now.
    3. Now deactivate Yoast. One would expect that WordPress’ own sitemap is back then, but it isn’t. Instead there is some kind of an empty page, but no sitemap anymore.
    4. Even if you uninstall Yoast the original WordPress sitemap doesn’t come back.
    5. Then in the Dashboard go to Settings > Permalinks and simply click on “Save changes” to refresh WordPress’ Permalink structure without any changes.
    6. After this the original WordPress sitemap is back again.

    Conclusion
    If you have ever installed Yoast and uninstalled it, you probably have no sitemap any longer without even knowing this, until you refresh your permalink structure for some reason. There should be many former Yoast installations that now don’t have a sitemap anymore.

    This problem should be solved immediately so that upon Yoast deactivation it is made sure that the original sitemap is back again.

    Greetings,

    -doffine

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Suwash

    (@suascat_wp)

    @doffine

    Thank you for bringing this issue to our attention! I’m sorry that our plugin caused a problem on your site. A bug report has been created and is under review by our product team.

    Workaround
    At this time, there is only the workaround to update the permalink setting like you mentioned.

    What’s next?
    Our product team will assess the severity of the issue and assign a priority level to the report. Our developers work on the highest priority issues first. We cannot give you an estimate of when they’ll start working on the issue.

    If you have any further information that may affect the prioritization or help our development team solve this bug, please leave a comment or subscribe to the GitHub report to get updates on the issue.

    Thread Starter doffine

    (@doffine)

    Hello @suascat_wp,

    wow, the GitHub bug report is 2 1/2 years old. Yoast knows about it for 2 1/2 years and doesn’t fix this. Is it because users that deinstalled your plugin are no longer in your focus that much?

    You put up with many users relying on having a sitemap but don’t have one because in the past they had installed your plugin. Don’t you think you should change the “severity: minor” status? Else there might be further years going by.

    Yoast gets so many little and functional updates every month which – in my humble opinion – could wait a day longer instead. Something like such a bug really shouldn’t wait for years to be fixed. The more time goes by the more users with this problem and not knowing about it at all will be generated by your plugin.

    And think about those users: They have deinstalled your plugin and thus an update of your plugin with a fix for this bug won’t reach them any longer. So you put up with producing such former users. The longer you wait, the more users with this problem will be there. I simply cannot believe this.

    Greetings and thanks for your – beside this – great plugin and your work,

    -doffine

    Hey Doffine,

    Thank you so much for your elaborate reply, which we do appreciate. I had a look at the initial report and I agree this is something to be picked up. I’ll move it forward and ping the dev team to investigate why it isn’t flushing or working by default – which it should.

    Workaround: flushing your permalinks manually does fix it, but this shouldn’t be necessary so we need to improve that.

    Thank you once again for letting us know!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bug report: Yoast enduringly disables WordPress’ own sitemap’ is closed to new replies.