Calendar View - A database error was encountered

Hi Rob!

Hope you're doing fine!

All of a sudden, my customer can't access the calendar view and is getting an error (or, as you always like to point out a warning, not an error) message:

ABPro WARNING! A database error was encountered, see error log for details.

After checking the error log, it turns out to it wasn't out of the blue but happened a couple of times from august already. The error is:

functions2 Incorrect DATE value: '16-11-2020'

I'm on Joomla 3.9.18 with ABPro 4.0.3 RC13

It's probably a stupid little thing that I'm just not able to see...

Thanks in advance and kind greetings from Finland.

Olivier

Thanks for your reply.

No, it's not specific to one date. It throws the error whenever I try to access the calendar view. So the answer to your other question (reproduce it myself) would be yes.

Now that I think of it, I changed hosting company around that date in August... could it have something to do with server configuration changes? It was a cPanel to cPanel migration and all things seemed to be working right away...

I tried to access the calendar through the link index.php?option=com_rsappt_pro3&view=calendar_view instead as with the menu alias and it throws another error:
Error on server call to get buildCalendarDeskView : 500-

The error log keeps saying: functions2 Incorrect DATE value: '17-11-2020'

Just to let you know I opened a ticket with my hosting company. Was looking for my DB in phpMyAdmin and it wasnt't there...

After regaining access to my database via phpMyAdmin I tried the following:

- used ABPro's backup function to backup everything
- uninstalled ABPro
- reinstalled ABPro
- checked on the site if the calendar is working: SUCCESS
- restored backup
- checked calendar: FAIL

Hi Rob,
Thanks for your reply.

No, unfortunately it didn't do the trick.

- Unpublished all resources.
- Checked the empty Calendar View opens ok.
- Created a new resource called "test", left all other resource settings default.
- Checked Calendar View. It doesn't work.

I attach a CSV export (altering some sensible elements), and it seems clear that the first resource in the list isn't formatted properly. However, only disabling it didn't solve the issue.

Olivier Fontana wrote: and it seems clear that the first resource in the list isn't formatted properly.

Or it's simply a CSV export bug. From phpMyAdmin it looks fine...