No matter what end/to-time i put in at node/add/merci-reservation when i go to /reservation/week the booked timeperiod (all on 1 day within the open hours) starts at the right starttime but does not end at the to/end-time. i know there was https://drupal.org/project/calendar_span which seems to do this for drupal6 but how can i manage that in D7?

CommentFileSizeAuthor
merci.png15.17 KBpimok3000
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

darrick’s picture

Category: bug » support

Check to make sure you have the date to display both start and end times in your view.

tangz22’s picture

Issue summary: View changes

display both start and end times selected and pb appears...
any issue on that?
Tx

shasha_s’s picture

Drupal 7.34
merci-7.x-2.0 and
merci-7.x-2.x-dev

Hello!
Thanks for the very nice module.

I have the same problem with the correct start but wrong end time.
In the Reservation View, display is set correct to -->both start and end times.

but the end time does not appear. It also shows wrong when the availability calender shows up.

I get also this message on the page
Notice: Undefined index: groupby_times in template_preprocess_calendar_week() (line 485 of /.../sites/all/modules/calendar/theme/theme.inc).

How can I please solve it.

thanks
S.

metakel’s picture

The latest version 7.x-2.1, in the view editing page, even I have set the field "Content: Reservation" > Display to "Both Start and End dates".

However, still only the start date (time) is shown. Even if I set the "Display" to "End date only", the calendar still only show the start date (time).

darrick’s picture

Version: 7.x-2.0 » 7.x-2.1
Category: Support request » Bug report
Status: Active » Needs review

Via: https://www.drupal.org/node/2014609#comment-7624883

Click on Aggregation Settings for the Content:reservation field. Under Group columns (additional) check the box next to "value2." I just tested and it worked on my end. If you can confirm the fix I'll update the code.

Thanks

metakel’s picture

Darrick, your "value2" method works, thank you! Please consider to include this into the documentation.