-
Bug
-
Resolution: Fixed
-
Medium
-
6.0.6, 6.1.4, 6.2.1, 6.2.3, 6.2.4, 6.3.1, 6.4.0, 6.5.1, 6.7.1, 6.9.3
-
17
-
Severity 3 - Minor
-
9
-
Summary
When importing a word document and splitting by headers, the page tree that gets created is alphabetized. What we are expecting to happen is that the page tree would be in the same order in which the headers appear in the document.
To reproduce, simply import a word document which can be split by multiple headers that do not appear in alphabetical order within the document. Once the document is imported, notice that the page tree is alphabetical in order as opposed to their order within the document.
I have attached an example Word document to test with.
Steps to Reproduce
- Import Brian.docx
to Confluence and use Split by heading functionality. - Observe pages tree generated in sidebar.
Expected Results
- Page tree will be ordered properly (as in document).
Actual Results
- Pages are sorted alphabetically.
Notes
The issue is not reproducible with 5.10.8.
It looks like problem is introduced in Confluence version 6.0.6 and plugin OfficeConnector-5.0.3.jar. The issue is not present in plugin 5.0.2 and Confluence 6.0.5.
Workaround
There are 2 workaround at this point:
- Manually sort and reorder pages.
- Downgrade the plugin:
- Stop confluence
- Find the folder <confluence-install>/confluence/WEB-INF/atlassian-bundled-plugins/ on production
- Backup and move OfficeConnector-5.x.x.jar from this folder
- Download Confluence 5.10.8 zip.
- Extract from the same folder OfficeConnector-5.0.2.jar. and copy it to the same folder on production.
- Remove the following folders:
- <confluence-home>/bundled-plugins
- <confluence-home>/plugins-cache
- <confluence-home>/plugins-osgi-cache
- <confluence-home>/plugins-temp
- <confluence-home>/bundled-plugins_language
- Start Confluence
Note: The work around (2) has been confirmed to work up up to Confluence 6.5.2 but does not work for Confluence 6.7.1 (Confluence 6.7.1 will crash when importing Word Documents when using the older OfficeConnector-5.0.2.jar)
- blocks
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
CONFSERVER-27121 Importing Word docs to Confluence results in topics that are ordered alphabetically
- Closed
-
![[JIRA Server (Bulldog)]](/images/icons/generic_link_16.png "[JIRA Server (Bulldog)]")
PSR-265
You do not have permission to view this issue
[CONFSERVER-52595] When importing a word document, header order is not respected
A fix for this issue is available to Server and Data Center customers in Confluence 6.13.7
Upgrade now or check out the Release Notes to see what other issues are resolved.
If you're running the Confluence 6.13 Enterprise release, a fix for this issue is now available in Confluence 6.13.7, which you can find in the Download Archives.
A fix for this issue is available to Server and Data Center customers in Confluence 6.10.3
Upgrade now or check out the Release Notes to see what other issues are resolved.
If you're running the Confluence 6.6 Enterprise release, a fix for this issue is now available in Confluence 6.6.14, which you can find in the Download Archives.
A fix for this issue is available to Server and Data Center customers in Confluence 6.6.14
Upgrade now or check out the Release Notes to see what other issues are resolved.
If you're running the Confluence 6.6 Enterprise release, a fix for this issue is now available in Confluence 6.6.14, which you can find in the Download Archives.
A fix for this issue is available to Server and Data Center customers in Confluence 6.15.2.
Upgrade now or check out the Confluence 6.15 Release Notes to see what other issues are resolved.
poacher fish
added a comment - Interesting to see the comment that this issue is at certain header levels. I have been creating pages manually by cutting and pasting from the old system and into Confluence. I have noticed that sometimes the pages hold the order I have created them in and sometimes they load alphabetically - sounds like this might depend on the level I am at.
Just mentioning as this might not be restricted to Word imports.
We are running 6.7.2
poacher fish
added a comment - Interesting to see the comment that this issue is at certain header levels. I have been creating pages manually by cutting and pasting from the old system and into Confluence. I have noticed that sometimes the pages hold the order I have created them in and sometimes they load alphabetically - sounds like this might depend on the level I am at.
Just mentioning as this might not be restricted to Word imports.
We are running 6.7.2 Hi blivingston,
We are not able to reproduce the bug with level 3 headings on the version of Confluence with the fix (6.15.1). I have attached the files we are using for testing.
Could you please provide some more details about the file you are using? It would be great if you could supply an example file that is failing on your instance. Otherwise, please provide the version of Word used to create the file and some general information about the structure.
Test Lvl3 Headers.docx
Test Nested Headers.docx
I first reported this on Confluence 4 in 2011! The original Jira issue was OFFCONN-53.
User Ioana on writethedocs.slack.com does not encounter this bug on a 5.8.6 instance there. So apparently it was fixed at some point and then reverted.
Deleted Account (Inactive)
added a comment - Hello Oliver,
I created the case and first reported the issue. Was so happy to see that there was FINALLY a fix but -The bug isn't fixed. Header level 3 is still not being respected.
So the issue wasn't present at header level 1 but was present at level 2 and level 3. You guys fixed the bug at level 2 but level 3 is still not respecting the header order.
I have to say that I am disappointed. Nearly 2 years (reported in June 2017) to get a fix for an issue effecting many customers and this wasn't tested properly, then closed.
Please do not continue to keep us waiting for a proper fix. I'm sure I am not alone.
Deleted Account (Inactive)
added a comment - Hello Oliver,
I created the case and first reported the issue. Was so happy to see that there was FINALLY a fix but -The bug isn't fixed. Header level 3 is still not being respected.
So the issue wasn't present at header level 1 but was present at level 2 and level 3. You guys fixed the bug at level 2 but level 3 is still not respecting the header order.
I have to say that I am disappointed. Nearly 2 years (reported in June 2017) to get a fix for an issue effecting many customers and this wasn't tested properly, then closed.
Please do not continue to keep us waiting for a proper fix. I'm sure I am not alone. This bug has been fixed on 6.15.1. I've updated the issue to reflect this.
A fix for this issue is available to Server and Data Center customers in Confluence 6.13.8
Upgrade now or check out the Release Notes to see what other issues are resolved.
If you're running the Confluence 6.13 Enterprise release, a fix for this issue is now available in Confluence 6.13.8, which you can find in the Download Archives.