[MGNLPN-147] Disable unsupported actions on a selected variant node Created: 06/Jun/14  Updated: 05/Apr/17  Resolved: 06/Jun/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLPN-375 Enable Change template and Show versi... Closed
duplicate
duplicates MGNLPN-143 Review actions and availability for s... Closed
supersession
supersedes MGNLPN-129 Review actions and action availability 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

In essence, a page variant should look and feel like a regular page. We thus show all actions just like we would for the regular page, but disable some: those that are (currently) not supported.

However, currently, if a single page variant is selected, some actions are available that cause problems as they're not properly supported. Other actions may cause problems, but whether they cause problems or not has to be researched.

  • Add page (disabled), Delete page
  • Preview page, Edit page, Rename page (disabled - currently hidden), Duplicate page, Change template (enabled, if it works), Move page (disabled)
  • Publish, Publish w sub pages (disabled), Unpublish
  • Add page variant (disabled), Choose audience
  • Versioning actions
  • Import/export actions

= not currently as it should be
= research, if these actions could be left enabled, else disable them.



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

This should be already fixed by MGNLPN-143.

Generated at Mon Feb 12 06:34:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.