Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[stable11] Add DAV repair step to fix calendar data #2807
Dec 22, 2016
referenced this pull request
Feb 1, 2017
I switched from OC 9.1.3 to NC 10.0.x, no problem
I've done again the upgrade (restored to oc 9 and so on) several times, to be sure (I wasn't sure if I had to have the calendar plugin reactivated while in transition NC 10, before upgrading to 11.0.1). Same problem, every time.
I mass-edited some cal entries with this bad DTEND property. Now the logs (logging menu in NC adminitration) don't show any error (all debug levels enabled) but I have even more calendars loading endlessly. I don't think I have bad entries because of the mass-editing. But in any case, the upgrade from 10 to 11 doesn't correct the entries that make NC 11 load endlessly.
Can't move to NC with this bug. I switched back to OC 9.1.3
I've exported the calendar entries from the DB and checked the format. All entries seem to have a consistent DTEND format.
To me it looks like the readProperty method has an issue parsing the line.
Second try upgrading today. It's working now after manually repairing the calendar entries.
Just wonder why the repair job of NC didn't do that automatically.
Thanks to @jokakilla , I managed to upgrade to nextcloud 10 then 11. But some problems should still be considered by the team, I suppose:
You can correct your faulty calendar entries with something like :
But, new problem, as I couldn't migrate from OC to NC, some days ago, I upgraded my OC 9.1.3 to 9.1.4.
Then I could migrate to NC10 and 11 right after, disabled maintenance mode and my calendars aren't loading forever anymore. whoaaaa.
I hope all this will help.
DO A CODE AND DB BACKUP BEFORE PLAYING WITH IT ALL.
@jokakilla @michauk sorry for the late reply (but I'm glad you figured it out). Since we wanted to be a bit smarted when migrating and making upgrade faster the fix is not run on upgrade. Since if you have a large large enough instance that would make it all painfully slow.
So if cron would have been triggered a few times it should have launched the repair job.
Anyway hope all is fixed already!