First of all I want to say that I am currently working with repeating dates and it obvious that Karen has put alot of work into the various combinations and handling them with views. (Glad I didnt have to write that code!).

I was even able to generate a node with a Friday the 13th 10-year repeating date pattern that worked perfectly!

But here is my issue.

If I include a CCK date field in a node, then i am asked to choose between either a multiple date, or a repeating date.

As I just said, repeating dates work great. I seem to be able to generate almost any repeating date except perhaps the first blue moon after easter in each leap year. This satisfies my needs exactly for about half of the events I have to generate.

But I can't use repeating dates for the other half - because I have some nodes that recur at different times of the day, or have no discernible pattern.

So unfortunately, it seems I cant use repeating dates if I have to choose between the two, beause I have to support predictable as well as random patterns of potential dates.

But then it occurred to me:

What If I included 2 CCK date fields in each node (one repeat, one multiple), and carefully use the one which is best for my needs. If it repeats regularly, use the repeat date, if it doesnt, use the multiple date.

Well, this works great! - Now I can save just about any combination of repeats, plus any extra random dates and times I need into one node.

BUT NOW FOR THE TRICKY PART....

How can I get views to extract the dates from BOTH date fields of the nodes using a view?

I have no problem extracting either the repeating dates, or the multiple dates, but dont see how I can extract both sets of dates, sort the merged results into one list for processing or including into a calendar.

Maybe I'm asking for too much - but unless I can handle both multiple and repeating dates in one node, or find a way of adding odd dates to my repeating date pattern, I will probably have to abandon repeating dates and go only with multiples, then enter 365 dates per year/ per node for daily events. OMG

Has anyone else been able to resolve this?

(I have a few other date questions, but I'll save them for another time)

Thanks for any advice.

Comments

dpatte’s picture

dpatte commented
Title: Entering dates: multiple AND repeating then processing in ONE view. » Repeating dates: change EXCEPT to ADD/REMOVE
Category: support » feature

I have an idea:

If EXCEPT is changed to ADD/REMOVE then there may be a way to support my needs....

if ADD/REMOVE date/time is the same as a repeating date/time, the repeat is removed (as it does now)
BUT if a ADD/REMOVE date and time overlaps a repeating date/time, the new time replaces the repeat,
otherwise the new date/time is simply added to the list (the case I need most).

On top of that, if data entry allowed multiple add/removes for the field, then that field could handle both regular pattern and irregular pattern date needs.

Karen, I'll start digging in the code to see how much work this may be.

Exploratus’s picture

Exploratus commented

This would be wonderful...

dpatte’s picture

dpatte commented

Multiple EXCEPTS are of course allowed (though the interface doesnt seem to make it obvious - you have to save first), but if they where multiple ADD/REMOVES, that would be perfect.

On my side at Dance-Ottawa.com, I decided to go with repeating dates after all, it turns out that events with unpredictable patterns are far less than 50% of the time, more like 20% - so i accepted that. But I must say my users do find it somewhat confusing, especially when events end past midnight.

Exploratus’s picture

Exploratus commented

it would just be so much less annoying if one didnt have to get out and save every time. when you have 10 or 20 except dates, it makes it reaaaallllyyy annoying.

MBroberg’s picture

MBroberg commented

+1 for add/remove exception
Sometimes a repeat pattern just doesn't quite have the options I need, and adding a date by hand would be great. I don't want to create a new node because then they are not grouped together in views.

Exploratus’s picture

Exploratus commented

Yes, especially when I am trying to add something like a baseball season or something. The dates are so irregular and there are so many, that to do one season of baseball I would need to get in and out of the node probably 90 - 100 times to exclude all the dates. Can't we just have a add anotther item button or something so we can add multiple exceptions at once. This should be the way it works, having to get out and in is a workaround....

scottrouse’s picture

scottrouse commented

I second the comment in #6. Is there an easy way to get an "Add another Exception" button or something rather than having to re-save the node ever y time. If this is being discussed in another Issue, feel free to direct me there. This is the best I could find searching.

chaps2’s picture

chaps2 commented
Status: Active » Closed (duplicate)

For additional dates this a duplicate of #292522: Additive Exception to Repeating Date. A button to "add another exception" is another issue.