[MAGNOLIA-2767] Multi subscribers with various toURI for the same content Created: 08/Jun/09  Updated: 08/Jun/09  Resolved: 08/Jun/09

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.6.5
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Francis BORRAS Assignee: Philipp Bärfuss
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris / Sparc


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   

We have just migrated from Magnolia 3.5.8 to 3.6.5 with XA activation,
and we have a problem when activating content.

We have 3 Magnolia instances. 1 author and 2 public (public1 and
public2).
In author website, we have 3 pages :

  • Page1
    • Page2 (child of Page1)
      • Page3 (child of Page2)


The goal is to activate all pages to public1 and only Page1 sub-pages
(Page2 and Page3) to public2 root.
After activation, we want the following result on the public instances :
Public1 (same as author) :

  • Page1
    • Page2 (child of Page1)
      • Page3 (child of Page2)

Public2 :

  • Page2 (child of root)
    • Page3 (child of Page2)


In the author subscribers we have :

  • public1 - fromURI : / - toURI : /
  • public2 - fromURI : /Page1 - toURI : /


Results :

1/ When activating Page1, it appears on both public1 and public2, so the
same behavour. This is NOT what we want for public2.

2/ When activating Page2, it appears on both public1 and public2 as a
child of "Page1".

3/ Trying to workaround the problem, on public2, we moved Page2 to / ,
then deleted Page1.

4/ When activating several times Page2, it is always correctly activated
on public2 to /Page2, but on public1, sometimes it is correctly
activated to /Page1/Page2, and the other times it is moved to / !!?

5/ When activating several times Page3, sometimes it is correctly
activated on both (to /Page1/Page2/Page3 on public1 and /Page2/Page3 on
public2), and the other times it fails with "Parent not found (not yet
activated): /Page2 on public1).

It seems this is a bug, as activation results can fail (randomly?).



 Comments   
Comment by Zdenek Skodik [ 08/Jun/09 ]

Hi,

This Jira project is used to report bugs and improvements on the current codebase, specifically for the Packager module.
For such questions or issues, please use either the mailing lists or your dedicated support.

So please move this content into your channel SUPPORT-327 using Edit this issue button on left bar of your support issue. Thanks.

Best regards,
Zdenek

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