In 6.x, there were prompts for "starting from"/"ending on" values on the Display Fields screen for repeating date fields.

In 7.x, I see only a "Show [ ] value(s)" prompt for repeating date fields, which starts with the earliest date. (Drupal 7.8 + latest -dev releases of Date/Calendar/CTools/Views.) Is there a way to display the next upcoming date for repeating dates in a node without resorting to views?

Comments

delapohl’s picture

Bump. To recap, looking for a way to display the next occurrence of a repeating date. This was possible in 6.x by specifying "now" as the starting from value on the Display Fields screen. I don't see this option in 7.x.

chalee’s picture

Any solution to this problem?

vuthappa’s picture

Any update on this guys? Thanks

bnicoll’s picture

Still desperate for a solution on this.

steven jones’s picture

Category: support » bug
Status: Active » Needs review
StatusFileSize
new1.16 KB

Actually all the code for this is there, but the admin UI for those two field are hidden on D7, not sure why this is, but here's a patch that un-hides them and makes the whole thing work as far as I can see.

arlinsandbulte’s picture

Status: Needs review » Fixed
steven jones’s picture

Thanks for committing this. Would it be possible next time to use the Adding a commit author guidelines so that I get credit as the author of the patch please?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

bnicoll’s picture

Just upgraded to latest version of the date module 7.x-2.3. Previously tried the patch - still not working for me.

Is there any other workarounds or planned implementation?

Thanks,
Ben.

burningdog’s picture

Component: Date Repeat API » Code
Status: Closed (fixed) » Needs review
StatusFileSize
new1.38 KB

This doesn't work for me either. To replicate:

  • Add a multiple value date field to a content type, and don't check the "Collect an end date" checkbox.
  • Add a node, and give the date field some values, e.g. 2013-01-02 - 12:02, 2013-01-15 - 15:30, 2013-04-11 - 12:30.
  • Create a view, add the date field to the view, and in the field settings set Multiple values to 5, starting from as 2013-01-05T00:00:00 and ending with as 2013-02-01T00:00:00 (why can't we use relative values for these?).
  • Preview the view. The result is that the output shows "Friday, January 11, 2013 - 15:30, Thursday, April 11, 2013 - 12:30" which is incorrect - it should be "Friday, January 11, 2013 - 15:30".

So it appears that the "starting from" setting works - date values which exist before this value are correctly excluded, but the "ending with" doesn't exclude values which end after the specific date.

The problem is the checks in date_prepare_entity(). They check if the "from" value is less than the value of the "starting from" textfield, and if the "to" date is greater than the value of the "ending with" textfield. What they neglect to check is if the "from" value is greater than the "ending with" date.

Patch attached.

mjk3r’s picture

Same problem here.

Using: repeating date (Date 7.x-2.6)

Node display date field settings:
- Display both Start and End dates
- Show 1 value(s) starting with earliest, ending with latest
- Hide repeat rule

1. It works correctly if displayed through Calendar View
2. It doesn't work at node display - once you click on event on specific date in Calendar
- it will always display date of the very first event in the series, no matter what date you were actually clicking on
- it should display however the date for event instance of the real date which was selected from calendar
- it doesn't matter if you collect an end date or not, it just doesn't affect that feature at all
- it doesn't matter if you Display both Start and End dates, or just the starting date, it just doesn't affect that feature at all (tested all combinations of collecting and displaying end dates)

Help would be very much appreciated
with all the best wishes

lias’s picture

Have the same issue with the Date Repeat module not displaying the current date on the full display of the node. It displays the original date which has passed. I understand there are modules that will create new nodes or clones of the repeating event but to me that seems like more content and management when it would seem to make sense to have the date repeat module display the current repeat date.

podarok’s picture

Status: Needs review » Needs work

The last submitted patch, 10: date-range_fix-1285260-10.patch, failed testing.