Foutpagina verschijnt herhaaldelijk na het proberen te openen van een privé-pagina

AI-generated summary

Users reported a bug where accessing a private page (e.g., #lounge as a new member) triggers an “oops” error page that persists even when navigating back to the homepage or other topics. WooleyWool first noted the issue occurs across all sites and can only be resolved by refreshing or opening a new tab. tshenry confirmed the bug as an anonymous user, observing broken routing in certain menu links, with a console error appearing upon clicking restricted categories. codinghorror requested reproducibility and later suggested it may relate to non-Ember pages. riking identified the root cause: Ember’s intolerance for rejected promises in Route.model, compounded by an incorrectly overridden error action in routes/application.js. Two GitHub PRs (#11424 and #11425) were submitted to fix the issue, with the latter addressing the core problem by restoring the correct error action implementation. The bug was assigned for a post-release fix as requested by codinghorror.

Hi, so I was just browsing through the forums and one of the posts had a link to the lounge. I tapped it and of course, it’ll take me to the oops page. What’s odd is when I try to the home page by pressing the logo, the oops page appears again. Even going to another post, it does the same thing. Unfortunately, I can’t post a video about it but it’s easy to replicate. For instance, try going to #lounge but you’re a new member.

Note: This happens on every site, not just this one. I can confirm that I can replicate this repeatedly and the only real way of fixing this is to open a new tab and go to the forum.

I’d just like to note that this is my first time trying to post a bug, I’m sorry if there are any inconsistencies in my post but I noticed this bug and would like to get this addressed.

5 likes

Can we repro this @tshenry?

4 likes

Ok, I’m glad I am not the only one having this issue because I was a little skeptical at first.

2 likes

I can, indeed, as an anon user. It looks like the routing breaks down in certain places and you get left in a weird state:

Noting that I can successfully click through to the Popular/Recent topics, but as you can see some category-related routes in the hamburger menu don’t seem to function correctly. Interestingly, I don’t see anything in the console or error logs. I was wrong, there is an initial error when clicking on the category link, but I think that’s to be expected:

Screen Shot 2020-11-18 at 5.18.20 PM

7 likes

The only way to fixing this currently is refreshing the page or just opening a new tab. It occurs even when looking at another topic and clicking the home icon.

3 likes

Usually this has to do with hitting a non-Ember page, but that’s typically difficult to do.

1 like

@eviltrout can you assign this for a post-release fix next week?

3 likes

Got a fix here! Ember really doesn’t like it when you reject from Route.model, it seems.

https://github.com/discourse/discourse/pull/11424

3 likes

Update: This is actually caused by overriding the error action, which has the correct implementation at the top level routes/application.js.

Follow-up commit to fix this properly:

https://github.com/discourse/discourse/pull/11425/files

4 likes

This topic was automatically closed after 2 days. New replies are no longer allowed.