[MAGNOLIA-2713] different ordering of websites in Author and Public instances Created: 05/May/09 Updated: 23/Jan/13 Resolved: 12/Jun/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 4.0.1, 3.6.5 |
| Fix Version/s: | 3.6.6, 4.0.2 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Zdenek Skodik | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| 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 |
|
if I create the main page with subpages, activate them incl. subpages and then change the order of subpages and activate them incl. subpages once again, the order of subpages is different in Author and in Public instances as well. It was tested in Magnolia EE 3.6.3, 4.0.1, 4.1-SNAPSHOT. Example test:
When I create and move more subpages, the ordering is different also. |
| Comments |
| Comment by Boris Kraft [ 05/May/09 ] |
|
which activation (simple/XA?) are you using? |
| Comment by Zdenek Skodik [ 05/May/09 ] |
|
I tested it on both activation modules and it happened on both simple and transactional also. |
| Comment by Jan Haderka [ 15/May/09 ] |
|
Done on trunk as of r25100, on 3.6 branch as of r25106 and on 4.0 branch as of r25104. |
| Comment by Philipp Bärfuss [ 08/Jun/09 ] |
|
This patch activates all content in reverse order and will always fail if the parent (which will be activated after the children) does not exist. |
| Comment by Jan Haderka [ 12/Jun/09 ] |
|
Fixed as part of the solution for |