On Friday, we added a repeating event, an exhibit that occurs daily (Tuesday - Saturday) from April 16 to September 19.
At first, only the first few instances showed on the calendar. After a while (maybe an hour?) the next week or so worth of instances showed up. By the end of the day, that was all that was showing.
This morning, after refreshing the calendar, the rest of the instances are now showing.
All instances of the event were listed in the backend events manager. And the ical feed we use in our portal was correct, so all instances showed there.
What would cause our calendar to take so long to display all of the events?
I have a similar instance. With our Faculty/Staff profile merge, I’ve been working with the old profiles: setting all to Hidden, removing balloons and stars, moving all the original profiles to an archiving group, removing all linked copies, making the two types non-global.
For many of these steps– move 200 profiles, delete 400 profiles, etc.– I set the task going, and the page stalls for a minute or two before refreshing: “Page not found”. However, if I return to the page, I can see some of the work is done. Refreshing, I can see the server working on it steadily in the background.
Perhaps something similar is happening here? You’ve set in motion a process to make ~150 events: perhaps it just needs time to work through it.
That said, it does feel a bit slow. My one step to set things to “Hidden” seems like it should be pretty quick, even at 200-300 items, but it took maybe 3-5 minutes. I’d assume event making would take some time, but not a good part of a day.
Hey guys, I’ll let us get more info from the team to speak further to this, but just as a bit of context – bulk actions (even just setting things to Hidden) does more than just change the status flag behind the scenes, it also has to clear or update a lot of cache entries, since the LW cache can serve up pages (and 404s) even if the db were to falter. So things that were live and become hidden, LW has to replace those cache entries on both nodes so it doesn’t erroneously show up as Live in cached results when you want it hidden. I’ll leave this for Rachael and the team to speak to further, just wanted to pop by with that additional context!
Ah, that makes sense. With that context, I guess one potential improvement to consider would be to have some kind of UI that explains what is going on when a large enough bulk action is started.
When I did my first set of bulk actions, the page hanged for a minute or two, refreshed back to the profiles_list page, but with a message “Page not found”.
I first thought that the process had failed, attempting too much in a maximum time limit.
Seeing some tasks did complete, I thought that it was only able to work up to a point before hitting a maximum time limit.
Its only after being distracted and coming back after a few minutes to see more was being done did I realize it was still working in the background.
For a rough idea of something better: if a bulk action takes more than 30 seconds, refresh the page and show a message like, “Your bulk action is being processed by the server and may take some time. If additional edits require that action to finish, please wait for it to complete before continuing.”
There’s more potential there, perhaps, like a task queue system that can report to the editor the tasks progress and notify when complete. While more transparent, its use case is likely too rare (e.g. my series of bulk actions) to merit it.