[MGNLACTIVATION-35] Cannot publish demo-project pages marked for deletion Created: 03/Oct/13  Updated: 28/Aug/15  Resolved: 28/Aug/15

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.0.2
Fix Version/s: 5.0.x

Type: Bug Priority: Major
Reporter: Jozef Chocholacek Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

When a page bootstrapped on install (/demo-project/*) is marked as deleted on author, and you try to publish it, it is deleted from author, but not from public.

The log on author says e.g.
INFO info.magnolia.module.activation.BaseSyndicatorImpl: Exchange: activation succeeded [/demo-project/service/dummy-events/another-event-5]

but on public:

INFO info.magnolia.module.activation.ReceiveFilter : User superuser succeessfuly deactivated null on magnoliaPublic.
or
INFO nolia.module.exchangetransactional.XAReceiveFilter: null User superuser successfully deactivated null on magnoliaPublic.

If the page is first created and published "manually", and marked as deleted only then, the publication of such deletion works properly.



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

It seems that it is enough to activate any of the bootstrapped pages manually, and the activation of deletion gets to normal. But when you try it right after the installation, it is broken.

Setting the priority to Major, as it is a bit unlike situation that someone will test the activation of deleted (marked as deleted) page as the very first thing after the installation.

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