Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Is it happening?
Comment | File | Size | Author |
---|---|---|---|
#10 | cacheexclude7.patch | 2.95 KB | andypost |
Comments
Comment #1
xeontheone CreditAttribution: xeontheone commentedI hope!
Comment #2
chawl CreditAttribution: chawl commentedsubs
Comment #3
Crell CreditAttribution: Crell commentedI have no immediate plans to do so, but I'd like to see it happen, too. :-) Patches welcome before I find time to do so.
Comment #4
andypostMaybe join forces with #334658: Port Cache Disable to Drupal 7
Comment #5
rodrigoaguilerasubs
Comment #6
valderama CreditAttribution: valderama commentedsub
Comment #7
anonym-developer CreditAttribution: anonym-developer commentedsub
Comment #8
socialtalker CreditAttribution: socialtalker commentedsub
Comment #9
skizzo CreditAttribution: skizzo commentedsubscribing
Comment #10
andypostLooks like this not hard to port, variable
cache
still works in drupal_page_footer()Comment #11
Les LimJust applied and installed #10 on a Drupal 7.8 site. The path exclusions appear to be working fine. Haven't tested the content type exclusions yet, though.
Setting to RTBC, mostly to indicate that this would suffice as an initial 7.x dev version from which other issues could be created in the queue.
Comment #12
Crell CreditAttribution: Crell commentedI agree. :-) I've committed and pushed a 7.x-2.x branch. Thanks, anypost!
I created a release node for the dev branch. It should show up soon. I am going to leave this thread open for a bit for feedback, but we can close it once we're sure the dev release works and I tag a 2.0 stable.
Comment #13
andypostGreat! Are dev releases are allowed to be viewed at module page in settings?
Comment #14
Crell CreditAttribution: Crell commentedYep. I just needed to wait for the file to be generated before I could flag it to display. :-)
Comment #15
hardcoding CreditAttribution: hardcoding commentedworks for me with node/123 entered in the textarea
Comment #16
pascalduez CreditAttribution: pascalduez commentedWorks fine here, I'm excluding the frontpage
<front>
, where I have random content.Comment #17
Les LimNow that this port is officially a branch, let's close this issue and encourage bug posting in separate issues.