I have currently having a problem where the "upcoming events" side bar as well as the visual calendar are frozen on a particular day. However, if I navigate to any other page, the date updates its self to the correct date. If you navigate back to the home page, everything is messed up again.

Anyone got any thoughts on why this is happening?

Example: http://tsmonline.org

-TG20

Comments

tg20’s picture

tg20 commented

Note: This problem also does not exist when one is logged in.

tg20’s picture

tg20 commented
Status: Active » Closed (fixed)

It appears that running the update prompt fixed the problem. I will follow up if the problem re-appears.

tg20’s picture

tg20 commented
Status: Closed (fixed) » Active

I have to re-open this topic because it has appeared to re-establish.

markDrupal’s picture

markDrupal commented

I have seen this problem before. I think it is because when you turn on the Cache, drupal will cache the front page for anonymous users. When you log in you force drupal to build a page that is specific to you, but it doesn't overwrite the cache.

I am not sure when the cache is destroyed for anonymous users. I think if you are to post a new node it would rebuild the cache and update your events block.

You might have better luck creating your own block for events using the views module.

Anyone know when the cache is purged for the Upcoming Events Block?

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Closed (won't fix)

The cache is destroyed when new content is posted or existing content is modified. If this does not happen too often, the upcoming block will contain stale data.

You can either post more stuff or disable the cache.

tg20’s picture

tg20 commented
Status: Closed (won't fix) » Closed (fixed)

Thanks. That all makes sense.

-Tg20

gtcaz’s picture

gtcaz commented

Is there a way to force the cache to refresh? I have some fairly static sites that frequently get out of date. I don't like to disable the cache because the server they're on in kind of slow at the moment.

killes@www.drop.org’s picture

killes@www.drop.org commented

Just edit and save any node (without makeing changes).

gtcaz’s picture

gtcaz commented

@killes, thanks. My problem is that I have a few sites that I don't remember to mess with each day. That leaves this block in a stale condition. I think there should be a way to force the cache to update (say at least once a day, as the date changes in the default timezone perhaps), even if a node isn't updated.

Cron never sleeps, and doesn't forget.

gtcaz’s picture

gtcaz commented
Status: Closed (fixed) » Closed (won't fix)

I'm changing this to "Won't Fix" -- I think it's clearly a bug, but it looks like it's not a concern to most (who have sites that are updated at least daily).