[MAGNOLIA-1189] Order changes to webpages are not reflected in the subscriber sites Created: 08/Nov/06 Updated: 23/Jan/13 Resolved: 06/Dec/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0 RC4 |
| Fix Version/s: | 3.0.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Travis Melhiser | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Tomcat 5.5.20, FireFox 1.5.06 |
||
| 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 a webpage is reordered in the Authoring environment, the changes in the order are seen during a preview of the pages. However, when the page is activated, the subscribers do not reflect the ordering change. |
| Comments |
| Comment by Magnolia International [ 14/Nov/06 ] |
|
From what I see with the current trunk, if you move a single page and activate that page, it works. However, I can indeed reproduce the problem that the ordering is not kept if you move multiple pages and activate the parent ("including sub pages"). Could you be please a bit more explicit in your scenario ? |
| Comment by Magnolia International [ 14/Nov/06 ] |
|
Also, as a workaround, you can de-activate the parent of the pages you moved, then re-active it ("including sub pages"), and the order should be restored properly. |
| Comment by Travis Melhiser [ 14/Nov/06 ] |
|
I will have to check out the current trunk to verify its behavior. The version this is tested against has this build date: --------------------------------------------- When changing a page order, an alert message is displayed saying: "The node /xyz/abc/123 will be de-activated immediately. Are you sure to continue?" After selecting the OK button the page is reorderred, however the page is not de-activated from the public site, nor is it flagged as having changed in the Author site. If the page is activated on it's own, the ordering change is reflected on the Public site. However if multiple pages are re-ordered, then each page individually activated, the ordering is not correct. By selecting the parent page to acivate-including-subpages, none of the ordering changes are visible. Depending on the number of sub-pages and the amount of data held within them, it is not always acceptable to de-activate the partent due to the potentially long publish time for all of it's children. In the interum this is at least an option to ensure that the ordering is correctly replicated to the Public instance. |
| Comment by Philipp Bracher [ 17/Nov/06 ] |
|
This is urgent |
| Comment by Sameer Charles [ 17/Nov/06 ] |
|
it will be fixed together with |
| Comment by Philipp Bracher [ 17/Nov/06 ] |
|
Hm, we produced this error by reordering one page and activate a single page. I'm not sure if |
| Comment by Sameer Charles [ 21/Nov/06 ] |
|
maintaining transaction will not only help in maintaining order but also to reduce redundent cache flushing. |
| Comment by Sameer Charles [ 27/Nov/06 ] |
|
fixed on svn, This will be changed together with the implementation of transactions |