Am 19.03.2013 20:26, schrieb Michael Heydekamp:
It worked again. Now I have to find out why and under wich circumstances it didn't work yesterday. :-/
Stay tuned.
@alec:
After some more local tests, I must admit that even I can't reproduce the issue anymore that I encountered last night after your fix. But I swear that I had the issue, the messages are still existent here.
Furthermore I can confirm that the fix itself now seems to work as it should. Thanks again.
But strange, how can that happen...?
We are currently doing a git-pull with a cron job every night. My tests have apparently taken place at approx. the same time while the cron job was running (which I wasn't aware of). So some files may have been updated already, others not (although there were only two files affected). Or I should have done a fresh login before testing anything (which I didn't).
May this be the reason...?
Sorry for the hassle that I may have caused.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany