Mar 17
5 / 6
Apr 3
2d ago
RalfBeckerEGroupware GmbH
18d

There is no month 0, it has to start with 1 (=January).

If you want to see where this error is comming from, you can enable a trace: Admin > App configuration > Security: at the very end you’ll find: Should exceptions contain a trace, including function arguments

Ralf

RalfBeckerEGroupware GmbH
17d

Try the following SQL queries:

SELECT * FROM egw_cal_dates WHERE cal_start=20642400 OR cal_end=20642400;
SELECT * FROM egw_cal_user WHERE cal_recur_date=20642400;
SELECT * FROM egw_cal WHERE cal_created=20642400 OR cal_modified=20642400 OR cal_deleted=20642400 OR  cal_range_start=20642400 OR cal_range_end=20642400;
14 days later
RalfBeckerEGroupware GmbH
2d

Sorry, typo:

SELECT * FROM egw_cal WHERE cal_created=20642400 OR cal_modified=20642400 OR cal_deleted=20642400 OR  range_start=20642400 OR range_end=20642400;

Ok, the problem is the timestamp 20642400, from which EGroupware thinks it’s a date, newer PHP throws an error instead of an exception …

It’s fixed now:

You can apply the fix to your instance (see the howto in our help-section), wait for the next maintenance release, or delete the three events.

Ralf