Artefact path is not being calculated correctly on file rename
Bug #1359531 reported by
Yuliya Bozhko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Yuliya Bozhko |
Bug Description
Discovered while doing some testing in files and folders
To reproduce:
1. Get fresh install.
2. Login as admin
3. Click content > files
4. Add a folder "f1"
5. Enter folder
6. Add a subfolder "f2"
7. Edit "f2", rename to "folder2"
8. In SQL client run: "SELECT id,path from artefact;"
The subfolder's path should be something like '/5/7' but instead it's '/5/5/7'.
It is quite important to fix as permissions to view artefact ancestors are calculated from the path. I checked and this happens only when files/folders are renamed as constructor is missing $oldparent property which is no supplied from the DB.
description: | updated |
Changed in mahara: | |
milestone: | none → 1.10.0 |
status: | In Progress → Fix Committed |
tags: | added: regression |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Patch for "master" branch: https:/ /reviews. mahara. org/3653