I am not sure if the following problem is a Calendar or a Date issue. If I have posted in the wrong place, please let me know. I recently upgraded to the latest calendar (6.2.4) and date (6.2.7) modules, and was pleased to see the ability to add additional dates to repeating dates. Upon using, however, I find that the time is not captured properly. The additional date appears, but the time is listed at 12 AM, the default for no time. It does not matter which View I use, all have the lack of a time for the added date. I upgraded both calendar and date modules to latest dev version and went through the debugging steps with no success. The date field for the node type is configured as datetime, and I use "text field with date popups and repeat options" as the entry method. Granularity is to the minute. So when I create this node type I have a date popup and a separate box to enter the time. But when I choose the option to add additional dates, I only have the date popup, which didn't surprise me, given that the time should be the same. Core version is 6.19. I thank you in advance for any assistance.

Comments

styledata@yahoo.com’s picture

Could someone tell me if this is a DATE issue or a CALENDAR issue? I know others are having trouble with this.
Thank you

HAg’s picture

Version: 6.x-2.x-dev » 6.x-2.4

I have seen the same issue posted as a Calendar issue.
Same issue here. Both the time and the date span is not captured properly. The time setting ad the to date is ignored.

j_byrd’s picture

When I add a date configured with with no ending time, the new date is listed as "all day", but if there is an ending time, the start time becomes 12:00am regardless of the time set in the from and to date section.

honeycomb’s picture

Related issue posted here: http://drupal.org/node/1053158#comment-4162416 Sorry no resolution yet.

Renee S’s picture

I am seeing this same bevahiour. Additional Dates aren't picking up the time, and schedule themselves for the same time PERIOD (weirdly) but starting at 12:00am - so a booking from 3-4:30 repeated will show up fine, additional dates will show up on the correct date with a 12:00am - 1:30am timeslot.

Renee S’s picture

(Also, I don't know that the time should necessarily be the same anyway - it would be great if users could add, say, an extra booking at a different time and have it show up as the same event, if one instance got cancelled or moved. So maybe the answer is to HAVE a time field for additional dates.)

Renee S’s picture

dp

fchandler’s picture

I am having the same issue with Additional dates. Same set up as styledata except core 6.20.

Setting the end date to include all dates and adding Exceptions does not appear to have the problem - the time of the initial date's times repeat correctly.

subscribing

quinns’s picture

I'm also experiencing this issue on a client's site. Using D6.20, Calendar 6.x-2.4, Date 6.x-2.7.

quinns’s picture

Priority: Normal » Critical
StatusFileSize
new73.68 KB

I've confirmed that this is happening on multiple sites that we maintain. This is a real show-stopper for some of our customers, so I'm elevating the priority of this bug.

This incorrect data gets inserted if an event node is edited or a new node is created, causing our customers to be unable to update their calendar events.

I've attached a screenshot showing a sample repeating date displaying a few elements... element 0 is the original (primary) date and elements 1, 2, 3 are repeats.

You can see that element 0 has the times set correctly (02:00:00 - 03:00:00 GMT) but the repeat times are wrong (08:00:00 - 09:00:00 GMT). (We are on Pacific Standard Time so the when the time zone difference is calculated, these repeat dates are shown as starting at midnight.)

I've marked the correct time in green and the incorrect times in red in my screenshot here.

quinns’s picture

Component: Miscellaneous » Date Repeat API

Edited to clarify this is an issue with the Date Repeat API component of the module.

quinns’s picture

Version: 6.x-2.4 » 6.x-2.7
StatusFileSize
new60.26 KB
new53.39 KB

Upon further investigation it appears that there is a UI widget missing on the latest version of this module.

On the previous version of the module (6.x-2.6), there is an "end repeat time" form element, the ID is:

edit-field-event-date-rrule-UNTIL-datetime-timeEntry-popup-1

This element is apparently missing on 6.x-2.7. Thus, when a repeating event is input, no "end time" value is passed.

I'm attaching two screenshots here: One showing 6.x-2.6 and one showing 6.x-2.7, each highlighted in the appropriate area.

quinns’s picture

So this issue keeps getting more complicated and strange. I've been running a lot of tests and it seems the problem might be with the "REPEAT EVERY WEEK" option ... if I set the the repeat to "REPEAT EVERY 7 DAYS" it does store and display the repeat dates correctly. I've just updated back to the latest release (the one without the end-repeat-time form UI element) and am now using "REPEAT EVERY 7 DAYS" instead of "EVERY WEEK". I'll continue to post anything else I discover here.

sketchysteven’s picture

subscribe

maio1980’s picture

I have a date field with repeat option, no end date. (7.x-2.x-dev date module)
Assuming that I want same time of start date, I resolve changing this code

  // add additional dates
  foreach($additions as $addition) {
    $days[] = date_format($addition, DATE_FORMAT_DATETIME);
  }

to this

  // add additional dates
  foreach($additions as $addition) {	
    $current_day = clone($start_date);
    date_modify($addition, '+' . date_format($current_day, 'G') . ' hour +' . date_format($current_day, 'i') . ' minute');
    $days[] = date_format($addition, DATE_FORMAT_DATETIME);
  }
  }

in date_repeat_calc.inc

Seems to be working, but this is very bad approach.
I think that the best approach is changing the input form to include hours and minutes.

Renee S’s picture

Try this: #1053158: Add time field to "Additional" repeat dates - I created a patch with a start-time for the event (defaults to the same duration as the original), comment #8.

Renee S’s picture

Status: Active » Closed (duplicate)