Closed (outdated)
Project:
Cache Expiration
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Oct 2011 at 00:30 UTC
Updated:
13 Dec 2016 at 15:48 UTC
Jump to comment: Most recent
Comments
Comment #1
mr.j commentedI have noticed that too. Its not an easy one to fix the way the module just sends an array of URLs when it calls its hook. Without changing that I assume you would have to specify each page as a separate URL with the ?page=1, ?page=2 etc appended.
If you purge whatever cache you use with wildcards for example you could inadvertently clear a whole bunch of other pages. eg When a user updates a forum node on our site, the taxonomy part of this module purges the /forum URL as well as the actual forum node page like /forum/discussion/topic/12345. But if you purged /forum/* that would clear every page in the whole forum. So you need to either specify the pages individually, or somehow recognise that the URL is for a specific node and not a taxonomy term or homepage, and then apply a wildcard to it.
Comment #2
mr.j commentedI have some code here that does this when using core's db caching:
http://drupal.org/node/1308252#comment-5133192
Its not perfect and relies on the ordering of the URLs passed through by the module, but so far it works great for my needs.
Comment #3
liam morlandDrupal 6 is no longer supported. If this issue exists in Drupal 7, please reopen and provide details.