This strange header problem still exists. No matter what I do, I cannot get rid of this error.
In simulation this error never occurs, but in my live virtualized webmailserver this error occurs all the time. This is not a multicore issue (read somewhere that PHP and multi threading causes setlocale issues in PHP with multicore systems), I've tried booting the virtual server with a single core, but the error remains. What to do? Thx, /PGE ----- Forwarded Message ----- From: Pro Green European <pro_green_europ...@yahoo.com> To: "imp@lists.horde.org" <imp@lists.horde.org> Cc: Sent: Wednesday, November 23, 2011 3:40 PM Subject: [imp] Fw: Fw: Strange header problem in IMP 5.0.14's message window. I've attached a screenshot of the issue. It seems that it is only the dynamic ui that is affected by this issue. I've also aplied all patches that were released recently (for example imp 5.0.15). Regards, /PGE ----- Forwarded Message ----- From: Pro Green European <pro_green_europ...@yahoo.com> To: "imp@lists.horde.org" <imp@lists.horde.org> Cc: Sent: Wednesday, November 23, 2011 3:27 PM Subject: Re: [imp] Fw: Strange header problem in IMP 5.0.14's message window. Hi. Thank you for your reply. I've done so quite many times. But it does not help. Could this be a memcached issue on the server? Regards, /PGE ----- Original Message ----- From: Michael M Slusarz <slus...@horde.org> To: imp@lists.horde.org Cc: Sent: Wednesday, November 23, 2011 9:36 AM Subject: Re: [imp] Fw: Strange header problem in IMP 5.0.14's message window. Quoting Pro Green European <pro_green_europ...@yahoo.com>: > I've worked out which procedure is causing this strange header problem. > > Example: > - Log in, do not change any settings in the login window. > - Log out. > - Change the language. > - Log in. > - Log out. > - Change back to the first language you had selected when you first logged in. > - Log in. > - Select a message. > - Double click it. > - Now the headers remain in the wrong language. > - The same goes for writing new messages. > > Know bug? It's not a bug - or at least I can't reproduce. Sounds instead like a browser cache issue. At a minimum, you should clear your browser cache. michael ___________________________________ Michael Slusarz [slus...@horde.org] --IMP mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: imp-unsubscr...@lists.horde.org -- IMP mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: imp-unsubscr...@lists.horde.org -- IMP mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: imp-unsubscr...@lists.horde.org -- IMP mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: imp-unsubscr...@lists.horde.org
