Recurring Events as Options: A Single Post Type Solution

[joshuadavidnelson]

A little follow up to #10, I've got a branch that seems to be working so far. I'm going to circle back to this in a few weeks to test further and refine a few things, but I think this first go at it solves some of the issues with a single post type.

Next up is some conditional recurring options: I think all "children" events in a series should provide the following options. If one of the "update" options is selected, the event details become editable again in the correct context.

• Keep event details as-is (default)
• Update event details and remove from series (similar to this, creates a stand-alone event)
• Update event details for all future events (create a new series with the current post as the series master, optionally deleting all the original series future events or creating a spin-off series and leaving the original series alone)
• Delete all future events in this series. (when trashing or updating the current post, all future events are deleted)

On a previous project I added an option to delete all related recurring events when series master is delete (what happens when a series master is deleted, do we remove the series information from the child events or delete them as well?). Perhaps this is an argument for using a unique id for tracking a series instead of a master post? Or, by default we remove the parent id from all the children, making them stand-alone events?

[joshuadavidnelson]

@billerickson I see you closing issues, and then I'm reminded of the work I have left to do on this! 😀 I don't think it's much, but I've refined the process a bit on a couple projects this then (each too customized to be used for the plugin directly). Apologies on the incredibly long delay...

I'm actually hoping to have a little time later this summer to work on a few open source items and plugins, like getting a PR ready for this, if that's still of interest.

[billerickson]

I apologize for not hopping on and helping you back in August when you first created this branch. I'm definitely interested in a PR for this.

I have a project starting this week involving a calendar, which is why I finished the simpler outstanding issues. I don't think we'll have recurring events on this specific project, and was waiting until I had a client with that requirement to dig into your set of changes.

No rush on the PR, but when you do put one together I'll review and test in a timely manner.

[joshuadavidnelson]

Awesome, sounds good - and no worries! There's plenty of paying work that gets in the way.

I've cleared up my mid/late summer a bit to enjoy the sun with my family and do some plugin/open-source work, so hopefully it will be less than a year from opening the issue to opening a PR. 😜