-
Bug
-
Resolution: Fixed
-
Neutral
-
1.1.5, 1.2.4
-
-
Empty show more show less
-
Yes
-
Yes
-
Maintenance 55, Maintenance 56, Maintenance 57
-
13
Steps to reproduce (taken from PUBLISHING-62)
1. Create 4 nodes (names 1-4 and in that order) on the same level, publish them all.
2. Move node 1 between 3 and 4.
3. Move node 2 between 3 and 1.
4. Publish node 2.
5. Publish node 1.
6. See the difference between author and public
Note: the order can be fixed by publishing node 3 as well.
Most likely there's insufficient ordering info we send during the activation process (only the siblings are included and not the whole structure).
Old description which was probably copied from wrong ticket:
Steps to reproduce:
- create page tree
- publish everything
- check node order on public instance
- modify page3, page4, page5 so they have orange status
- publish page2
- observe wrong order of nodes on public instance
- clones
-
-
- Closed
-
- duplicates
-
-
- Closed
-
- is caused by
-
-
- Closed
-
- is causing
-
-
- Closed
-
- is related to
-
-
- Closed
-
- to be documented by
-
PUBLISHING-117 DOC: Document new default ordering of nodes on public instance
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
