XF 2.3 "Oops! We ran into some problems" when switching style variation

Russ

Russ

Well-known member
I've only seen this on a single client's site, but I'm not sure what to make of it. We upgraded their style to 2.3 with variations enabled. They disabled the old 2.2 version, switched everyone to the new 2.3 version. Various users when switching to the dark mode get the oops error, with this in console:

1730482413625.webp

The strange part is when the user switches to the default XenForo style, then back, they're able to use the variations then.
 
Sort by date Sort by votes
Russ said:
I've only seen this on a single client's site, but I'm not sure what to make of it. We upgraded their style to 2.3 with variations enabled. They disabled the old 2.2 version, switched everyone to the new 2.3 version. Various users when switching to the dark mode get the oops error, with this in console:

View attachment 313316

The strange part is when the user switches to the default XenForo style, then back, they're able to use the variations then.
Click to expand...
You could check if a firewall or proxy is blocking access to the URL or if there are any permissions set on the server that might be causing this restriction since a 403 error is returned.
 
Upvote 0 Downvote
It's weird.

We updated our style right after updating to 2.3. @Russ's 2.3 style has a light dark switch top right, as well as the more regular bottom left position. No matter which option they choose - lots of members get that Oops. This is not all users, it works as normal for most.

This fixes it, but why?

If I activate the default xf style, get the affected user to log into it, and while using it, toggle dark and light mode a couple of times. When they log back into the new style, it works; the light/dark changes, no oops.

What is going on? Any idea?
 
Upvote 0 Downvote
Paul B said:
A 403 error is a web server error, happening outside XF.

It will most likely be due to some sort of security mechanism.
Click to expand...

A server error that doesn't error on the Xf default style. But it does error on a third-party style, but then doesn't if you log in and out of the default style first.

Anyone any Idea what security mechanism that could be? Cheers.
 
Upvote 0 Downvote
JamesBrown said:
A server error that doesn't error on the Xf default style. But it does error on a third-party style, but then doesn't if you log in and out of the default style first.

Anyone any Idea what security mechanism that could be? Cheers.
Click to expand...
What happens if you try to load that URL only? Do you see the Cloudflare branding page?
Cloudflare usually serves 403 responses if the request violated a default WAF rule enabled
 
Upvote 0 Downvote
Are there any user or group permissions for being able to switch light and dark?

Edit, grasping at straws there, if it was anything to do with permissions, they wouldn't be able to change when using the default style.
 
Upvote 0 Downvote
OK I just had another user report it, and I logged in as him and got the same error. Checking in Console. The first error is different. from above, Uncaught Reference error.

1730744360971.webp

Chat GPT tells me

This indicates that your code is trying to use $ (typically the shorthand for jQuery) but cannot find the jQuery library loaded in the environment. This usually happens because jQuery is either not included or not loaded before your script runs.

So why might some users have jquery loaded OK and others don't, and why would it be loaded for them after they visit the default theme?
 
Upvote 0 Downvote
OK, the Uncaught Reference thing was nothing to do with it.

Russ spotted when digging deeper in to the error that, somehow, the affected users were still browsing in the old deactivated style. How? No idea. But once we deleted the old style the issue was fixed.
 
Upvote 2 Downvote
I'm seeing the same issue after upgrading to XF 2.3.

After the upgrade we switched to the XF default style and disabled the previous custom styles. It does seem like the members are somehow stuck in the old style and picking ANY style variation throws the error message.

I will delete the old inactive styles and report back.
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

C
  • Question Question
Oops! We ran into some problems...
Replies
12
Views
131
colenot
C
Num7
  • Solved
XF 2.3 Optimizing attachments leads to Oops! We ran into some problems
Replies
9
Views
168
Num7
Num7
B
  • Question Question
XF 2.2 Getting issue Oops! We ran into some problems.
Replies
3
Views
76
pattycake2
P
joshg
  • Question Question
XF 2.3 Another "Oops! We ran into some problems" report... can anyone help diagnose?
Replies
3
Views
72
Paul B
P
IntelliJ
  • Question Question
XF 2.3 Oops! We ran into some problems. Provided file is not a valid image.
Replies
15
Views
215
CtrlV
CtrlV
Back
Top Bottom