This plugin now “takes over” other site pages… How do I stop this?

  • Resolved roam92

    (@roam92)


    9 months, 1 week ago

    For over a decade, my site has had a human-readable sitemap page under /complete-sitemap.html … It’s quite a common practice to provide a “table of contents” directory to a website for visitors.

    But now, since one of the recent updates to XML Sitemap Generator for Google (after version 4.1.13), this page has been taken over by your plugin and now just shows a blank/empty “XML Sitemap.” It has no use or value to humans or crawlers.

    My site’s actual sitemap for search engines is under /sitemap.xml and this works properly.

    But how do I stop your plugin’s new behavior of replacing the valid & useful contents of /complete-sitemap.html and restore it for my visitors, as it was before?

    Thank you

Viewing 3 replies - 16 through 18 (of 18 total)
  • Plugin Author Auctollo

    (@auctollo)

    @roam92 this issue was born of logic that existed in the project since before we took over it’s development, fixing the underlying bugs (that no one had noticed), improving performance and a variety of other improvements led to this issue.

    Would you consider using this code as a workaround?

    function sitemap_fix_rewrite_rules( $wp_rules ) {
        unset($wp_rules['.*-sitemap(?:\d{1,4}(?!-misc)|-misc)?\.html$']);
        return $wp_rules;
    }
    add_filter( 'rewrite_rules_array', 'sitemap_fix_rewrite_rules', 1, 1 );
    Thread Starter roam92

    (@roam92)

    Hi @auctollo

    Thank you for your reply. Are you saying the plugin cannot be changed or fixed, and are instead asking me address the problem only on my own site?

    I’m not sure I understand the purpose of the plugin generating a blank/empty sitemap where my complete-sitemap.html “Table of Contents” overview page should be:

    And again, this never used to happen – it is new behavior since version 4.1.13. Everything worked fine before then. However, the redirects in your “add_rewrite_rules()” function changed in between versions 4.1.13 and (the current) 4.1.21.

    Could you possibly explain further? Thanks!

    Plugin Author Auctollo

    (@auctollo)

    We’re working on removing rewrites from the plugin entirely.

Viewing 3 replies - 16 through 18 (of 18 total)
  • You must be logged in to reply to this topic.