-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect when XML Sitemap URL does not exist for Auto-Cache Engine #555
Comments
@jaswsinc I think we can do better than a note: We should just check the XML Sitemap URL and see if it returns the appropriate status code. If it does not, we show a warning message indicating that the XML Sitemap could not be found and suggest installing the Google XML Sitemaps plugin, or clear the XML sitemap field and use the list of URLs instead. (Bonus points if we can also validate that a valid XML Sitemap exists at the URL when then URL returns an non-404.) |
👍 |
Next Actions
|
@kristineds While working on this issue you can learn more about |
Next Pro Release Changelog:
|
@raamdev, @kristineds, @jaswsinc, This is a great new addition. (I am just trying out the new RC.) Thank you! I had enabled this before without realizing that I need to use a plugin to create an xml sitemap. I have now installed Simple Wp Sitemap (https://wordpress.org/support/plugin/simple-wp-sitemap) and it seems to be doing the job (without pinging Google, which other sitemap plugins do, and which I don't want). But now I have a question. This plugin allows me to add other pages outside WordPress (e.g. static html files) to the sitemap. If I do this, does it mean that ZenCache Pro will then be able to cache them too? |
Nice! Thanks for the link. I'll bookmark that one.
I'm afraid not. If it's in the sitemap, ZenCache may attempt to load that page and cache it, but that attempt will fail gracefully since WordPress and ZenCache are not actually loaded in static HTML files. |
@jaswsinc, That's what I suspected. Thanks for the explanation! |
ZenCache v151114 has been released and includes changes from this GitHub Issue. See the v151114 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#555). |
Forked from #512 (comment)
@jaswsinc writes...
The text was updated successfully, but these errors were encountered: