By coreyp_1 on

Am I missing something here? I have cache enabled, which is a necessity on my site. The problem is that when an anonymous user sends me a message using the contact form, the message "Your message has been sent" is saved in the cache, and then every anonymous user sees this message until the cache expires.

Is there a setting somewhere that keeps a page from being cached when a message is being displayed? So far, the only thing I know to do is either disable the cache (not a good option in this situation) or visit my site once a day as an anonymous user, and clear the cache if necessary.

Surely there's a better way to do this. Any suggestions?

-Corey

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

Are you not logging off betwen sessions ?

coreyp_1’s picture

coreyp_1 commented

Yes, I log off, but I don't necessarily check my website every day. It e-mails me when specific things happen, of course, but that is not the issue.

For example, I checked my site on Saturday morning and all was well. I left town, but somebody sent me a message via the contact form. The message got cached, and now everyone that visited my site saw the message, and wondered what was going on.

I got back in town Sunday night and found a message from one of my moderators who was worried about a "weird message" appearing on the front page. I recognized the problem (because it happened once before with anonymous comments) and cleared the cache.

My point is, the problem should never have happened. The page should not have been cached if there was a message being displayed. Is there a work-around for this?

- Corey

vm’s picture

vm commented

rummaging through the modules this evening, I noticed a cacheexclude module , may be worth investigating

Pinolo@www.drupalitalia.org’s picture

Pinolo@www.drupalitalia.org commented

I have the very same issue. The bad part being that also confirmation messages after subscription are affected, so a user's email address remain exposed as long as cache lasts. Very bad!
I'm filing an issue about this: http://drupal.org/node/168909
At least now I know it's not been introduced with 5.2.