Author Topic: Recurring event - 4.6.beta1 - not initially treated as recurring [FIXED] (Read 495 times)

ken · February 28, 2015, 03:50:06 am

In 4.6.beta1, edits to an event after making it 'recurring' only update the original event. It's not until one presses 'Save and Done' that the event configuration can be edited and the 'which events should be updated' dialog appears.

Create a new event
Make it recurring using 'Save' (not 'Save and Done')
Visit another tab and edit the event
The 'which event instances to update' dialog doesn't appear, and only this instance is updated

Deepak Srivastava · March 04, 2015, 06:29:49 am

"Save and Done" is reloading the page, and therefore also loads the JS required for dailog to appear. Whereas the save uses an ajax call to just save the values (without reloading the page).

In anycase this sounds like a bug.

Correct behavior i think would be:
Save (repeat tab) -> saves & reloads the page, so JS gets loaded.
Save and Done (any tab) -> behavior should be like normal events - saves and redirects to a event-manage screen (whatever is available from user context)

ken · March 28, 2015, 03:52:45 am

Fixed in 4.6.beta4

CiviCRM Community Forums (archive)

News:

Author Topic: Recurring event - 4.6.beta1 - not initially treated as recurring [FIXED] (Read 495 times)

ken

Recurring event - 4.6.beta1 - not initially treated as recurring [FIXED]

Deepak Srivastava

Re: Recurring event - 4.6.beta1 - recurring event not initially treated as recurring

ken

Re: Recurring event - 4.6.beta1 - recurring event not initially treated as recurring