I don't think I agree with either solution really, because if you add some views, and then navigate away without clicking any of the next/cancel/done buttons, you end up with a collection in a state where it has views in it, but all those views have different access rules.
That's a problem with both creating new views and creating new collections -- they're pretending to be a wizards when that's not really what they are (they have 'cancel' buttons down the bottom that aren't really cancel buttons, they're 'delete' buttons). For views it's not so bad, because a half-created view is pretty harmless - only the owner can see it. With collections you end up with broken links which is worse, and potential upgrade headaches for us later on when we eventually merge access across collections properly in the db. So I'd prefer to either: (1) leave it as it is, and add a message to the user to say what access was added every time views are added (admittedly this is still a bit yuck), or (2) Change the way the page works so that the views are not updated at all until you save the page (by clicking next/save) - then the cancel button really means cancel. We can tell the user at that time what access rules will be added. Stacey, I think you had a half-finished view picker widget that will do this job, right? -- 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? _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
