Hi there, one of my users reported a change in the navigation behavior after the upgrade to Discourse 3.5.0 (stable branch). They mention that they always used to read a topic in /unread and then click the Topics button in the sidebar, and it would take them back to “Unread”. Now after the upgrade it takes them back to /latest. I honestly never noticed that “sticky” behavior one way or another. Can anybody confirm if this behavior has been changed and/or if there is any way to get it back? Thanks a lot.
@member-xp-triage I have a feeling this is not an intentional change? I can’t be fully sure the behaviour worked as described before, but it would make sense to me that ti does.
Huh, I honestly don’t know. I don’t remember it working as described in the OP, but it does seem like something that we might have done.
Yep, I also can’t personally confirm or deny if it worked that way before, but the user that reported it is very active on the forum, so he clearly remembers how it used to work.
Welcome to Meta 
I think the behavior of being taken to unread topics or latest by using the sidebar can be configured with the Link to the filtered list option in the navigation menu user preference (https://meta.discourse.org/my/preferences/navigation-menu) and that still seems to work for me.
It may help if the user checks their preferences.
Funny enough, it does not work for me! It was the first thing I checked too.
It applies when clicking on the logo, but not when clicking on the sidebar topics link.
I wonder why it works for me 
I thought maybe it’s because of @new-new-testers but it also worked when I joined the group.
Even more interesting: When I change the navigation menu preference, it doesn’t change what happens when I click the logo. That only changes when I use the “default home page” in the interface preferences.
Thanks for this suggestion! Unfortunately it doesn’t seem to change anything for me. I also attempted enabling an admin setting Default sidebar link to filtered list described as “Make navigation menu links link to filtered list by default” but it doesn’t seem to make any difference.
@sb56637 문제 해결이 되셨나요? 방금 테스트해 보니 Moin님의 제안이 제 환경에서는 잘 작동합니다.
원하시면 default sidebar link to filtered list 설정을 변경하고, 해당 변경 사항을 과거 데이터에도 적용하는 데 동의하시면 모든 멤버의 기본값을 변경할 수 있습니다.
후속 답변 감사합니다. 그렇게 하면 되는 것 같습니다. 팁을 주신 모든 분들께 감사드립니다.
이번에는 다른 방식으로 처리하신 부분이 있을까요? 제가 그 방법을 제안했을 때, 당신(그리고 @chapoi)은 처음에 작동하지 않는다고 하셨는데, 지금은 작동한다고 말씀하고 계십니다. 작동하려면 충족되어야 하는 다른 조건이 있는지 궁금합니다.
그렇게 하려면 브라우저에서 사이트를 새로고침해야 하는 것 같네요. 처음 시도했을 때 새로고침을 하지 않았던 것 같습니다.