Am 02.05.2012 10:05, schrieb Thomas Bruederli:
Michael Heydekamp wrote:
If we would install 0.8-beta and the problems would seem (!) to be gone, we wouldn't still know why exactly. And we would never know if at some stage they wouldn't appear again. In some way I'm sort of "happy" to see those problems, as this is the only chance to track them down. Getting rid of bugs/problems by coincidence would be a somewhat, uh, sloppy way.
We already tried to track them down with your current version but obviously without success. In the meantime we even made some changes to improve the session validation and they might already have solved your issue as well.
Uh, where...? Didn't know that. I was just aware of a fix in the autosave routine, which I haven't applied yet (but will do so most likely this evening). Hopefully this fix will be compatible with 0.7.2 (A.L.E.C said it should).
Either you install the latest SVN in order to verify or we have to provide patches which you can apply and test again.
Well, if you don't mind I would prefer this way for the time being. Simple reason: I can fiddle around with patches myself without having to bother my main admin. A new installation (for me) is a bigger task which I can't/won't do myself.
If you can send me those patches (off-list?), I'll be happy to apply them shortly.
With regards to "latest SVN": In a previous message you said we should install 0.8-beta, so this advice is now superseded with "latest SVN", right? Just wanna be sure...
- Start using that fresh installation of Roundcube with your IE8. If
you still experience session problems, try with other browsers such as Firefox or Chrome.
Ok, should the problems persist after appyling the patches (and/or installing the latest SVN), I'll try it with a different browser.
- Enable the config option 'log_session' and check
<roundcubedir>/logs/session if you ever loose a session.
Done. But just a few minutes ago (and two hours too late), as I had a session timeout again two hours ago. Hopefully next time I'll be able to report something meaningful.
I'm sure there'll be another session timeout to be logged :-)
Hopefully. :-) But we may have another issue here: Although I enabled 'log_session', there is still no file "session" in the logs directory. Are entries to this file written in case of any errors/timeouts only...? So far I haven't had another session timeout since I enabled this option, but I also haven't used RC heavily since then - due to the job I'm being paid for. ;) But now I'm waiting any minute for another timeout and it would be a pity if it would happen, but wouldn't get logged.
If there is anything else for me to do apart from just enabling the option, let me know.
Thanks for still being attentive,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany