-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Study sharing URL: wrongly redirects to newly created chapter #14959
Comments
@kraktus I'm not sure it's an off by one issue. If you create a third chapter, it will land on the third one. If you create 60 chapters, it will land on the 60th chapter. I think it is the last created chapter. I need to check what happens when the last chapter is reordered to the first position in the study. Also, I noticed that after some time without modifying the study, the issue corrects itself and the study url lands on the first chapter. |
If you would like to link to a specific chapter in is study, you should use the "Current chapter URL". Seems like that should solve this issue? Also just noting that there is a setting to keep everyone synced to the same position in a study, which is on by default. Just something to be aware of, guessing you want that off. |
@brollin yes, having the link to the first chapter does "fix" this issue. Although removing or reordering the first chapter would bring it back, it's a minor issue as we don't do that often. The current behavior with the chapter in the url is appreciated. I also tried with sync disabled and I still have the bug when sharing the url of the study. |
Exact URL of where the bug happened
https://lichess.org/study
Steps to reproduce the bug
What did you expect to happen?
I expected the study to open chapter 1.
What happened instead?
It opened chapter 2. If we make more chapters, it will land on the last one when opening the study URL.
Operating system
Windows 11
Browser and version (or alternate access method)
Chrome 122
Additional information
No response
The text was updated successfully, but these errors were encountered: