One admin user is having a strange error after updating Discourse. The error happens when the user clicks on the back button or the site logo. It appears to trigger JavaScript to go to the root/home of the site, but instead the following errors trigger: Visually the error appears as: [image] In the JS console: [console] I’ve also found that this happens with any nav bar clicks such as trying to go to /admin as well. Any thoughts on tracing this out further? Not seeing error in production.log or otherwise, so this has been a real head scratcher since it seems bound to JS.

Thank you for the suggestion. Strangely it still had the error even with enabling all 3 options in Safe Mode: [image]

Still been hitting dead ends in further debugging so far. I have to suspect that “Safe Mode” is not fully disabling JS due to this… Is there another step that can further eliminate JS from functionality for testing?

Is your site publicly accessible? If so, any chance you can share a link? (via a PM is fine if you prefer not to post it publicly)

Thanks for the link @mreach. I’m not seeing any obvious issues from here. You mentioned that this is only affecting one user on the site. Do you know if it’s a problem is limited to a single browser/device? Or does it happen to this user even when they log in using a different device? If it’s just one browser/device, then it could suggest a browser plugin (e.g. an ad blocker) intefering with Discourse’s code. If it’s affecting them in every browser, then that’s more tricky. Do you have any third-party plugins installed on your forum? It would also be interesting to know what the user has configured for their ‘default home page’ (found in their Discourse ‘interface’ preferences)

Thanks - yes, I’ve had mostly the same thoughts. I had them try disabling all extensions, clearing all browser data. I just had ANOTHER user report the same problem… And they’re both on Chrome. I asked them to try Firefox and Brave and they each said it worked for them there, but nothing they can do seems to make Chrome work “properly” for them again. The asked them again about Incognito results and they both reported that Incognito DOES work. Again, all of this was after the last Discourse update, so it seems as though something must not be clearing in JS somehow… Which I truly don’t understand how that could be the case. I’ve asked them what they have configured as their homepage… Will let you know. That’s a very good idea that had not crossed my mind…

Alright, interesting but not conclusive: The user that has the problem has “Categories” set as their home: [image] If they change it to another, such as “Latest” instead, they CAN load the home page by clicking the site logo AND using the “back” arrow in the browser. If they change BACK to “Categories” instead of “Latest” the problem / error returns. :weary_face: So this user is also an admin and if/when they click on the hamburger icon in the upper right and click “Admin”, they also get the error as reported above - even when the home page is changed to “Latest” instead of “Categories”. Of course that’s new info, but not entirely helpful given my perspective. Hm.

[image] mreach: In the JS console: [console] Any chance you can get some more detail on these errors? They should all be expandable, and should hopefully include a little more detail about the error.

They got me the following console output: https://pastebin.com/LuDHesyQ

Thanks again for the suggestions up to now - happen to have any observations from that @david?

Error: Something went wrong - "Error while processing route: discovery.categories"

Product Support

pfaffman (Jay Pfaffman) September 30, 2021, 9:19pm 2

Did you try How to use Discourse Safe Mode

Topic		Replies	Views
Lost all categories and admin access Product Support	10	512	June 21, 2024
Category link failed after updating today Product Support	7	1175	June 22, 2021
Clicking home from admin panel results in error Bug	5	663	November 20, 2023
Site broken after update Self-hosting	3	1162	April 12, 2021
Discourse broken after moving servers Self-hosting	15	926	May 10, 2024

Error: Something went wrong - "Error while processing route: discovery.categories"

Related topics