← Back to team overview

mahara-contributors team mailing list archive

[Bug 548327] Re: Users should have one directory that can't be removed

 

** Tags added: review

-- 
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/548327

Title:
  Users should have one directory that can't be removed

Status in Mahara:
  Confirmed

Bug description:
  The 'viewfiles' copying debacle and related discussion suggests we
  should have a directory for all users what can't be deleted, whose ID
  is known to the view copying/blog file uploading code.

  This is a directory that can be renamed, and even moved around in a
  user's file structure. And it can have files/folders inside it, which
  can be moved in and out. But the directory cannot be removed.

  That directory ID is known by the code. When views are copied, the
  folder which contains files copied from that View is put in this
  nondeletable folder.

  This stops the problem of copying a folder named 'viewfiles' causing
  an infinite loop.

  The blogfiles folder can be replaced with using this folder too.

  This means we can remove some code from public static function
  change_language in lib/user.php.

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