nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Some pages render blank after upgrade

Snorre Selmer

After upgrading our Confluence from 4.3.1 to 6.7.2, some pages have stopped rendering.

If you go to the page, it shows as blank, but if you use the View Source option in Confluence, the content displays fine.

If you edit the page, the content is there, but saving the page doesn't do anything. Adding a few random characters to alter the content and then saving doesn't help either.

If I copy the content from the edit-page and paste it into a new page, it still renders as a blank page. If I copy the content from the "View Source"-window and paste it into a new page, it renders correctly.

Anyone here have an idea what's happening? Any way to fix this for all the affected pages in one go?

Accepted answers

Nic Brough -Adaptavist-

Pick one of the broken pages and have another look at the source. Do you have any macros that could be doing bad things? I've managed to break upgrades with "unmigrated wiki markup" and my own user macros more than once (especially my dodgy user macros that don't upgrade nicely)

All comments

Nic Brough -Adaptavist-

Snorre Selmer

As far as I can tell, there are no user macros in use on these pages. They only use bullet-point lists and tables from the Confluence GUI editor.

Nic Brough -Adaptavist-

Ok. I think we need to have a good look at the difference between these blank pages and one that works ok.

When they're coming out blank, is it everything that is blank, or just the content area? Is there any real content in the raw html of the page? (Use browser development tools to see the page source)

Snorre Selmer

I'll do a diff on the content when I get back to work next week (busted my back today, out for a week).

Snorre Selmer

Sorry for the lengthy delay on replying, been out sick for two weeks.

Inspecting the HTML in Chrome yields no page-content, so what is rendered is correct according to the HTML.

But when I "View Source" or "View Storage Format", the pop-up window displays the expected text correctly. The strange thing is that this seems to be a problem this user has with more pages on his personal space, but so far it's only this one user.

Here's a screen-capture with the "View Source" window content partially visible on the right:Could it be a problem with Active Object indexing? User privileges?