Bug #75890
open
Epic #90674: Backend UI not reflecting permissions
editor with only read access to page - some interface improvements
0%
Description
Steps to reproduce the issue
1) set up a page where an "editor" BE user has ONLY the "show" permission.
2) translate also the page on an alternative language
3) enter as the editor, go to the page and do the following:
3.1) Switch to "languages" view
RESULT:¶
see attached file schermata1.png
- the "edit" pencil icons are still present
3.1.1) if you click on the pencil > see attached file schermata2.png- the error is not much evident (maybe a Bootstrap alert panel would be better)
- the name of the user should be used instead of/altogether with the id
- the name of the page should be used instead of/altogether with the id
- the error number "1437679336" should not be shown - for the editor, it means nothing
- last but not the least, it should be better to not show the pencil at all, I guess.3.2) Switch to "quickedit" view
RESULT:¶
see attached schermata3.png
- the error is not much evident (maybe a Bootstrap alert panel would be better)
- if you click on the arrows, nothing happens; again I guess it should be better to not show them at allHope I made myself clear enough. have a nice day.
Files
Updated by Riccardo De Contardi about 8 years ago
same issue for 8.5-dev (latest master)
Updated by
Updated by Riccardo De Contardi over 6 years ago
Same error occurs on 8.7.15 and 9.4.0-dev (latest master)
Updated by Riccardo De Contardi over 6 years ago
- Related to Bug #14238: User cannot save existing page if page-type is not allowed by backend-group config added
Updated by Susanne Moog about 6 years ago
- Sprint Focus set to On Location Sprint
Updated by Susanne Moog almost 5 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Riccardo De Contardi over 4 years ago
Still present on 11.0.0-dev (latest master);
- the error is now a Bootstrap alert panel
- the part about "quickedit" view can be ignored ("quickedit" is no more present)
I just discovered that even the "translate" dropdown is operable, but - as the editor does not have write permission on the page, another error message is. triggered, but now the page is greyed out with a semitransparent layer and with an infinite loader animation. The editor is stuck in this page; you have to reload the page or the browser to exit it.
Updated by Riccardo De Contardi about 3 years ago
- Related to Task #94629: Simplify and optimize the readability of the page module interface added
Updated by Riccardo De Contardi 6 months ago
- File Cattura.png Cattura.png added
I repeated my test on TYPO3 13.2.0-dev and these are the results:
- The buttons "1" are still working, but they lead to an alert:
Sorry, you didn't have proper permissions to perform this change. No page edit permission for user 2 on page 795 1437679336
Edit form could not be loaded The edit form could not be loaded for the requested records. This might be due to insufficient permissions.
Again, I think it would be better not to show them at all
- the button 2 works; it opens the usual translation wizard; you can go through all the steps of the wizard, and in the end..nothing happens. No error message, nothing. The translation simply does not create any content element. (tested with both "Translate" and "Copy")
- if there is still another language to which you can translate the page, the dropdown works, but it leads to an exception:
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception PHP Warning: Undefined array key "NEW6664ae149ad80280765212" in /var/www/html/typo3/sysext/core/Classes/DataHandling/DataHandler.php line 4899
Same as before: it would be better to hide it
Updated by 
