Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter douw0119

    (@douw0119)

    I investigated a little further into the source code. Inside

    PgCache_Plugin_Admin.php

    in function

    parse_sitemap,

    the line

    $urls = array_merge( $urls, $this->parse_sitemap( $loc ) );

    returns empty arrays.

    • This reply was modified 1 year, 5 months ago by douw0119.
    • This reply was modified 1 year, 5 months ago by douw0119.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @douw0119

    Thank you for reaching out and I am happy to help!

    Priming from sitemap?https://www.aquaperm.co.za/sitemap.xml?entries 1..10
    Success: PageCache Priming triggered successfully.

    So the message says that the priming was succesfull.

    Can you please share where do you see that the parsing was not completed? How many pages per run have you set in the Preload option and have you tried using:
    wp w3-total-cache pgcache_prime [--start=<start>] [--limit=<limit>]

    Thanks!

    Thread Starter douw0119

    (@douw0119)

    So the message says that the priming was succesfull.

    From other posts here I assumed that all the pages it primes will be echoed to the console. Please correct me if I’m wrong. As mentioned in the origional post, the ‘root’ sitemap consists 6 more sub-sitemaps which don’t seem to be parsed.

    Can you please share where do you see that the parsing was not completed?

    Only pages manually visited show op in ./wp-content/cache/page_enhanced/www.aquaperm.co.za.

    Might be that I’m too impatient in expecting them to be there in 30min or so. I’ll flush the cache and check again, employing more patience.

    Thread Starter douw0119

    (@douw0119)

    Might be that I’m too impatient in expecting them to be there in 30min or so. I’ll flush the cache and check again, employing more patience.

    I think that was it. I have it caching 10 pages every 10 min, and it seems be bo doing it’s thing. I had the setting at 100 pages every 15 min, maybe that’s too many pages at once.

    From other posts here I assumed that all the pages it primes will be echoed to the console.

    Obviously I was wrong on this one.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @douw0119

    Thank you for your feedback.
    Yes, you need to wait a bit depending on the settings in the W3TC cache preload.
    It’s advisable not to prime a lot of pages at once to avoid server overload.
    Glad to know everything is working as expected.
    Thanks!

    Thread Starter douw0119

    (@douw0119)

    Just to report my final finding.

    AIOSEO produces an incompatible sitemap with loads of [CDATA] tags all over the show, which W3TC doesn’t strip out.

    I reverted back to XML Sitemap Generator for Google, now it primes properly.

    BTW, I had to restart httpd to get the new sitemap loaded.

    Regards.

    Douw.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘PRIME SITEMAP NOT PARSING’ is closed to new replies.