Bug #40819
closed
Epic #90674: Backend UI not reflecting permissions
Edit icons (pencils) still visible in WS even though use has no modify access
Added by Bart Dubelaar almost 12 years ago.
Updated about 3 years ago.
Description
When a user had no access to modify a certain table (as defined in access lists) then the pencils in the record listing are not shown. This doesn't work when working in a workspace. The pencils are still there and clicking them will get you in a blank screen that you cannot exit.
There are even save buttons in the top toolbar that generate a token error when clicking them.
Holds for 4.5 up till 6.0
I now see that this doesn't work in the Live workspace either! Pencils only disappear when setting editing permissions in the access module.
Still believe that this is buggy..
- Status changed from New to Accepted
- Target version set to 4.5.20
Reproducing:
- edit non-admin user / usergroup
- Access lists > Tables (listing) > mark "Website User"
- Access lists > Tables (modify) > make sure "Website User" is NOT checked
This user can now view the FE users, has access to the edit icon, but sees a blank form.
- Target version changed from 4.5.20 to 7.1 (Cleanup)
- Is Regression set to No
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Category changed from Backend User Interface to Workspaces
- Target version deleted (
7.5)
still an issue on 8.2-dev (latest master)
The issue is still present on 10.4.0-dev; it is not related to workspaces IMHO, as it occurs even on LIVE workspace, just entering the list view and you'll see an edit icon on the records that the editor is not supposed to modify.
- TYPO3 Version changed from 6.0 to 9
- Related to Bug #89307: List Module shows edit action icon even if User has no edit permission added
- Parent task set to #90674
#89307 has been solved, is this solved, too? How can it be tested? (See #90954 that's why I ask)
- Status changed from Accepted to Closed
Just checked this and as Riccardo already mentioned, this was fixed with #89307. #90954 does not seem to be related.
I'll therefore close this issue. If you still experience this bug, please contact me so I can reopen the issue or directly create a new one.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by