[MGNLUI-3053] Reconfigure availability of de/activation actions in Security app Created: 30/May/14  Updated: 11/Jul/14  Resolved: 10/Jul/14

Status: Closed
Project: Magnolia UI
Component/s: security app
Affects Version/s: None
Fix Version/s: 5.2.7, 5.3.1

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

Issue Links:
Relates
relates to MGNLUI-2939 Reconfigure availability of de/activa... Closed
relation
is related to MGNLUI-2945 Action availability with writePermiss... 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)
Date of First Response:
Epic Link: publishActionsAvailability

 Description   

Since any de/activation request actually attempts to write to involved node/s, to update its metadata, the actions should be implicitly allowed only for users having write permissions to them. Since MGNLUI-2510 it's trivial to restore this former 4.5 like behaviour. Thes to any actions resulting in write events.



 Comments   
Comment by Peili Liang [ 17/Jun/14 ]

@Roman Kovařík, why I can not find magnolia-module-public-user-registration-2.2.x ?

Comment by Roman Kovařík [ 17/Jun/14 ]

2.2.x was raised to 2.3 and 2.2.x haven't been created yet. Feel free to create it from the tag magnolia-module-public-user-registration-2.2.3 and revert the last 'prepare-release' commit.

Comment by Evzen Fochr [ 10/Jul/14 ]

Action "activateRecursive" should be affected too, but isn't right now.
When you log in as user peter and go to pages, you still can active "Publish incl. subpage"s on pages with subpages (i think it shouldn't be able).

Comment by Daniel Lipp [ 10/Jul/14 ]

On top my port to master wasn't right: setting the property has to be done in 5.3.1 versionHandling section as only then we'll end up having the proper value when someone is migrating from 5.3.

Generated at Mon Feb 12 09:02:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.