Is it happening?

CommentFileSizeAuthor
#10 cacheexclude7.patch2.95 KBandypost
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

xeontheone’s picture

I hope!

chawl’s picture

subs

Crell’s picture

I 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.

andypost’s picture

Title: Drupal 7 port » Drupal 7 port of CacheExclude
rodrigoaguilera’s picture

subs

valderama’s picture

sub

anonym-developer’s picture

sub

socialtalker’s picture

sub

skizzo’s picture

subscribing

andypost’s picture

Status: Active » Needs review
FileSize
2.95 KB

Looks like this not hard to port, variable cache still works in drupal_page_footer()

Les Lim’s picture

Status: Needs review » Reviewed & tested by the community

Just 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.

Crell’s picture

Status: Reviewed & tested by the community » Needs review

I 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.

andypost’s picture

Great! Are dev releases are allowed to be viewed at module page in settings?

Crell’s picture

Yep. I just needed to wait for the file to be generated before I could flag it to display. :-)

hardcoding’s picture

Version: 6.x-2.x-dev » 7.x-2.x-dev
Status: Needs review » Active

works for me with node/123 entered in the textarea

pascalduez’s picture

Works fine here, I'm excluding the frontpage <front>, where I have random content.

Les Lim’s picture

Status: Active » Fixed

Now that this port is officially a branch, let's close this issue and encourage bug posting in separate issues.

Status: Fixed » Closed (fixed)

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