Not Doing Automatic Event Updates

I have the same problem : no update automatic in the widget
Only clear cache manually !

Http ://www.vytajog.fr

What happens if you change your cache time to a lower value? Does it work better when you do that?

Actualy cache time is 21600 (6h)

Nick, I just now reset “Cache Duration” to 1. I did follow that up right now with “Update”. That does update the events, but as I noted earlier just using “Update” itself with no “Cache Duration” change does do a manual update. So I will have to wait 24 hours before I can tell whether automatic updates occur or not.

Nick, it is now showing no events and kicking out the following error message. “Connection time-out Please ensure your feed URL is correct. There are currently no events to display.” I’ll try changing it to 3600, which is half of what it was originally.

Nick, using 3600 does not give the Connection Timeout error message but it does still say “There are no events to display”. And that “There are no events to display” message takes a long time to appear. Interestingly during that long wait for that message to appear, our top of page banner slideshow spins away trying to load also. And the correct slideshow appears at about the same time as the “There are no events to display” message appears.

At this point, I have changed the Cache Duration back to 7200 which was what it was when I first communicated with you yesterday. And things are back to how they were working yesterday. ie All eleven events appear normally with no delay and the banner slideshow is back to working normally. It will probably take some time (24 hours?) to see if the automatic event updates work any differently.

Nick, with the Cache Duration set back at 7200 the automatic updating of events is still not working. Since changing that value to smaller values just caused additional problems, I have now tried setting it to a larger value, namely your default number of 43200. We will see what happens.

In my initial post to you, I listed all my feed settings and widget settings. What I did not give you was the “short code” settings that version 2 automatically generated from the 0.7 short code settings. I list those below. Do they look right?

As displayed on visual tab:
[event-title]
[if-not-all-day]
[start-time]-[end-time]
[/if-not-all-day]
[if-location]
Location: [location]
[/if-location]

As displayed on text tab:
<p class=”gce-list-event gce-tooltip-event”>[event-title]</p>
[if-not-all-day]
[start-time]-[end-time]
[/if-not-all-day]
[if-location]
Location: [location]
[/if-location]

Just released patch 2.0.3.1.

If you decide to try it please let us know if it fixes the issue. If not, please give us details and we’ll try to fix it soon.

Thanks.

Just to summary what I have seen so far on version 2.0.2
Cache Duration=1 – Kicks out error message “Connection Timeout”
Cache Duration=3600 – Clears cache and then neither auto or manual updates work.
Cache Duration=7200 – Clears Cache and then manual update works but auto update still does not work.
Cache Duration=43200(the default) – Clears Cache and then manual update works but auto update still does not work.

I have now just installed your latest version 2.0.3.1
I don’t see any immediate auto update (ie Deletion of yesterday’s events and replacement of those events with future events which already exist on the calendar at Google.)
You didn’t say, but does the latest update to version 2.0.3.1 requires a “Clear Cache” command after installing it in order to implement it?

Yes you will probably need to clear your cache after the 2.0.3.1 upgrade. Mainly because it fixes some issues with the caching so to reset it completely on your side should help.

Sometime between yesterday morning when I installed 2.0.3.1 and this morning, our site did its first auto event update since we first installed version 2.0 eleven days ago. And that was without even clearing the cache. Based on your comment above to clear the cache to reset it completely, I will do that also. Thanks

It is now OK :the cache is automaticly updated
Thanks

Great glad to hear that!