You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When logging in as user which has read-only rights on some specific collection and opening an entry of this collection, all fields are marked as read-only, which is fine. However, the user can restore previous revisions.
I would expect, that the user can see and examine previous revisions, but not restore them, e.g. the restore button in the 'revision overlay' could be disabled.
How to reproduce
Create a new entry in some specific collection.
Make sure the entry has multiple revisions.
Create a role which only grants access to the CP (access cp) and read access (view {collection_name} entries) of the specific collection.
Create a new user and assign the previously created role to it.
Log in as the new user and open the previously created entry.
Try to restore a previous revision (click 'View history' on the right panel -> select a revision -> click 'Restore' button in the top right corner -> confirm by clicking the popup's 'Restore' button)
Toast in the left lower corner says 'Revision restored' and the entry has the state of the selected revision.
Bug description
When logging in as user which has read-only rights on some specific collection and opening an entry of this collection, all fields are marked as read-only, which is fine. However, the user can restore previous revisions.
I would expect, that the user can see and examine previous revisions, but not restore them, e.g. the restore button in the 'revision overlay' could be disabled.
How to reproduce
access cp
) and read access (view {collection_name} entries
) of the specific collection.Logs
No response
Environment
Installation
Existing Laravel app
Additional details
No response
The text was updated successfully, but these errors were encountered: