[MAGNOLIA-2173] Moving / rename a page on author should not deactivate it on public instances Created: 05/Jun/08  Updated: 23/Jan/13  Resolved: 22/Jan/09

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

Type: Improvement Priority: Critical
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1899 activation: if the page (uuid) exist ... Closed
relation
is related to MAGNOLIA-2131 Moving nodes can create inconsistent ... Closed
is related to MAGNOLIA-2527 Moved pages should not have a green icon Closed
is related to MAGNOLIA-2690 Renaming content causes bogus deactiv... Closed
is related to MGNLACTIVATION-67 Same name siblings Closed
supersession
is superseded by MAGNOLIA-2251 Deletion should not de-activate immed... 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)
Date of First Response:

 Description   

This is really annoying, especially when "refactoring" an existing website. The problem with the current activation mechanism is that activating the moved page would activate it in its previous location, because activation is uuid-based and does not check paths.



 Comments   
Comment by Philipp Bracher [ 11/Jul/08 ]

The needed changes in the tree are committed. But it will only work as expected once MAGNOLIA-1899 is solved.

Comment by Jan Haderka [ 14/Jul/08 ]

All works now.

Comment by Magnolia International [ 30/Dec/08 ]

Well, deactivation doesn't happen anymore indeed, but we still get the alert box!! this is VERY confusing.

Comment by Magnolia International [ 30/Dec/08 ]

Committed a quick fix to trunk and 3.6 branch. Needs to be reviewed and confirmed.

Comment by Magnolia International [ 09/Apr/09 ]

For the record - this was first fixed in 3.6, but reopened due to the popup still appearing. The temporary fix mentioned above was reviewed, despite this not being noted here, and thus finally re-fixed for 3.6.4

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