[MAGNOLIA-3456] Self-publishing a deleted page will make the page disappear even if the publication fails. Created: 07/Dec/10  Updated: 13/Dec/11  Resolved: 10/Jan/11

Status: Closed
Project: Magnolia
Component/s: activation, admininterface
Affects Version/s: 4.4, 4.4.1
Fix Version/s: 4.4.2, 4.5

Type: Bug Priority: Major
Reporter: Danilo Ghirardelli Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3250 Content deleted from authoring instan... 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   

This is something stupid I did, but I want to report it anyway because maybe it is just the symptom of a bigger issue.
This happens on Magnolia 4.4 and 4.4.1, with or without workflow module. Steps to reproduce:

  • change the active subscriber to the same instance in use (making Magnolia pointing to itself)
  • delete a page (you'll see the new icon and such)
  • publish the change
    The publication fails (as expected), but the deleted page is gone.

Making an instance point to itself is just stupid and pointless, I know, and it's not something you should usually do. Until the previous version any activation would just do almost nothing (or fail sometimes), and any de-activation would simply fail (it's quite obvious). With the new version I would expect a similar behaviour, but the deleted page is gone even if the activation failed.
By the way, I may expect that self-publishing a deleted page would really delete the page, I do not expect that the page is gone after a failure... The question may be: what to do with an authoring error happened after the page was succesfully deleted on the public machine? If the activation should be considered transactional, should the page be restored on the public machine in case of an authoring error after deletion?



 Comments   
Comment by Jan Haderka [ 10/Jan/11 ]

As you already know, this kind of configuration is not supported.
However some of the problems that occurred might happen also when running concurrent activation workflows for the same content. I've improved the error handling on those situations to make sure nicer and more meaningful errors are printed when system can't cope with the situation.

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