[MAGNOLIA-3717] Provide Activation Lock for Authoring Instances Created: 27/May/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: activation, admininterface, core, workflow
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: Maximilian St√∂rzer Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Magnolia is often used in enterprise environments with a cluster of public instances used to serve contents to the user. However, in case of maintenance for the public instances, activation from the authoring system is still active and may result in data corruption in the public systems.

Transactional activation only partly addresses this topic, as activation of trees may fail "in the middle" of the activation, leaving a partly published tree on both nodes (no rollback).

In case of maintenance work for one public node, it should be possible to deactivate activation altogether before starting maintenance work on the public instace. This activation lock must be respected by any Magnolia module, inclusive website, dms, data and workflow (including times activations).

Current workaround is to shutdown the authoring system so prohibiting work on the website altogether.



 Comments   
Comment by Zdenek Skodik [ 30/May/11 ]

At the moment it's possible to temporarily disable activation per subscriber - active = false at /server/activation/subscribers/<my_dear_public>

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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