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
Changing the language redirects to index.php #5625
Comments
For ther deeplink maybe some addional information are needed like the post stuff or the anker information, |
We do maintain a note of the user's current URL during their session1 so that we can redirect the user back to it after certain actions (e.g. login). Redirecting after changing languages should be possible if we extend that system to include the action of changing languages. 1 A note for any privacy conscious readers: This is an ephemeral record only of the current URL you are visiting at the moment, not a record of where you have been. Whenever you go to a new page, the previous URL is forgotten, and the record is deleted entirely after you leave the site. |
Try to redirect the user to the same page after changing of language. Fixes SimpleMachines#5625 Signed-off-by: Oscar Rydhé oscar.rydhe@gmail.com
Redirect to old url after language change. Fixes SimpleMachines#5625 Signed-off-by: Oscar Rydhé oscar.rydhe@gmail.com
Redirect to old url after language change. Fixes SimpleMachines#5625 Signed-off-by: Oscar Rydhé oscar.rydhe@gmail.com
Redirect to old url after language change. Fixes #5625 Signed-off-by: Oscar Rydhé oscar.rydhe@gmail.com Co-authored-by: Oscar Rydhé <oscar.rydhe@sony.com>
Description
Changing the language from the top-right dropdown menu redirects to
index.php?language=foo
. Is there a technical reason for this? Could it be changed to redirect to<current deeplink>?language=foo
?Currently, I either have to re-click my way back into the maze that is, for example, the admin center, or use my browsers back button and reload to see the language change.
Steps to reproduce
Environment (complete as necessary)
The text was updated successfully, but these errors were encountered: