[MAGNOLIA-1007] Sort order of website on public side is not in sequence but in chronology of activation. Created: 17/Aug/06 Updated: 30/Sep/13 Resolved: 26/Feb/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0 RC2 |
| Fix Version/s: | 3.0 RC4, 3.0.2 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Thomas Martin | Assignee: | Christopher Zimmermann |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Tested on several environments (mac os x, solaris, win xp) all affected |
||
| 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 |
|
When activating pages from author to public instance the sequence of the pages gets messed up. IE: a website tree on the author looks as following:
if user activates them one after each other (a, b, c) everything works fine - BUT if user activates them in a different order (eg. b,c,a) order on public site is according to activation chronology which means the tree on the public instance looks as following:
To wrap it up: order on the public side is not in sequence but in chronology of activation. |
| Comments |
| Comment by Philipp Bracher [ 18/Aug/06 ] |
|
This is a blocker and we are already aware of that. Thanks for reporting. |
| Comment by Philipp Bracher [ 18/Aug/06 ] |
|
Just for the insiders:
Therfore we need to activate the additional ordering invormation (since not in the standard import/export) and move the page to the right place after activating. |
| Comment by Sameer Charles [ 21/Aug/06 ] |
|
This is not so trivial, content subscribers could subscribe to receive content from different authoring systems and if the set of pages are not identical on subscriber its almost impossible to keep the ordering unless we sent the the ordering of "all" siblings (could be thousands of sublisgs of a given page) with each activation request. |
| Comment by Sameer Charles [ 07/Sep/06 ] |
|
on svn |
| Comment by Tom Wespi [ 12/Dec/06 ] |
|
with magnolia EE 3.0.1 running with BDB (je-3.2.13.jar) the problem is still there |
| Comment by Sameer Charles [ 12/Dec/06 ] |
|
this happens if you have versioning command before activation command. I will have a look... |
| Comment by Sameer Charles [ 19/Dec/06 ] |
|
its on svn |
| Comment by Sameer Charles [ 26/Feb/07 ] |
|
tested:
|