Actions
Bug #5235
closedFilter creation allows me to enter and save with a field that isn't available for searching and blows up the resulting entity page
Description
1. Create a New Role
2. Click to add new Filter
3. Select 'Domain'
4. Add all permissions for Domain
5. Enter 'anything = 4' into the Search box
6. click 'Submit' (Note: no validation to stop you from saving this invalid filter)
7. Grant Role to user without any other permissions
8. Log in as new user
9. Navigate to Domains page
10. Attempt to create a Domain
Error output "Invalid search query: Field 'anything' not recognized for searching!"
Updated by Dominic Cleal over 10 years ago
- Category set to Users, Roles and Permissions
Updated by Dominic Cleal over 10 years ago
- Blocks Tracker #4552: New permissions/authorization system issues added
Updated by Anonymous about 10 years ago
- Status changed from New to Assigned
- Assignee set to Anonymous
Updated by Anonymous about 10 years ago
- Status changed from Assigned to Ready For Testing
Updated by Anonymous about 10 years ago
- Target version changed from 1.8.1 to 1.8.0
Updated by Dominic Cleal about 10 years ago
- Translation missing: en.field_release set to 18
Updated by Anonymous about 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 0545fd10e610f350e1b43783d3073ab2296bdf33.
Updated by Dominic Cleal about 10 years ago
- Related to Bug #6830: upgrade 1.4.5 to 1.5.2 results in "Invalid search query" error added
Actions