Custom Query (2152 matches)
Results (1021 - 1023 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1063 | fixed | Groups listing widget on package screen shouldn't show group name by default | sebbacon | sebbacon |
Description |
I've been asked if we can do something about the overflow of the Group name in the right hand column on this page:
The reason is that the list display for groups is in the form "group_tltie (group_name)", and of course group_name can't have spaces and so can't wrap nicely. I was wondering if there's a good reason why we don't only display group_title (if it exists) and group_name only when there's not a title? |
|||
#1064 | duplicate | Remove Workers from ckanext-queue | amercader | |
Description |
The current implementation of Workers in ckanext-queue is broken. Basically the various consume / callback functions expect three arguments (routing_key, operation, payload) when they are in fact receiving only two of them (message_data, message). This is fairly easy to fix, but the question is if Workers add an extra complexity to use the messaging library directly. |
|||
#1065 | fixed | [super] Change Authorization System | zephod | johnlawrenceaspden |
Description |
Child tickets
Old ticket description:
More info on Hierarchy changee.g. UserGroup? NHS contains the User nhsysadmin, as well as the UserGroups? SURREY and BERKS, which themselves contain users. One user in SURREY is Simon the Sysadmin, who has permissions on the whole system. His permissions should not leak out to other users or groups, and user permissions generally should not. Each Group has permissions over various objects. A user has permissions in his own right, and also has the permissions of his own group, and of all the groups contained in his group, and so on recursively. Algorithm: possible(user, action, package):
|