Re: Re: Re: Re: Fatal error in calendar
Benoit Hamet <[email protected]> Thu, 06 May 2010 23:30:49 +0200
| Newsgroups | gmane.comp.web.phpgroupware.general |
|---|---|
| Message-ID | <[email protected]> |
Hi all, Greg Valcourt a =E9crit : >=20 >=20 > Is there a solution to this problem? I've got the same problem with my = server. >=20 > Sever Specs: > Ubuntu Hardy > Linux 2.6.24-16-server #1 SMP Thu Apr 10 13:58:00 UTC 2008 i686 > Server version: Apache/2.2.8 (Ubuntu) > Server built: Nov 13 2009 21:59:05 > PHP 5.2.4 > PHPGroupware 0.9.16.015 >=20 > The database runs on a different server: > Ubuntu Hardy > Linux 2.6.24-16-server #1 SMP Thu Apr 10 13:58:00 UTC 2008 i686 > PostgreSQL 8.3 >=20 > I haven't been able to personally duplicate the issue. I got E-mails fr= om two users today, after upgrading from 0.9.16.12 last night. They say i= t happens when ignoring conflicts after changing the date of an existing = Calendar entry.Sent from the phpGroupWare forums @ http://forums.phpGroup= Ware.org Since we are preparing a release, I will try to reproduce this and fix it. But as skwashd mentionned, it seems to be hard to reproduce. Which locales are you using ? Do you have any phpgroupware specific configuration ? (ie using php4 session / db session, in cookie mode or get mode, etc ...). Regards, Caeies