mahara-contributors team mailing list archive

[Aaron Wells <1359531@xxxxxxxxxxxxxxxxxx>]

** Changed in: mahara
    Milestone: None => 1.10.0

** Changed in: mahara
       Status: In Progress => Fix Committed

** Tags added: regression

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1359531

Title:
  Artefact path is not being calculated correctly on file rename

Status in Mahara ePortfolio:
  Fix Committed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1359531/+subscriptions