I have a problem with Calendar running on a small society website. (http://www.awo-norf-rosellen.de/?q=event )

The Problem is, that Calendar shows the wrong current date for unauthenticated users. If i login as admin, the Calendar shows the correct date.
Also if i change something in the "Date & Time" Settings the current date is updated for unauthenticated users too, but then it keeps this date for unauthenticated users until i save the "Date & Time" Settings via the administration system. Obviously other admin dialoges has the same effect than "Date & Time" but i was not able to check which of them in detail yet.

Drupal core version is 5.5
Date Version is 5.x-1.8
Calendar is 5.x-1.7

Thanks in advance for your support

Comments

dystopic’s picture

dystopic commented

Can I provide some additional Information to help to analyze the problem?

karens’s picture

karens commented
Project: Calendar » Event
Version: 5.x-1.7 » 5.x-1.x-dev

That link shows me you're using the Event module calendar, so moving this there. I don't know what version of Event you're using, so you'll have to set that.

dystopic’s picture

dystopic commented

I have updated Drupal core to v5.7 and Event to 5.x-1.0 right now.
I will see if the phenomenon is still existing (i have to wait until tomorrow, to check if the date is now displayed correctly for unauthenticated users, because the db update script altered the db) and i'll post the result.

dystopic’s picture

dystopic commented

The phenomenon is still existing, the event calender shows the wrong date for unauthenticated users.

Anonymous’s picture

Anonymous (not verified) commented

I have exactly the same problem on 2 sites. I have to login every day, go to Event module administration and do something like change the 'Upcoming event block limit', then [Save configuration] - the 'time left to event' and current day then updates for unauthorised users.

Sites are:

www.saphna-professionals.org
www.weconnect.org.uk

Using Drupal 5.5 and Event 5.x.1.0

If you need any further information, please let me know.
As these sites are live and for paying clients, I will continue to go in every day and update.
However, on holiday soon so would love to see it resolved !

Jackie

ejwensley’s picture

ejwensley commented

I recently discovered that my site has this same problem. It is used only for unauthenticated users (I'm the only one who logs in to do stuff administratively). I've received occassional complaints about this, but after I log in and poke around a bit, the problem magically goes away. After reading Jackie's post, I realize mine is behaving identically.

Anonymous’s picture

Anonymous (not verified) commented

By process of elimination (I had 2 sites with the problem and 2 development sites working ok), I found that on Administer/Site Configuration/Performance page, that the sites where Page cache is 'Disabled' work ok.

I changed the Page cache setting on the problem sites from 'Normal' to 'Disabled' and so far it looks like it has rectified the problem.

Perhaps the Event module was working fine all along, but that the unauthenticated user was being presented with a cached page therefore it looked like the current date wasn't progressing ?

dystopic & ejwensley - it would be good to know if this works for you too ??
Jackie

ejwensley’s picture

ejwensley commented

Thanks for the update. I suspected it might be this. I disabled the cache and will check in on it over the next couple days. I'll post back later with results.

dystopic’s picture

dystopic commented

@McJax Thank you very much for this hint!

I disabled caching and i'll investigate over the next days if this solves the problem.

dystopic’s picture

dystopic commented

Disabling caching solved the problem, the current date is updated for all users now without playing around in the configuration dialogs.

On my site this behaviour of the Event module is no big issue because i have not that mich traffic on the site, but i assume that disabling the cache will be a big problem on high traffic sites.

japerry’s picture

japerry
Location KOMK
commented
Status: Active » Closed (outdated)

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