-
Bug
-
Resolution: Fixed
-
Major
-
3.1
-
MOODLE_31_STABLE
-
MOODLE_32_STABLE
-
MDL-54751-master-v5 -
Difficult
-
-
5
-
3.2 Sprint 7
With the recycle bin enabled, deleting large, complex objects forces the user to wait until the backup process has completed before they can do anything else. When you delete small objects (e.g., labels, simple pages), the deletion occurs quickly. By "deletion," I mean this workflow:
1. Turn editing on
2. Delete item
3. Turn editing off
But when you delete a larger, complex object, step 3 above – turning editing off – can take a long time ( up to > 2 minutes), and there is no indication (other than what the browser provides) that something is happening. You basically have to wait for it to finish. Something that used to happen immediately – turning editing off after deleting something (regardless of its complexity) – can take minutes with the Recycle Bin enabled. An example of a "large, complex object" is a quiz with 95 questions and 155 student responses. Obviously, Moodle is working on backing up the quiz, and since it's rather complex (lots of responses), it takes time. The same thing happens on restore. Restoring this kind of quiz can take some time, but there isn't any kind of progress indicator to let the user know that something is happening and that it may take some time.
The concern here is that with the recycle bin enabled, a fundamental aspect of the Moodle experience has changed; i.e., deleting some objects no longer happens quickly if they are complex. How long it takes for Moodle to return control when turning editing back off after deleting an object depends on how large/complex that object is. And Moodle provides no progress indicator that something is happening.
We also saw this behavior when testing the recycle bin plugin our Moodle 2.7 site (we also saw session lock errors for large object deletions). We also see this issue on a test Moodle 3.1 server with the recycle bin enabled. While this quiz example may represent an outlier, users delete all sort of things... small and large objects.
- caused a regression
-
MDL-72780 (another) try..catch(Exception $e)
- Open
- has a non-specific relationship to
-
MDL-56847 Tags attached to activities are visible after activity is deleted
- Closed
-
MDL-80670 Improve the way gradebook handles activities which are pending deletion
- Open
-
MDL-55383 Recycle bin - introduction of a pre_scheduling hook to allow recycle bin to create entries before the async deletion task runs
- Closed
- has to be done before
-
MDL-55342 Recycle bin should use adhoc deletion process for mobile
- Closed
- is a regression caused by
-
MDL-48012 Integrate the 'local_recyclebin' plugin into core
- Closed
- Testing discovered
-
MDL-56796 Possible missing requires when running recycle bin cron.
- Closed
-
MDL-56870 Course modules can be viewed after adhoc deletion is scheduled
- Closed
-
MDL-56789 Recycle bin warns of pending grade items being deleted even if no grade items are being deleted.
- Closed
-
MDL-56793 Possible to lose deleted activities before they reach the recycle bin.
- Closed
-
MDL-56821 Settings page for grades of deleted activities show some options can be set.
- Closed
-
MDL-56819 Add loginas support to cron_setup_user
- Closed