New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prevent group of users from deleting objects #218

Closed
mfrasca opened this Issue Jul 19, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@mfrasca
Member

mfrasca commented Jul 19, 2017

it happened: we had very absolute beginners as users, they had the task to add objects, they deleted one or two genus objects. the problem is that the software let them.
@KiliBio

@mfrasca mfrasca added the JBQ label Jul 26, 2017

@mfrasca mfrasca modified the milestone: JBQ-2017-1.0 Jul 26, 2017

@mfrasca

This comment has been minimized.

Member

mfrasca commented Jul 26, 2017

actually... why is it at all possible to delete a Family, by clicking yes to the question
screenshot from 2017-07-26 11-49-16
I think we should make it an option, which is reset to its default value at each session, no deletion allowed if cascading is needed.
and yes, also add a users group with limited permissions.

@mfrasca mfrasca self-assigned this Aug 1, 2017

@mfrasca

This comment has been minimized.

Member

mfrasca commented Aug 1, 2017

interesting enough: this is already so for Location:

    if len(loc.plants) > 0:
        msg = _('Please remove the plants from <b>%(location)s</b> '
                'before deleting it.') % {'location': loc}
        utils.message_dialog(msg, gtk.MESSAGE_WARNING)
        return
    msg = _("Are you sure you want to remove %s?") % \
        utils.xml_safe(s)
    if not utils.yes_no_dialog(msg):
        return

so I'm going to do the same also for Family, Genus, Species, Accession.

mfrasca added a commit that referenced this issue Aug 1, 2017

@mfrasca mfrasca closed this Aug 1, 2017

mfrasca added a commit that referenced this issue Aug 1, 2017

mfrasca added a commit that referenced this issue Aug 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment