We are working on a development server adding in extra functionality for a client (the site itself was originally made by a separate developer). We have it set up now so that users can anonymously create an event on the front end of the site using the Community Events plugin. These events are set to be “Pending”, so the administrator can go in and publish them after checking them. Unfortunately, it seems that any events set to be recurring are duplicated whenever the status is changed. So if they publish the event, there are two sets of recurring events, both set to published oddly enough.<\/p>\n
This works even if you create the event in the back end of the site by creating it set as Pending, and clicking “Save as Pending”, then once the page loads clicking “Publish”. With this issue, we can’t hand off the calendar functionality to the client as it doesn’t work if the user creates a recurring event. It seems like it’s re-creating the recurrence chain even if you save the original event item itself.<\/p>\n","protected":false},"template":"","class_list":["post-74064","topic","type-topic","status-closed","hentry"],"yoast_head":"\n