[MAGNOLIA-136] Actiavation when parent page is not activated Created: 26/Oct/04  Updated: 23/Jan/13  Resolved: 10/Oct/05

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.0 Final
Fix Version/s: 2.1.1, 3.0 Beta 1

Type: Bug Priority: Minor
Reporter: Vinzenz Wyser Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Activation metaData of the requested page is set to activated



 Comments   
Comment by Boris Kraft [ 08/Nov/04 ]

If parent page does not exist on a subscribing instance (e.g. on public) then activation fails but is indicated as successful.

In 1.1 we automatically activated the parent page after user confirmation. This is not done anymore as it was cumbersome. For now one has to activate the parent pages manually first.

To fix current behaviour, do not set status to activated if parent pages do not exist.

Comment by Boris Kraft [ 15/Jun/05 ]

Anoher option would be to grey out activation if parent pages are not existent on subscriber

Comment by Sameer Charles [ 05/Oct/05 ]

svn branch 2.1.1 and Trunk not in sync, it has been fixed on branch 2.1.1

Comment by Philipp Bracher [ 10/Oct/05 ]

Commited

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