[MGNLACTIVATION-49] Deleted node is not deactivated from public instance if "delete" command is used Created: 20/Nov/13  Updated: 13/Jan/14  Resolved: 21/Nov/13

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1.1, 5.2

Type: Bug Priority: Blocker
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLACTIVATION-78 Deactivation command should not be tr... Closed
is causing MGNLACTIVATION-69 Non-activated nodes cannot be deleted... 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.2-rc2

 Description   

If "delete" command is used then node is not removed from public instance. It's only removed from author. Correct behaviour should be that the node is removed from both instances.

"markAsDeleted" command works as expected. When node is marked as deleted then you have to confirm deletion by "Publish deletion" and then node is correctly deactivated from public instance.

How to reproduce:
1. The easiest way is use configuration app where "delete" command is used.
2. For example under /modules/core create node named "TestDeletion"
3. Activate "TestDeletion" node and check if node exist on public instance
4. Remove "TestDeletion" node from author instance
5. "TestDeletion" node still exist on public instance



 Comments   
Comment by Jan Haderka [ 20/Nov/13 ]
  • The update task should check and perform only if no one modified that command by themselves yet (i.e. check the class value as well).
  • make sure that if deactivation command fails, the chain doesn't continue.
Comment by Milan Divilek [ 20/Nov/13 ]

make sure that if deactivation command fails, the chain doesn't continue.

If deactivation command fails (for example when public instance is unreachable) then you will get error message that the command couldn't be done. And content is not removed from author instance.

Generated at Sun Feb 11 22:59:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.