On Nov 10, 2011, at 1:40 PM, Oren Livne wrote:
Dear Nate,
Uncommenting those three lines worked. I also tried to implement a change to the Grids feature that would allow injecting app.config into Grids, but this doesn't work yet. (Are all variables such as operations and standard_filters read and used by the framework as static vars even before a UserListGrid object is created?)
Hi Oren, Unfortunately, I'm not familiar enough with Grids to be able to answer this off the top of my head.
I can now see the Delete, Undelete and Purge buttons. Is there a way to permanently delete a user from the database? What does the purge feature do?
There's no way to do this from the Galaxy application, since it breaks one of Galaxy's goals of permanence and reproducibility. There are quite a few references to user records in other tables, so deleting the user would leave these dangling. Purging a user removes all of the user's saved data from the instance. --nate
Thanks so much, Oren
Hi Oren,
Hrm, it looks like the option to delete users was removed from the interface since it couldn't be made conditional on a configuration setting (due to a limitation in Galaxy's "Grids" feature, which is used to display the table of users in the UI). They can be added by uncommented lines 98-100 in lib/galaxy/web/controllers/admin.py:
#operations.append( grids.GridOperation( "Delete", condition=( lambda item: not item.deleted ), allow_multiple=True ) ) #operations.append( grids.GridOperation( "Undelete", condition=( lambda item: item.deleted and not item.purged ), allow_multiple=True ) ) #operations.append( grids.GridOperation( "Purge", condition=( lambda item: item.deleted and not item.purged ), allow_multiple=True ) )