[MAGNOLIA-5010] Add functionality to disable delete or move buttons on a component - port to master Created: 03/May/13  Updated: 25/Jun/13  Resolved: 14/May/13

Status: Closed
Project: Magnolia
Component/s: rendering, templating
Affects Version/s: None
Fix Version/s: 5.0

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-4476 Add functionality to disable delete o... Closed
dependency
depends upon MAGNOLIA-4989 Permissions for operations Closed
depends upon MGNLUI-1038 Add functionality to disable delete o... Closed
documentation
to be documented by DOCU-407 Disabling edit/move/delete buttons on... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Hi guys,

in our current Magnolia project we need to restrict the permission to delete an existing paragraph.
Users with a special role shall be allowed to edit an existing paragraph, but not to delete it.

In Magnolia versions prior to 4.5 it was possible to simply hide the "Delete" button by specifying an empty "deleteLabel" property in the <cms:editBar> depending on the current user role.
Looking into the source code of the new <cms:component> tag, we could not find a similar approach to restrict the appearance or the functionality of the "Delete" button.

Any hint would be helpful!

Best regards,
Daniel



 Comments   
Comment by Roman Kovařík [ 14/May/13 ]

Reopen and resolve to refresh the status.

Comment by Roman Kovařík [ 25/Jun/13 ]

Cloned because 4.5 version MAGNOLIA-4476 contains also fixes for 4.5 page editor.
Master fix for page editor is registered under MGNLUI-1038.

Generated at Mon Feb 12 04:01:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.