• One of the settings in the Page Cache settings is for the sitemap URL in the Cache Preload section. Are you able to just enter a relative URL here, such as /sitemap_index.xml? I also noticed that the W3TC settings file uses {wp_content_dir} for other settings. Could I input the following in the Page Cache setting field: {wp_content_dir}/../sitemap_index.xml ? If I do that, the exported setting seems to output as expected (“pgcache.prime.sitemap”: “{wp_content_dir}\/..\/sitemap_index.xml”), but I’m not sure how to test if this setting is properly configured and W3TC is using the sitemap to prime the cache. How can you test if the cache has actually been primed?

    My goal is to have a general settings file that I can just import with each new site without having to change this setting to the correct domain each time.

    Thanks for any advice or suggestions!

Viewing 2 replies - 1 through 2 (of 2 total)
  • I saw a settings/set up post where the example image showed the guy using a relative url, but I also cannot find any verification that it works correctly. Have you confirmed that relative url’s are acceptable?

    Thread Starter joejoe04

    (@joejoe04)

    I can’t say that I’ve confirmed that relative URLs are acceptable, unfortunately. Would really be nice if the options page stated the acceptable or required format(s). It would also be nice if they just answered people’s questions on here. For being such a popular plugin, I am very surprised at how many questions go unanswered by them. This is not the first question I’ve asked which received no response.

    I ended up using {wp_content_dir}/../sitemap_index.xml. If you view the settings file, other options use the {wp_content_dir} variable and ../ is valid URL syntax, so I’m just assuming it’s okay. I still don’t know how to test whether this is properly directing this option to my sitemap_index.xml file to specify which pages/posts to prime though.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cache Preload Sitemap URL’ is closed to new replies.