mahara-contributors team mailing list archive

[Mahara Bot <1475104@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/4973
Committed: https://git.nzoss.org.nz/mahara/mahara/commit/c1393bf907312b1030fa0961d9eb4241b2729cef
Submitter: Son Nguyen (son.nguyen@xxxxxxxxxxxxxxx)
Branch:    master

commit c1393bf907312b1030fa0961d9eb4241b2729cef
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date:   Thu Jul 16 17:19:39 2015 +1200

Removing an access option from presets if there is a locked instance

Bug 1475104

To test:

Edit the access rules for a profile page

Change-Id: If5d4bbbfd63a4e758635217380ae3598b14440ea
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>

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

Title:
  Trying to add same access permission as a existing locked option gives
  error

Status in Mahara:
  In Progress

Bug description:
  When editing the access on a page such as Profile page if you try to
  add a 'registered users' access permission that is different to the
  locked one it throws error.

  When in reality one shouldn't be able to even add an access permission
  of the same type if it has a locked instance.

  Either we need to hide that option on page load or have some
  javascript check to say 'Hey no, that is not allowed'

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