Bug #75890

Epic #90674: Backend UI not reflecting permissions

editor with only read access to page - some interface improvements

Added by Riccardo De Contardi over 5 years ago. Updated 11 months ago.

Status:
New
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-04-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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 all

Hope I made myself clear enough. have a nice day.


Files

schermata1.png (29.1 KB) schermata1.png Riccardo De Contardi, 2016-04-24 10:02
schermata2.png (16.9 KB) schermata2.png Riccardo De Contardi, 2016-04-24 10:02
schermata3.png (30 KB) schermata3.png Riccardo De Contardi, 2016-04-24 10:02

Related issues

Related to TYPO3 Core - Bug #73591: Page Module: Click menu in content elements missing if editor has only read accessClosed2016-02-22

Actions
Related to TYPO3 Core - Task #79364: Move page module function `QuickEdit` to EXT:compatibility7Closed2017-01-18

Actions
Related to TYPO3 Core - Bug #14238: User cannot save existing page if page-type is not allowed by backend-group configClosed2004-07-14

Actions
#1

Updated by Riccardo De Contardi almost 5 years ago

same issue for 8.5-dev (latest master)

#2

Updated by Josef Glatz over 4 years ago

  • Description updated (diff)
#3

Updated by Riccardo De Contardi about 3 years ago

Same error occurs on 8.7.15 and 9.4.0-dev (latest master)

#4

Updated by Riccardo De Contardi about 3 years ago

  • Related to Bug #14238: User cannot save existing page if page-type is not allowed by backend-group config added
#5

Updated by Susanne Moog almost 3 years ago

  • Sprint Focus set to On Location Sprint
#6

Updated by Susanne Moog over 1 year ago

  • Sprint Focus deleted (On Location Sprint)
#7

Updated by Riccardo De Contardi over 1 year ago

  • Parent task set to #90674
#8

Updated by Riccardo De Contardi 11 months 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.

Also available in: Atom PDF