Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hello,
First of all, many thanks for this wonderful module.
when I set "How to render a split day" to "none" in the configuration and set the "Show split day states" to "unchecked" in the availability calendar field with widget:Shows the calendar as a number of months .. and I try to book in the calendar say from 05-02-2012 to 10-02-2012 .. I find down in the "clear selected dates" button area that the departure date is incremented by 1, stating that departure date is 11-02-2012 instead of 10 .. Is there anyway to adjust this??
Comments
Comment #1
fietserwinThe problem is when not using split day, what day do you want users to click: their last full day of their stay, or the date they depart? Currently the former is implemented, though the text is not accurate in this situation. I recently noticed this and added a todo remark about it to the module, but more at the level of changing the text than considering this an error, let alone a critical one.
[You may notice that there's an underlying assumption being that when showing full day bookings, a booking is shown from (and including) the day of arrival up to (and including) the last full day of the booking (but not the departure day. Personally, I've never seen otherwise.]
If I would implement the latter option, users would click on a day that, subsequently, does not get colored. I found that a bit counter intuitive, so I opted for the first option. Note: that's why I always use split day, IMO it is clearer for the visitor (except for the misleading text...). But thinking again about it, I now start to doubt it.
What is your opinion in this? How should A.C. react in the different settings? Is clicking on the departure date more logical for users, even if that day would not get colored?
Comment #2
fietserwinCreated a task with an even wider scope: #1661454: Better distinction between whole day and overnight rental. This issue will be handled by that task, so closing this one as a duplicate.