First off: When holding CTRL and drag for creating recurring events it shows a dialog that i'm changing a repeating event. On creation this should not be the case
Also the new dialog where you can confirm that will not trigger an event beforeeventsave or beforeeventadd.
I opened up my network that in the examples so you can see the API calls are or are not triggered
- 5EPNweHHwm.gif (679.08 KiB) Viewed 1377 times
For the change of an recurring event:
You will see there is a listener configured for the 'SAVE' button event: @beforeeventsave="onBeforeEventUpdate"
This will trigger a API call to our backend.
But when it is a recurring event the 'SAVE' button does not trigger te beforeeventsave event.
Instead it shows a new modal where you can either choose 'YES', 'ALL FUTURE EVENTS' or 'ONLY THIS EVENT'
Based on selecting the first event in the recurring or one of the following.
You will see that when we click these buttons i have no eventListeners for this action and so our backend data will never be updated.
Here you see a API call get triggered on creating a new event
- Uv32ePf8Im.gif (940.37 KiB) Viewed 1377 times
Here you can see that no events are triggered when pressing the buttons in the modals because the save does not trigger an action anymore but it's triggering the modals:
In one of the examples you will see that even i choose 'ALL FUTURE EVENTS' not all the events are updated correctly.
- fkn3CCFgHB.gif (3.45 MiB) Viewed 1377 times
Also when a recurring event takes place i saw that it is stored in a object variable recurrenceRule. But if you only change the middle one of the 3 events how should this be stored and keer the recurrenceRule data?