[MAGNOLIA-2204] Should not deactivate from public instances when status on author is not activated Created: 25/Jun/08  Updated: 18/Jul/14  Resolved: 04/Dec/13

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2251 Deletion should not de-activate immed... Closed
is related to MAGNOLIA-2864 Deactivating content before deleting,... 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

 Description   

When moving or renaming, pages or documents get deactivated immediately (which shouldn't be the case, really, but that's a larger task). The user at least gets a warning about this, except if the node's status was not "activated". Unfortunately, the deactivation still occurs in any case, so nodes get silently deactivated on public instances (this happens for instance with samples or bootstrap content which is not marked as activated, even though it somehow is in synch between the instances)



 Comments   
Comment by Magnolia International [ 11/Jul/08 ]

could possibly fixing this together with MAGNOLIA-2251

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