-
Bug
-
Resolution: Fixed
-
Medium
-
1.3
-
any
When a space, with hierarchical structure, is exported to PDF, the result does not make much sense.
There was a bug about it before, because, previously the PDF Index (on the left hand) was not reflecting what you would see on the website - was not ordered the same way.
Now, I can see, that the index is ordered properly but if you just printout the PDF the sequence of chapters in the content section does not, really, follow the structure of the index.
If the index is:
1. blah
1.1 blah blah
1.2 blah blu dah
2. duh
2.1 duh duh
2.3. duh duh duh
3 yadda
4 kuku
5 puku
5.1 puku tuku
and
{children:all}shows the sequence that way, PDF index will show it properly but the sequence of content pieces in the exported PDF (hence - the sequence in the hard copy when printed out) will not be the same and will be some obscure sequence, that makes no sense.
P.S. There is still no way to indicate sequence of the pages, on the same level, without explicitely giving them weird names that begin with numbers so that Alphabetical sorting works the way we wanted. That, kinda, sucks.
- incorporates
-
CONFSERVER-801 Support different sortings of page children
- Closed
- is duplicated by
-
CONFSERVER-6543 PDF exports in wrong order
- Closed
- is related to
-
CONFSERVER-1031 Page ordering
- Closed