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; } } }

Default Theme not working properly after migration form 3.4.9 to 4.1.9

David

Hello,

We just performed a Confluence migration on our test environment from v3.4.9 to v4.1.9 and all went well. All plugins were updated and pages display fine. However in page Edit mode the layout is all messed up: imagine a 4 cell table where the header is in the top left cell and the content in the bottom right, the other two cells are empty.

We did not customize the default theme to avoid any issues between migration in order to upgrade frequently.

We need to migrate to v4.1.9 and not later as some used plugins are not yet compatible with later versions of Confluence.

Accepted answers

Nawaz Quadri

Don't know the exact reason for that, but I too faced the same issue while upgrading from confluence 3.5 to 4.2.1. In our case we were having a customized global Layout. We reverted back the Global layout to default. That helped us to resolve the issue. Go to Admin>Look and Feel>Layouts and see if you have a custom global layout. Try to revert back to default layout and then cutomize the Global layout according to your need.

Hope this helps

All comments

Nawaz Quadri

Hope this helps

Matthew J. Horn

You say you didn't customize the default theme, but does that mean you didn't touch the layouts only? Or did you also avoid touching the CSS files that are used by Confluence? Or load any additional CSS files?

K Kelly

Is there a need for upgrading at this time? If not, you may want to delay your upgrade until the new RTE that replaces wiki markup is more robust and stabilized. If you use PDF export, there are issues as well.

Food for thought...

David

Hello,

There was a customization referring to editor-capatcha.vm & editor-setting.vm but these files did not exist in Confluence 4.1.9 installation directory. To fix this, we executed the following query against the database:
{code}select * from decorator;{code}
Save a copy of the customization just in case. And then, delete it:
{code}delete from decorator; {code}
After that, restart Confluence.

This fixed the issue.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence