This is the only module on my site that says it's not compatible with aggressive caching. I would like to understand why that is, and what the potential problems are if I activate aggressive caching anyway.

Is this about updating the sitemap? If yes, I can live with it only being updated once an hour when cron runs. What other problem could there be? I realize it's still a dev version for D6, but it would be great to be able to use the most aggressive performance settings.

Comments

darren oh’s picture

darren oh
Primary language English
Location Lakeland, Florida
commented
Status: Active » Closed (won't fix)

Drupal lists any module that implements hook_exit() as incompatible with aggressive caching. XML Sitemap uses this hook to ping search engines when the site is updated. However, since caching only affects anonymous users, only updates made by anonymous users (such as anonymous comments) are affected.

eagereyes’s picture

eagereyes commented

I see, thanks! Aggressive caching it is, then.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: xmlsitemap » Code
Status: Closed (won't fix) » Fixed

There is no way to say to Drupal if a module is compatible with aggressive caching; Drupal just checks if a module implements some hooks (one of them is hook_exit()) amd report the modules which implement them to be incompatible with that type of caching.

XML Sitemap should not have problems on working with aggressive caching. If you have any problems, just change the type of cache being used.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.