Server Timezone Settings: America/Regina (CST)
PHP Timezone Settings: America/Regina (CST)
Joomla Timezone: Regina

Issue:

Clicking on a date in the monthly calendar sets the check in time to the next day ie. I click on Oct 9, 2012 in the calendar, and the Check In input (html id: iFrom) is set to 2012-10-10.

Inspecting the span, the fromDate, fromDisplay, toDisplay and toDate are all off by one day.

I see many script declarations in /administrator/components/com_booking/helpers/document.php which are setting the properties on each span element, but this seems to be an issue somewhere in the date calculation.

We originally had the timezone in Joomla set to UTC, but the month view calendar was off by a day. ie. Sat, Oct 13th was actually showing as the 14th of Oct. (Interestingly, with the timezone set to UTC, clicking on a subject in the calendar would set the proper checkIn/checkOut date).

We are using the latest version of the component, the issues can be seen at rcmpheritagecentre.com/index.php?option=...ery-hall&lang=en

Appreciate any insight!

Hello,

I tested it on localhost and I have same problem with timezone settings you post us. We will look on this problem as soon as possible and write you about solution.

Awesome, thank you!

Hello,

see attachement. It is patch for the actual version of booking. It should repair your problem. Please, let us know if everything is fine with this patch.

How to install patch to your Joomla installation?
Just unpack it to root of your website. It will modify files of folders administrator and components

Thanks for the patch, that fixed the calendar issues.

However, now when following the booking procedure through, the ItemId is lost somewhere - you'll see what I mean if you try it here: rcmp.lookmatters.net/object/1-gallery-hall

I've removed all of our template overrides to be sure that it's not an error on our end.

This was working before the patch, I didn't diff the BookingHelper class against the old to see what changed there that might affect it...

Thanks!

I'm wondering if the patch was against the version we have, I now see that you're at 1.4.5, our installed version is 1.4.4...

We had this issue before, and it was resolved when we updated to 1.4.4.