mahara-contributors team mailing list archive

[Dan Marsden <dan@xxxxxxxxxxxxxx>]

+1 from me to update access on final stage (sounds like the easiest
option)

unless it's easier to store original access details on views and if they
remove it from the list/cancel the update/creation then revert to
original access

-- 
Collection: view access updating at problematic time
https://bugs.launchpad.net/bugs/619867
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: New

Bug description:
When a user creates a new collection and they get to the views stage access for each views access is updated immediately as it is added.  

This means that if a user decides that they don't want the collection anymore and cancel then the view access is already updated and they have lost original settings on views.

The user might also just add a view and then immediately decide that wasn't the right decision and remove from the list.

This is an issue for both new and existing collections.

The help file does mention this is going to happen, but I'm thinking it is not the most appropriate event for access updating to occur on anyway.

Solutions might be to:

For new collections:
a) update access only on the final stage when user saves collection completely
b) alert user somehow that views are going to have their access updated when they navigate past the views page

For existing collections:
a) only update when the user is completely finished with the page (clicking 'Done') and ensure it is clear that the access will be updated at this time

Any other ideas?