[MAGNOLIA-2527] Moved pages should not have a green icon Created: 30/Dec/08  Updated: 23/Jan/13  Resolved: 27/Jan/09

Status: Closed
Project: Magnolia
Component/s: activation, admininterface
Affects Version/s: 3.6.3
Fix Version/s: 4.0, 3.6.4, 3.6.5

Type: Bug Priority: Blocker
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
relation
is related to MAGNOLIA-2173 Moving / rename a page on author sho... Closed
is related to MAGNOLIA-2690 Renaming content causes bogus deactiv... Closed
is related to MAGNOLIA-2843 Copied/moved pages should not have a ... 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   

Since MAGNOLIA-2173, moving a page does not deactivate it automatically. However, since the page needs to be activated again for the move to "appear" on the public instances, it is confusing that a moved page still has a green icon.



 Comments   
Comment by Edgar Vonk [ 30/Dec/08 ]

But it does not? At least not in our environment. The page that has been moved has a red icon. Our client interprets this as: "this page has apparently been deactivated". However, this is not the case at all. Our client thinks this is very confusing.

Comment by Magnolia International [ 30/Dec/08 ]

In any case, it should be orange (edited - needs reactivation for changes to be taken into account)

Comment by Magnolia International [ 20/Jan/09 ]

See SUPPORT-196 - it seems the color is currently undefined - I get it green, Edgar gets it red.

Comment by Jan Haderka [ 27/Jan/09 ]

Done as of r21813 on trunk and as of r21814 on 3.6 branch.

Comment by Jan Haderka [ 27/Jan/09 ]

For the curious:
Seemingly undefined default color is actually determined based on the original status. If nodes were imported/bootstrapped with status "activated" (green), but were never actually activated (content.getMetaData().getLastActionDate() == null), their status will be determined in MetaData.getActivationStatus() as "activated" (green) even after the move). In this case it is impossible to determine whether status is valid (maybe there is no subscriber and there is no activation to be made, e.g. when serving content directly from the author).
Once document have been at least once published, the LastActionDate will be set and ActivationStatus will be determined properly as modified (yellow) with this fix (or as deactivated (red) prior to this fix).

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