XF 2.3 XF 2.2 to 2.3.2 Upgrade Broken

[trigatch4]

I upgraded via web from XF 2.2 to 2.3.2 and the installer verified success. However, when loading my forum now, the template and style are completely broken.

I deactivated all add-ons before upgrading (but not sure I deactivated style and set to default).

It seems my recent backup failed so I'm hoping to fix the problem live rather than restoring from an older backup.

I see error logs related to templates/styles an am wondering if there is a way to wipe these and start from scratch after the fact? The "broken" style of the page occurs whether I'm on the 2.3.2 Default Style or any of the previous styles.

Here's what my page looks like now for reference:

 

[Paul B]

Your site is loading mostly okay for me but there are some layout issues.

Disable all add-ons and create a new style with no parent.

How does it look then?

 

[trigatch4]

Thanks for the idea! I gave it a shot but the layout issues remain (the content/database does seem to be fine).

UPDATE: Appears to display fine for guests but broken for logged in.

 

[trigatch4]

Here is an example of a "Server Error Log" entry in AdminCP:

XF\CssRenderException: Error rendering template public:extra.less: ParseError: Unexpected input in public:extra.less on line 58, column 44 (on or near line 58) src/XF/CssRenderException.php:89

Line 58 is:
58| url('/styles/fa/brands/500px.svg?v=5.15.3'): "\f26e";

I've disabled all add-ons and only have the 1 style active and set to default... any other ideas @Paul B ?

 

[Mr Lucky]

If you have the default style active (the new one you created with no parent) , there cannot be a line 58 in the extra.less template - it should be empty.

 

[trigatch4]

If you have the default style active (the new one you created with no parent) , there cannot be a line 58 in the extra.less template - it should be empty.

EB Default is the new one I created:


100% of add-ons are uninstalled, disabled, or listed in a separate "legacy" section.

I agree that it defies logic but when logged in the page is still broken and when I log out it looks fine. Obviously have cleared cache and history and all that jazz. And those server errors (and other similar ones) persist.

 

[Old Nick]

What is the content of the extra.less template?

Nothing custom in ACP >> Appearance >> Template modifications?

 

[trigatch4]

What is the content of the extra.less template?

Nothing custom in ACP >> Appearance >> Template modifications?

extra.less is empty:


No template modifications:

 

[Mr Lucky]

EB Default is the new one I created:

I would delete the other ones so no room for doubt (export before deleting so there is a backup)

 

[Mr Lucky]

extra.less is empty:

Is there an admin or mod with access to the old ones? why I said delete them just to cover all bases.

 

[trigatch4]

The plot thickens:
I created a test user, logged in, and it works fine.
So the issue is only for Admins/Mods?

I'm wondering if existing users picked a default theme, which has since been deleted, it may continue trying to loading that deleted theme? Is it possible to reset all user preferences to default theme?

 

[Russ]

Disabling styles doesn't force admins to the active style. If you have an admin browsing the site, they could still be viewing the old style that is potentially outdated and therefore throwing errors.

Non-admins will not be able to browse disabled styles, they would be forced to the new active style.

 

[trigatch4]

Disabling styles doesn't force admins to the active style. If you have an admin browsing the site, they could still be viewing the old style that is potentially outdated and therefore throwing errors.

Is there a way to force/reset/forward these?
Or generate a link to the new default style to override?

 

[Paul B]

The style can be manually set for the user in the ACP.

Check all admin accounts and update them.

Or just tell your staff to change the style.

 

[Mr Lucky]

So the issue is only for Admins/Mods?

This was my point. Admins can use any of the styles so the old dodgy ones could cause errors if an admin is using one of those.

Hence export them for safety then delete all of them for testing. I'll bet that's why you got the extra.less line 58 error.

 

[trigatch4]

export them for safety then delete all of them

Does XML vs Archive matter or either will work fine?

 

[Mr Lucky]

Does XML vs Archive matter or either will work fine?

They both work