[MGNLWORKFLOW-158] activateDeletion action is not handled by the VersionHandler Created: 02/Oct/13  Updated: 04/Oct/13  Resolved: 04/Oct/13

Status: Closed
Project: Magnolia Workflow Module
Component/s: Base
Affects Version/s: 5.1
Fix Version/s: 5.1

Type: Bug Priority: Blocker
Reporter: Jozef Chocholacek Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLWORKFLOW-157 Some users (e.g. Eric) cannot publish... Closed
dependency
is depended upon by MGNLUI-2191 Missing i18n key: After deleting a pa... Closed
is depended upon by MGNLWORKFLOW-132 Deletion workflow message should not ... Closed
supersession
is superseded by MGNLWORKFLOW-160 ActivationAction must give proper res... 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:
Sprint: 5.1 - Final

 Description   

The version handler replaces /modules/pages/apps/pages/subApps/browser/actions/[activate|activateRecursive|deactivate] actions with startPublication|startPublicationRecursive|startUnpublication actions. But there is also 4th action, used to activate deleted pages: activateDeletion - and it is not replaced.



 Comments   
Comment by Jozef Chocholacek [ 02/Oct/13 ]

Luckily, as it uses the website-activate command, too, which is delegated to workflow-activate, the deletion is not immediately activated and the proper workflow is started. But it uses the wrong message to inform the user about that.

But because the parameters are not passed correctly to the workflow, the page is deleted on author instance, but not on public instance. The log says: INFO nolia.module.exchangetransactional.XAReceiveFilter: null User superuser successfully deactivated null on magnoliaPublic.

Comment by Magnolia International [ 04/Oct/13 ]

jchocholacek, that message is due to MGNLACTIVATION-35, nothing to do with installation/update of the workflow module

Generated at Mon Feb 12 10:07:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.