Actions
Bug #7615
closed
Unable to create a non-taxonomy role filter when current context set
Status:
Closed
Priority:
Normal
Assignee:
Category:
Organizations and Locations
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
As admin, visit try creating a new role filter in the UI for resource type Role. After submit no error message is displayed but the create page remains (versus normal behavior of returning to full list of filters). Looking at log an error is present of "Failed to save: Organization ids You can't assign organizations to this resource".
Updated by
Updated by Dominic Cleal about 10 years ago
- Related to Bug #5541: Filter of resource type Organization can result in error condition when trying to access organization resources added
Updated by Dominic Cleal about 10 years ago
- Subject changed from unable to create a role filter to Unable to create a non-taxonomy role filter when current context set
Only happens when multi-org's enabled and a current context is set, then the current context's added to the filter.
Looks like the add_current_* methods aren't being overridden correctly, they're overridden as class methods when they're actually instance methods.
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2291 added
- Pull request deleted (
)
Updated by Marek Hulán over 9 years ago
- Category changed from Users, Roles and Permissions to Organizations and Locations
- Assignee set to Marek Hulán
Thanks Dom, fixed the scope of methods.
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 28
Updated by Marek Hulán over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 76fca93b0093e9b4174d1a888ffca9f3fcb886c9.
Actions