-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
5.4.3, 5.5.4
When exporting a page that contains a Tasklist into a Word document, the following warnings will show in logs (2 for every task):
2014-05-15 13:34:53,125 WARN [http-5543-6] [atlassian.confluence.servlet.ExportWordPageServer] extractImagesFromPage Skipping datasource creation for non-relative url: http://localhost:5543null -- url: /exportword | userName: admin | referer: http://localhost:5543/display/TEST/testpage 2014-05-15 13:34:53,125 WARN [http-5543-6] [atlassian.confluence.servlet.ExportWordPageServer] extractImagesFromPage Skipping datasource creation for non-relative url: http://localhost:5543null -- url: /exportword | userName: admin | referer: http://localhost:5543/display/TEST/testpage
The export process seems to be referencing null images, perhaps the checkbox and expand/collapse button. These invalid images can also be found when examining the storage format of the resulting Word document in a text editor:
... <tr> <td width="5%"> <a href="http://localhost:5543/display/TEST/testpage" border="0"><img border="0" src="http://localhost:5543null"></a> </td> <td width="5%"> <img border="0" src="http://localhost:5543null"> </td> <td colspan="2" width="85%"> <font><b>TESTING123</b></font> </td> <td width="5%" align="right"></td> </tr> ...
Because this does not impede the Export-to-Word functionality in Confluence, and the file is generated as expected, I've raised this bug as Trivial. Ideally we'd suppress or address these WARN messages in the future to clean up the logs.
[CONFSERVER-33666] Warnings thrown in logs when exporting page containing Tasklist to Word document
Same problem in Confluence Server 6.15.1. I have problem with issue types icons when page is exported to Word.
I'd like to add that this issue is also occurring when exporting a page to Word that contains the HTML macro. This occurs on 6.9.1.
Hi msymons,
Thanks for taking the time to comment on this issue and share your thoughts. I also want to apologise for the inconvenience that this bug is continuing to create for you and your team.
To provide a bit more background about why this issue has been closed, having a leaner backlog of issues allows us to better identify areas we can focus on that will have the biggest overall impact for our customers.
I should stress that closing an issue doesn't mean that it's gone and forgotten, but it's intended to be an honest indication that we aren't prioritising a fix in the foreseeable future. Watching and commenting on a ticket will help us gauge demand - JQL queries easily allow us to find and reopen these issues when circumstances change.
Kind regards,
Edith Tom
If demand for this picks up, we will reopen the issue.
Just how would Atlassian know if demand is picking up when you have closed the issue and thus disabled the ability to vote? If the issue were open I would be casting a vote today.
- Hundreds of WARN events
- Seen with Confluence v5.7.4 & also with v5.8.6
- STP v3.5.40 log scan links to
CONF-25647 - As per comment of Michael Jositz (albeit implicit rather than explicit), issue is not just seen with Tasklist, it is also seen with JIRA Issue Macro export to Word
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on bugs with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If demand for this picks up, we will reopen the issue.
And 8.x...