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
Page Not Found page doesn't respect default site locale #7909
Comments
Can you describe the setup here? Is this a site where you have a custom language set for concrete5? Is this a site with Japanese set as the language but no other multilingual locales? Just trying to understand what's happening here. |
Tested on clean installed concrete5 with the guest account.
/page_not_found : lang=ja
/page_not_found : lang=ja
/page_not_found : lang=en
/page_not_found : lang=en |
This issue is reported on Japanese forum |
A new and same report from Japanese forum |
I can confirm this issue (version 8.5.4, German language as default). While a customized login page is always automatically translated to the default language of the site, the Page Not Found page always appears in English, no matter which way of customization you go (custom single page or page_not_found.php within the theme). In this case the T-Strings will not be translated. |
I have a question for you. You moved |
@mlocati Thanks. So, we shouldn't call |
Yes, I'm pretty sure that's the reason why I moved |
OK, I'll check. Thanks! |
See discussion about this change: concretecms#7909
See discussion about this change: concretecms#7909 (cherry picked from commit 9eff103)
See discussion about this change: concretecms/concretecms#7909 (cherry picked from commit 9eff103)
See discussion about this change: concretecms/concretecms#7909 (cherry picked from commit 9eff103)
See discussion about this change: concretecms/concretecms#7909
See discussion about this change: concretecms/concretecms#7909
If you access to YOUR_SITE/page_not_found, the active locale is the same as the default site.
However, if you access to YOUR_SITE/foo (or any other missing URLs), the active locale is always en_US.
Please see the attached image. Tested on 8.5.2a1.
This is a very similar issue with #6500, but it happens on non-multilingual site.
The text was updated successfully, but these errors were encountered: