Keep getting conflicting sitemaps

  • Resolved Lakjin

    (@lakjin)


    7 years, 2 months ago

    When enabling static sitemaps, I keep getting an error of conflict files, even after I tell AIO to delete the conflicting files. This is the reason why:

    [01-Jan-2018 01:57:07 UTC] PHP Warning:  file_get_contents(): SEEK_END is not supported in /home/xxx/public_html/wp-content/plugins/all-in-one-seo-pack/modules/aioseop_sitemap.php on line 1032
[01-Jan-2018 01:57:07 UTC] PHP Warning:  file_get_contents(): Failed to seek to position -1 in the stream in /home/xxx/public_html/wp-content/plugins/all-in-one-seo-pack/modules/aioseop_sitemap.php on line 1032

    How can this be fixed?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    @lakjin

    Thank you for reporting this. This was caused by a PHP 7.1.x change. We have a fix ready for the next release. In the meantime you can delete the files via FTP.

    https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/1428

    Thread Starter Lakjin

    (@lakjin)

    @michael: deleting the files via FTP does not help. The error just reappears after AIO itself creates the files.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    @lakjin
    Switch All in One SEO Pack to “dynamic” in the XML Sitemap settings and delete the files via FTP.

    Thread Starter Lakjin

    (@lakjin)

    Tried that as well. This error happens even if there were no files there before disabling the dynamic feature (i.e., error happens even when AIO itself is the one creating the files).

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    @lakjin

    You’ll want to enable, not disable, the dynamic sitemap functionality. This way AIOSEOP won’t create any files.

    Thread Starter Lakjin

    (@lakjin)

    I understand that. I *want* static files. That is why I’m testing the feature. What I’m reporting to you is the bug when I disable dynamic files. For the time being until this bug is fixed, I have dynamic enable.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    We’ll get this 7.1.x/7.2 compatibility issue fixed in the next release, but also be aware that we’ll be likely removing the static sitemap functionality eventually, and only doing dynamic.

    Thread Starter Lakjin

    (@lakjin)

    Why’s that? Unless a website is adding new content every few minutes, dynamic wastes a LOT of resources. If you are concerned about those high content websites, you can add an option to update the static sitemap every X minutes. Static is way better than dynamic. I don’t want to waste 10 – 100 MB (depending on size of sitemap and website) every time a bot accesses my sitemap.

    Thread Starter Lakjin

    (@lakjin)

    If it helps, think of it as cached WordPress page (static) vs uncached WordPress page (dynamic). No reason to do the latter.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    There’s an issue open here for this explaining it: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/541

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Keep getting conflicting sitemaps’ is closed to new replies.