Setting the repeat end date to a date less than what it was created with does not correctly adjust the nodes. It should remove the extra nodes after the end date, effectively shortening the repeat range. As it stands, the end date is updated and set correctly, but no nodes are removed.

Comments

seanbfuller’s picture

seanbfuller commented
Status: Active » Closed (fixed)

After updating event and core code to latest 4.7 I was unable to reproduce this issue. There is also the possibility that I had gotten confused on the mapping of events while testing. Given the complexity of moving massive groups of events around while testing any repeating events, I've found this to be a common occurrence.

I'm closing this issue for now, but if anyone finds this issue and has similar results, try updating to the latest code. If it persists, please reopen this issue with a detailed bug report on how to reproduce the problem.