Error page appears repeatedly after you try accessing a private page

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:

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.