Yes, it's true it could look like a big bug, but as i know where the function is returning an error, it's not a major one

So, i have checkec that 4 of your events have no valid date (you can see this in the list admin, where a "no valid date" in red is displayed in place of the published icon.)

But this should not be the reason of the notice error.
So, is it possible to have super user access, to be able to turn error reporting just a few minutes while i'm checking the frontend, this way i will be able to see which event is giving this error, why and how to fix it asap

Thank you for your help!
Regards,
Cyril

Hello,

It's okay now, but it is really a weird issue...

The problem is that on your server, the php function dateInterval doesn't exist, but should as you are on php 5.3.28 (php.net/manual/class.dateinterval.php)

For this reason, the script using the array of dates for a period was using the old function for old version of php (before 5.3). And that where the issue was.

What is really strange is that the function for version of php before 5.3 was working fine to return the dates, but was returning error if no dates between start and end date...
This is fixed, but this function is used since 2 years!
The only difference is now, on frontend, i'm using directly this function which has been migrated to the library, and not to use the data (this is a first step for the future database migration of dates).

So, the issue you had was a very rare possible issue.

In all cases, when testing your website by activating the development error reporting, i've seen many errors with your site template (maybe check for an update, seems old code for 1.6) and the google analytics plugin yu are using.

As a sum up, your issue is fixed with iCagenda! (no error in your events, it was just the "buggy" php you have on your server...)

Maybe ask your hoster why the class dateInterval doesn't exist on your server, as you could maybe one day have the same issue with another extension using dateInterval php class. (as Joomla3 as a minimum requirement of php 5.3.10, it could happen with a joomla 3 extension)

Best Regards,
ANd thank you for access, which has permitted me to fix a weird issue...

Regards,
Cyril

NOTE: attached the fix for buggy php 5.3 version