Geeklog Forums

Hi,

I have LG 1.3.9RS1 running happy on my site here. However, browsing my site as a non-logged in user, I noticed that some events spanned multpile days on the calendar, for example the event 'Bijeenkomst Instructie Collectief' .
After logging is as a member, the same event appears as a single day event (one evening, to be exact). When I log in as event admin, the event turns out to be really one evening, and not a multiple day event.

In short, non-members see a faulty calendar.

What is the problem here?

I tried reproducing the problem using the data for that event, but it only shows as a one-day event for me (both locally in 1.3.10 and on demo.geeklog.net, which is still on 1.3.9sr2).

Could you extract the data for that event from an SQL dump (use Geeklog's backup function) and either post it here or email it to me?

bye, Dirk

Hello Dirk,

I have been trying to reproduce the problem om your demo site, and I can't..
Could this issue have something to do with this issue?
On the demo site I can reproduce the issue described in that thead.

I have send an email containing the event table from my site..

But this doesn't cause the event to be displayed over several days.

The above problem has been fixed in 1.3.10, btw.

bye, Dirk

I have found the reason for this behavour. I just cannot solve it..

Do the following steps:
0) log in as (event) admin
1) create a public event on 15th december 2004. from 8pm to 11 pm
2) create a private event (no Anonymous users) on the 16th december 2004, 8pm to 11 pm
3) log out and check your calendar.
--> You will see a public event from 15 all the way to the 16th of december...
4) log in again and check your calendar.
--> You will see two events, one public on 15, on private on 16.. (correct)


I am not sure if the event start/end times have any influence, I have not checked that.

This odd behaviour is also on the geeklog demo site!

Willem Jan

Thanks! I was about to email you to tell you that I couldn't reproduce the problem ...

bye, Dirk

Just FYI: It is also reproducible in Geeklog 1.3.10, but has already been fixed in CVS (i.e. fixing another bug also fixed this one).

bye, Dirk