Restrict the Number of Repeats

Moving this to the Alpha track. These features are even more imperative with the repeat process being made part of the initial event creation process. There may be additional settings needed like: Publish first event but leave repeats unpublished. I believe a large number, if not a majority, of people who will utilize this module in a similar manner that I described above.

Ideally, this mod would be integrated with or made to work well with Scheduler and some additional code. For example, when creating the repetitions, a user might be able to enter a value in a field, Number of Days before Event that Node should be published. A quick calculation and a "To Be Published" date field could be populated for Scheduler to rely on. This should stick for each repeated node that is created.

Actually, in most cases I can think of, the desired result would be that notifications are sent in proximity to each individual event. This is how Meetup.com handles repeating events for example. As does Google Calendar for that matter.

If you are hosting a weekly event, you don't want one notification to be sent when you first create the event and then no further notifications after that. You likely want a notification sent each week, after the previous event, but before the next one.

I agree that this would ideally be handled at the notification level, but don't forsee that being possible without some extensive PHP/Rules coding. FWIW, our current work around for this (which actually utilizes a combination of Node Clone and Scheduler because Node Repeat continues to have problems) is to have users choose the publish date of each event instance. Then, with the use of the View Unpublished module, we make it such that everyone can see all the future events regardless of their published status. A similar setup could be accomplished very simply if Node Repeat offered a hook to Scheduler and/or some way for the node creator to specify a time frame in which nodes are published.

Again, something that could be accomplished with extensive PHP coding outside of the module, but seems like it would be much more simply accomplished within.

The signup module doesn't even come close to accomplishing the use case I've laid out, however (which is to notify everyone in a particular group of a new event that has been posted; not just those who have already signed up for it). There's some promise in the Signup CCK module, but I don't think it's matured yet.

And again, in most social networking group settings, the notifications will need to be sent out for each occurrence of the event since a) membership fluctuates and b) people count on the reminders.