[MGNLUI-3144] Activation menus / actions should not be enabled if ancestors have not been published Created: 09/Sep/14  Updated: 06/Aug/15  Resolved: 01/Dec/14

Status: Closed
Project: Magnolia UI
Component/s: app framework, pages app
Affects Version/s: 5.3.2, 5.3.3, 5.3.4
Fix Version/s: 5.3.6

Type: Bug Priority: Major
Reporter: Lars Fischer Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: frontend, support, usability, ux, uzh
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLDAM-566 Activation menus / actions should not... Closed
is cloned by MGNLUI-3300 Port IsPublishableRule to 5.4 Closed
is cloned by PAGES-2 Activation menus / actions should not... Closed
relation
is related to MGNLUI-3277 Apply IsPublishableRule to existing a... Closed
is related to MGNLUI-3230 Publishing and long running task defects 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   

The menus / actions for publishing a page should not be enabled until all ancestors have been published. Otherwise this leads to confusing errors in the log like

"Message received from subscriber: Parent content /restore/blabla/publications is not yet activated or you do not have write access to it. Please activate the parent content before activating children and ensure you have appropriate rights on blabla01"

It's also the wrong behavior from a usability standpoint.



 Comments   
Comment by Federico Grilli [ 01/Dec/14 ]

Since it is desirable that such a rule be applied to other apps too (other than pages) and given the already packed changelog for 5.3.6, a follow-up issue is going to be created addressing that.

Comment by Espen Jervidalo [ 03/Dec/14 ]

I suggest not merging this one into master. Pages app has been extracted. It's probably easier to fix the yet-to-be-created follow up correctly on master? Of course we will need update tasks in pages module nevertheless.
-> removed the 5.4 fix version.

Comment by Peili Liang [ 09/Dec/14 ]

The pages app has supported the function, others app will be supported in https://jira.magnolia-cms.com/browse/MGNLUI-3277

Comment by Adrian Andermatt [ 25/Mar/15 ]

Should be implemented for Assets too! I'd suggest to reopen the ticket, wouldn't you?

Comment by Federico Grilli [ 25/Mar/15 ]

Hi Adrian, I created a follow-up issue in DAM project which clones this one

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