The XML content could not be parsed error on most Confluence wiki pages after upgrade to 4.x from 3.x

I upgraded confluence from latest 3.x (3.5.17) to latest 4.x and all the wiki pages are broken:

  • ~90% of them present errors like The XML content could not be parsed ...
  • ~10% of them are some kind of plain text, looking like wiki-syntax presented as HTML (not parsed)

6 answers

Hi All,

https://confluence.atlassian.com/display/DOC/Migration+from+Wiki+Markup+to+XHTML-Based+Storage+Format

1) Storage format got to be change to xhtml.

2) you need to upgrade your macros to xhtml.

https://developer.atlassian.com/display/CONFDEV/Upgrading+and+Migrating+an+Existing+Confluence+Macro+to+4.0

3) What kind of implementation you have done for pages based on it it will give you xml or ac tags related errors.

xhtml combines xml with cDATA and html.

you need to update your plugins and then upgrade data.

thank's.

tousif shaikh.

Im having the same problem. Upgraded 3.5.16 to 4.3.2.

Same issue here, though much lower percentage of each. Any potential fixes identified yet?
I had this issue as well. With help from Atlassian support we identified my problem as pages having a null value in the content type, so they weren't migrated to XHTML from wiki markup. After updating the values to 0 (wiki) and forcing a migration again, all seemed good. I have SQL statements for the checks and updates, just not handy at the moment. Will post ASAP to see if that assists with these issues as well.

Please do post it, it may be the same problem.

it seems to be you need to update the code for macro 4.2.u can post the details for customized macro or u can share specific macro class implementation i with storage format for page it will help to identify rendering system.

if u need more assitance u can send email to me tousifishaikh@gmail.com.

NB: this worked for my issue, no guarantees that it will for anyone else, or won't break anything ( though it SHOULD be relatively safe). As ways, recommend doing this on a non-production copy first, or on prod after a complete backup so you can roll back. UPDATE BODYCONTENT SET bodytypeid = 0 WHERE contentid IN ( SELECT c.contentid FROM CONTENT AS c WHERE CONTENTTYPE IN ("PAGE","COMMENT") ) AND bodytypeid IS NULL; Restart confluence. Force wiki to XHTML migration. Good luck.

same problem
when upgrading from 3.5.7 to 4.2.13

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Confluence

Three common content challenges + how to manage them

An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough   cough, all companies). If content calendars, marketing plans, and bu...

66 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you