Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Sorin Sbarnea (Citrix)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 31, 2012

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

3 votes
tousifs
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 30, 2012

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.

1 vote
Ben Marshall December 30, 2012
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.
1 vote
Ben Marshall December 29, 2012
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.
Sorin Sbarnea (Citrix)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 16, 2013

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

tousifs
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 17, 2013

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.

1 vote
Ben Marshall November 3, 2012
Same issue here, though much lower percentage of each. Any potential fixes identified yet?
1 vote
Julio Mugabe November 1, 2012

Im having the same problem. Upgraded 3.5.16 to 4.3.2.

0 votes
Himanshu Mundra December 28, 2012

same problem
when upgrading from 3.5.7 to 4.2.13

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events