|
Mark Williamson
|
December 20, 2013 at 4:21 am
A question about recurring events. You create an event with X number of future events. This all works well. However, we have recurring events that happen in different locations. Event X (instance 1) will be run in Location 1 but Event X (instance 2) will be in Location two with possible different capacities.
We can obviously go in to each event separately and change details but if we want to make a change across all instances (such as a pricing change), every field for the event is replicated across all events thus losing any single event customisation.
Are we understanding this correctly and is it possible to make a change across all instances of a recurring event but only for the field that has been changed and all other information left untouched?
|
|
Tony
|
December 20, 2013 at 7:56 am
Hi Mark,
Are we understanding this correctly and is it possible to make a change across all instances of a recurring event but only for the field that has been changed and all other information left untouched?
When making changes within an event and then selecting ‘All events in the series’ it will overwrite all events with the current events settings.
There currently isn’t a way to prevent this without modifying the code.
I will add this as a feature request but can not comment on if/when it will be included currently.
|
|
Mark Williamson
|
December 20, 2013 at 8:00 am
Hi Tony
Thanks for the quick reply and clarification, we will have to look for a workaround.
Mark
|
|
Sidney Harrell
|
December 20, 2013 at 12:57 pm
Right now your best workaround would be to have some sql queries stored in a text file that you could copy and paste into phpMyAdmin. For example, to update the price:
UPDATE wp_events_prices ep SET ep.event_cost = 5.00 INNER JOIN wp_events_detail ed ON ed.id=ep.event_id WHERE ed.recurrence_id = 2
when you paste it into phpMyAdmin, you would change the recurrence_id and the event_cost. If you had multiple prices on your events, then you would need to add another clause to the WHERE to narrow down which rows you affect.
|
|
Mark Williamson
|
December 24, 2013 at 2:26 am
Thanks both, very helpful.
|
|
Josh
|
December 24, 2013 at 10:04 am
It may also help to use the event import tool import these events since the REM was designed to be more of a cookie cutter approach where all the events in a series are essentially the same except for the dates.
|
