mahara-contributors team mailing list archive

[Kristina Hoeppner <605705@xxxxxxxxxxxxxxxxxx>]

Hi Craig,

Thanks for getting back to this bug. I've revisited the page again and
have the following suggestion to make it clearer:

Do you really want to delete this View? It cannot be undone.

Note: None of the content blocks that have been added to the view will be deleted unless it is a Textbox block. 
However, any feedback placed against the view will be deleted. Consider backing up the view by [link to the export]exporting it[/link end] first.

[Yes] [No] (so that users have to read through the note. Otherwise it
may be too tempting to overlook it.

I would not use a question on that page that can be answered by Yes or
No because that could be confused with the buttons Yes and No.

The X for "Delete" is used throughout Mahara for removing and deleting
items, e.g. also in Files, Blog. the view deletion is a combination of
removing and deleting: the view itself is like a block in a view: it
gets removed, but it can be brought back again. However, the feedback
and the textbox block are items that are deleted.

I would not introduce a new icon that is not used elsewhere when we have
used the X consistently (at least to my knowledge), though we are not
yet consistent in the image. I think we have two different ones at the
moment (one primary one -> the big button, and a smaller one for blog
posts and files).

Kristina

-- 
More information when deleting a view
https://bugs.launchpad.net/bugs/605705
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: In Progress

Bug description:
Hello,

"Do you really want to delete this View? It cannot be undone." –> Some users may ask if their files and blog entries will also be lost when the view is deleted. 

Maybe a sentence should be added along the lines of "All your files and blog entries that you linked in this view will still be available. However, if you have written text directly into text boxes, this will be gone." 

BUT if text boxes also get the artefact status then the second sentence becomes redundant. 

Maybe we can also provide a link to the portfolio export. That could be used as backup (they could always do an HTML export to freeze their portfolio in time). E.g. "If you want to create a copy of your portfolio in the state it was in before deleting, you may want to [link]export[/link] it before you delete this view."