On this meta forum and our Discourse hosted forum we are getting a runtime error when directing to the sites through URLs causing a blank screen with only basic background styling. [Screenshot 2024-10-29 at 11.26.53] Unchecked runtime.lastError: The page keeping the extension port is moved into back/forward cache, so the message channel is closed. It points to this commit: [image] Commits · discourse/discourse A platform for community discussion. Free, open, simple. - Commits · discourse/discourse

Looks like it’s a browser extension in Chrome causing the issue. Specifically Jam. You can consider this closed.

[image] Phil Snow: when directing to the sites through URLs Can you expand on what you mean by this? How are you directing people to the site? Via a link? Typing into browser address bar? What URL are you directing people to?

There must be something specific/unusual about your links. If all links to Discourse forums were broken, we would be getting a lot more complaints. Can you share more about how the links are implemented? Are they just simple <a href=? Or is there some JS involved? Can you share a page which demonstrates the problem? Which browsers does this happen in?

Runtime error when navigating to discourse

Product Support

Phil_Snow (Phil Snow) October 29, 2024, 1:31pm 3

Through links yes. I have to refresh the browser to get the content.

Topic		Replies	Views
Error: Something went wrong - "Error while processing route: discovery.categories" Product Support	16	1750	October 5, 2021
Posting a link to the site root doesn't open Bug	4	995	July 4, 2017
Blank Screen for Topic on Mobile Web: TypeError in Admin Console Product Support	9	879	April 25, 2020
[PAID] Need someone to fix bugs and errors on my Discourse forum Marketplace	2	533	February 2, 2024
Discourse returns a 403 when attempting to load the main site Product Support	3	380	June 20, 2023

Runtime error when navigating to discourse

Related topics