-
Bug
-
Resolution: Fixed
-
Major
-
4.0
-
MOODLE_400_STABLE
-
MOODLE_400_STABLE
-
MDL-74506-master -
To reproduce:
- Check out a patch before
MDL-72092has landed:git checkout 47e880e347ccb2c216d72f803ff6154820695bf0
- Open the block_instances table.
- Log in as an admin and go to the Dashboard and then check the block_instances table. You'll see block instances for that admin's user context ID.
- Log in as another user and go to the Dashboard. Checking on the block_instances, you'll see the records for the user's context ID.
- Check out the recent version where
MDL-74271has been included. - Run the upgrade
- You'll see three "recentlyaccesseditems" records but their parentcontextid is set to 1 (system). Two of these (the one for the admin and the user) should have the parentcontextid set to the admin's and user's user context ID, respectively.
- Go to Site administration / Apperance / Default dashboard page.
- Reset the Dashboard for all users.
- You'll see the three "recentlyaccesseditems" records on the block_instances. The admin's and the user's block instance records are deleted.
- As admin, view the Dashboard again and check the block_instances table.
- You'll see that the new block instance records for the admin's context ID are created. Same will happen for the user. The extra recentlyaccesseditems block instance records are now orphaned.
- Discovered while testing
-
MDLSITE-6601 Upgrade moodle.org to 4.0
-
- Resolved
-
- has a non-specific relationship to
-
MDL-74271 Block upgrade steps are unnecessarily slow
-
- Closed
-