mahara-contributors team mailing list archive

[Mahara Bot <1266317@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/3077
Committed: http://gitorious.org/mahara/mahara/commit/415308d2fbf07d2b8016f8c2843b30f1ac445f2f
Submitter: Aaron Wells (aaronw@xxxxxxxxxxxxxxx)
Branch:    1.8_STABLE

commit 415308d2fbf07d2b8016f8c2843b30f1ac445f2f
Author: Mike Kelly <m.f.kelly@xxxxxxxxxx>
Date:   Wed Dec 4 16:04:14 2013 +0000

Check for institutional ownership of custom layout when importing LEAP2A

Bug #1266317

Change-Id: If065430bfd50b94597788c0ede91303cd1b476eb
Signed-off-by: Mike Kelly <m.f.kelly@xxxxxxxxxx>

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

Title:
  Institution/group ownership of custom flexible layouts

Status in Mahara ePortfolio:
  Fix Committed
Status in Mahara 1.8 series:
  Fix Committed
Status in Mahara 1.9 series:
  Fix Committed

Bug description:
  I came across a nasty bug in the mahara custom layouts feature.

  If a user saves a custom layout from within a group, the view owner is null, so usr in the usr_custom_layout table is set to be 0.
  This means that the saved custom layout becomes available to all users, so the advanced layout options area gets cluttered quite quickly.

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