It would be really great if the date widget could be set up in such a way that the user (or whoever is actually inputting the nodes) could choose for each node whether to set up a repeating pattern, or to input individual multiple dates.
Right now, if it's set for a repeating pattern, someone inputting an event that happens on January 1, January 6, and January 7 needs to say the event is happening daily between those dates, then exclude January 2-5, which requires submitting the form for each exclusion.
Alternatively, if it's set to input multiple dates, someone who is inputting an event that happens every Saturday for 6 months needs to add 24 separate dates, something which also requires multiple submissions of the form.
For both of these cases, adding dates is a cumbersome, user-unfriendly process. Allowing the user to pick which date type is most appropriate for their particular event would greatly enhance the usability of the form.
Comments
Comment #1
karens commentedFirst of all, I am planning to add 'Additions' as well as 'Exclusions' so you can either add or exclude as many dates as you like. It is messy in the D5 version since you need to submit the form each time. In D6 we have a nice AHAH 'Add more' button to make it easy to add a list of dates without submitting each one.
If that's not sufficient and you want to incorporate both the multiple dates and repeating dates forms into a single form and let the user choose one, I agree this would be nice, but it would also be quite complicated to do and I'm not sure how to make it work. If someone wants to try to make a patch for this, I'd look at it, but it would take some serious javascript to make it user-friendly.
Feature requests go against the D6 version and then (maybe) get backported to D5. This is complicated enough that it would probably *not* get backported.
Comment #2
arlinsandbulte commentedDuplicate of #292522: Additive Exception to Repeating Date