Deprecation warnings are causing an exception

AI-generated summary

A Discourse forum is experiencing issues due to deprecation warnings causing an exception. hithere initially reported the problem, and hithere later identified the issue as being caused by an undefined options variable in the code. sam confirmed that a fix would be issued shortly. In the meantime, david provided a workaround by suggesting the use of Safe Mode, which temporarily disables themes/plugins triggering deprecation notices. A revert commit (this commit) was made to resolve the issue, which was confirmed to be effective by vincentp.

Our forum, which is hosted by Discourse, is suddenly gone - it doesn’t show any posts anymore and there’s a big JS error in the console.

Any idea what might be the issue? I was thinking it could be an issue with the theme, but I’ve checked and it’s fine as far as I can see (We still have access to the admin panel)

1 Like

We are seeing the same issue since updating to beta 12

1 Like

It seems to be due to this part of the code:

options is undefined so an exception is thrown and that crashes the whole website.

2 Likes

We have a repro of the issue and will be issuing a fix shortly, thanks heaps for bringing it to our attention

6 Likes

We reverted the change via this commit. Thanks @hithere for identifying the precise issue!

As an immediate workaround, Safe Mode should allow you to access the affected forums. That will temporarily disable any themes/plugins which are triggering the deprecation notices.

We’ll get this fix rolled out to our hosting ASAP - very likely within the next hour.

7 Likes

Confirming the revert fixes things. Thanks for the quick response.

1 Like