You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the new autocache feature only accepts the sitemap.xml file from the primary domain. What about other domains in a multisite installation? I have 4 soon to be 5 sites in my multisite installation. I know I can put the individual URLS in a List of URLs to Auto-Cache, but that could be hundreds of pages and posts. In multisite, each domain has its own sitemap.
The text was updated successfully, but these errors were encountered:
Yes, that is correct; i.e. this is a limitation currently. I think it would be good to support all child blogs in a future release of QC Pro however. I believe @raamdev is considering this as a feature request.
Until then, one way to deal with this is to create a Sitemap Index on the Main Site. Quick Cache supports both a Sitemap and/or a Sitemap Index; i.e. QC will traverse the entire Sitemap structure recursively upon encountering a Sitemap index.
@jaswsinc Thank you for the comments and for confirming the limitation.
@vfontjr Thank you for the feature request! I agree the Auto-Cache Engine should be a bit more intuitive, or at least more instructional, with regards to supporting child blogs. I will add to this to the todo list for a future release.
raamdev
changed the title
AutoCache Only Works for Primary Domain in Multisite?
Feature Request: Improve UI for Auto-Cache Engine in multisite to clarify child blog caching
Jun 10, 2014
It appears that the new autocache feature only accepts the sitemap.xml file from the primary domain. What about other domains in a multisite installation? I have 4 soon to be 5 sites in my multisite installation. I know I can put the individual URLS in a List of URLs to Auto-Cache, but that could be hundreds of pages and posts. In multisite, each domain has its own sitemap.
The text was updated successfully, but these errors were encountered: