User doesn't have time/desire to debug, no one else seeing this, no 
feedback to go on.

The timestamp parameter is just used to track what day/month/period 
you were viewing - it has nothing to do with the event that's 
viewed/loaded.

The failure appears to occur when week.php emits, in a link to 
viewevent.php, a "timestamp=" parameter which preceeds the value of 
the event_modified field of the event in question. Does that make any 
sense? Where in the code does that timestamp parameter get emitted? 
And what is its purpose?

Well, I'm not aware of anyone else seeing this. You can probably 
disregard the null event problems, since that seems a side effect of a 
missing parameter. Focus on figuring out why you're getting prompted 
for a login; that seems like the root of the problem.

To be honest, I was hoping I could take the role of a user, rather 
than a developer here. I really just want my calendar to work. But if 
the bug is unique to me...



What's happening precisely is that whenever I attempt to view an 
event, I am being prompted to log in, at which point I am taken to an 
event view which is viewing a null event object. (Thus the dates in 
1969 and no other information.) If I try to edit the event, 
editevent.php crashes trying to call $event->getTitle() on line 26, 
complaining of a null object.



I will try to debug further, but the point of having a calendar app 
was to streamline my workload, not add debugging to it, so it may take 
awhile.

You need to put in some debugging time/code to see what's going on; 
assuming that other applications work for you and you have cookies 
enabled, which it sounds like, then this isn't anything I recognize.

Any attempt to use Kronolith currently causes me to become logged out 
of Horde after the first or second click. (I don't get any kind of 
logout message, it just asks me to log in as if I had no cookie at 
all. Note that my Horde logins are processed through IMP, which asks 
my IMAP server, if that's relevant.)



This may be related to an event I recently entered which appeared to 
become corrupted; It appeared fine in the calendar display, but 
clicking on the event (and then logging back in) caused it to show up 
at occuring in 1969 with no location or name. (The event had correct 
information in the MySQL database, so I'm not sure what was going on 
here.) I successfully deleted the event, at which point the current 
problem started: trying almost anything causes me to get logged out, 
with little rhyme or reason.