mahara-contributors team mailing list archive

[Richard Mansfield <620258@xxxxxxxxxxxxxxxxxx>]

Stacey,

It actually used to realise the view was part of a collection, but you
broke that behaviour with 528d83b5 (grr!).  I've just replaced the lines
that did this (see db0750c3), but I guess you might want to try to
remember if you had some other good reason for removing them earlier.

** Changed in: mahara
       Status: New => Fix Committed

** Changed in: mahara
   Importance: Undecided => High

** Changed in: mahara
     Assignee: (unassigned) => Richard Mansfield (richard-mansfield)

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

-- 
View access accessible when view is in a collection
https://bugs.launchpad.net/bugs/620258
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: Fix Committed

Bug description:
When a view is in a collection, its "Edit Access" page is still accessible and the access rights can be changed. When I went into the collection access rights, the new user had been added as well though I did not get a message on the view access page telling me that I update the collection access at the same time. 

When I go to the view access page of another view in the same collection, I still have the old access rights in there.

As collection access rights overwrite view access rights, I would disable the "Edit View Access" link on a view that sits in a collection. The user cannot get to it from the view overview page - why should he get to it on the actual view? That would make it easier to edit the access rights for a collection really only on the collection page.