Closed (outdated)
Project:
Event
Version:
5.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Mar 2008 at 16:41 UTC
Updated:
13 Apr 2018 at 21:35 UTC
Jump to comment: Most recent
I have installed the modules event, basic event, event all day, event repeat and event views (all 5.x-1.0) on a production site. Caching mode is set to normal. The calendar and upcoming events are displayed in the right sidebar. Cron is running every hour.
Since some time the calendar display is not updated when the day changes. I don't know if the behaviour is since drupal update (I'm currently on 5.7) or if it has always been (I really didn't notice it). It could also be that the display is only corrected, if there is an event on the day.
But when I disable and re-enable caching the display is correct (for today).
What can I do?
Comments
Comment #1
pepe roni commentedAs for two weeks no respond to my issue has been returned (the maintainers may be busy with porting to D6?) I changed the properties of this issue. I now think that the event module is not cache compatible and that you have to switch caching off, if you want to use the calendar block and the upcoming events block. Thus the event module is unusable in production sites!
Perhaps the maintainer of this module may respond?
Comment #2
killes@www.drop.org commentedThis is a well known issue.
On production sites the cache is usually cleared oftenenough that it doesn't matter.
Comment #3
pepe roni commentedIf that is the case, can you tell me the issue numbers, please?
If it doesn't matter, why did I post this issue then, just for fun? How can I force to clear the cache for events (e.g. by running a cron job) when
a) the date changes?
b) an event has timed out?
Comment #4
enkara commentedI am with you druppi. I've had the same issue. I've had to disable the caching after some time searching why was this happening. I think it should be written somewhere to prevent people loosing time. I'm very happy that this module exists and I thank the programmers, but I think an issue like this should be in the readme or somewhere.
Comment #5
antipix commentedsubscribing, i'd like to find a way to prevent the upcoming events block from being cached
[edit] perhaps we could use the block cache module to make the upcoming event block not being cached ?
[edit2] trying to add
at beginning of function event_block_upcoming($limit = 6)
don't know if it's a good idea ^^
[edit3] i guess that works
[edit 4] not working...
Comment #6
antipix commentedtried to add
at beginning og event module...
Comment #7
kleung11 commentedBLOCK_NO_CACHE is only available for Drupal 6, so this is still a problem with 5.x.
Comment #8
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.