I’m a week or so into an xWiki build. Ubuntu Server 24, xWiki 17.3, Docker installs for xWiki and Postgre 16.
The server is not on the internet, local intranet only.
I’ve just tested the PDF Export, and it puts together a nice header/footer/ table of contents. However, the main body is all one big paragraph rather than all the various heading levels and bullet points
I’ve tried looking into the PDF Export template, and I’ve poked around on changing some of the PDF Export settings, but nothing seems to change it reformatting the page to a single paragraph.
What was odd is that the Chrome Print-to-PDF looked fine, other than nuisance HTML garbage that Chrome throws in there…
I ended up testing on the Edge browser, and it exported just fine using xWiki PDF Export.
I tried chrome’s Incogneto mode, and it worked fine.
I deleted Adobe Acrobat Chrome Extention and it still didn’t export properly
I changed my ubuntu server from a Non-Internet IP address to an Internet IP address and ran updates on Ubuntu, just to see if something was internet dependant, but non of that fixed the PDF Export
I deleted the cached website data/cookies for my wiki’s address, and it still did not export properly.
Finally, I dumped 4 weeks of all Chrome cache data, and it properly exported the PDF at last.
This suggests that the exported content is rendered as plain text instead of HTML. I’ve seen this in the past (recently), because the output syntax available in the rendering context was wrong (plain text instead of HTML), but this has been fixed by XWIKI-22738: Target syntax is not set on the transformation context w… · xwiki/xwiki-platform@37ff31e · GitHub . Now, the fix is indeed in JavaScript code which might have been cached by your browser.
Did I understand correctly that the problem has been fixed by clearing the browser cache?