This is the issue I was thinking we may need to purchase a support ticket to resolve.
The problem could be in the our custom server-side code or something elsewhere. Please keep in mind that I am using Oracle PLSQL for the data processor and it also creates the json data load.
This is hard to explain…it is repeatable…the results are unexplainable (to me).
User 1: use chrome
Step 1: Create an event which repeats every day -- forever
Step 2: Edit the occurrence of the 1st day -- change the status
Step 3: View the results -- all looks well
Step 4: Press reload a few times --- all continues to look fine
User 2: use chrome or any other–FF/IE/Safai
Step 1: <b>Go to a different computer</b> this is important--not a different browser -- different computer.
Step 2: View the 1st day (which has the edited occurrence)
User 2 sees 2 events (which is different than user 1). Event 1 is series, Event 2 is the edited occurrence for that day.
User 3: use chrome or any other–FF/IE/Safari
Step 1: Go to the same computer as User 1, use a completely different browser
Step 2: View the same day as User 1 and User 2
This user see exactly what user 1 sees, a single event.
So the computer which created and edited the event see something completely different than all of the other users. You can open/close/refresh any browser, as long as it is on User 1’s computer and the day is shown as a single event.
All other computes see the double event. It does not matter which user or browser is viewing the day, it’s shown as 2 events.
Modified occurrence is binded to the recurring series via values of event_length and event_pid properties.
event_pid goes for a Parent series Id.
event_length - is a timestamp of the original occurrence. Meaning that if recurring events starts at 10AM and you move a single event that happens 10th April 10:00am to 12pm, event length will point to 10th April 10:00am.
It is needed for calendar to detect, which events of the series have been modified and shouldn’t be generated from the general recurring rule.
So calendar won’t display the original occurrence when it finds modified one.
In your case event_lenght timestamp seems to have correct value only for the system it is created in, and both events are displayed (modified and the original one)
This might be caused by timezone offset applied on server or on the client. Try enabling following config.