Assuming a multi-language site with DE as default language and EN as secondary.
You should land on /ueber-uns.html in German.
You get redirected to /en/ueber-uns.html instead, which results in a 404.
Joomla! 3.4.1 with everything up to date.
Another side effect is that after you switched to a language different to the default language once, following any links (f.e. on Google) to pages in the default language will result in a 404.
Build | 3.4.1 | ⇒ | staging |
Labels |
Added:
?
|
BTW, you should test on staging, not 3.4.1
I can confirm this bug - having the exact same problem.
Hello,
we have the exact same issue. In this case, we use English as default and we have Portuguese (PT) as the alternative.
For example: if the default language for the user is Portuguese, the website will be in that language and, if the user clicks on an external link that goes to the default article language: www.ourwebsite.com/somearticle it tries to open with www.ourwebsite.com/pt/somearticle, which it doesn't exist because we created a portuguese alias for that same menu item and article (because of SEO).
Our Joomla is version 3.4.1, with the language filter on with: automatic language change; item associatios; remove URL language code; cookie session.
For translating, we are using Falang component.
Status | New | ⇒ | Confirmed |
Test can't be done with Falang, but with native core multingual feature.
If you use falang, please contact the falang developer.
This has the Language & Strings
label, but should probably have Mult language
instead...
Category | Language & Strings Plugins Router / SEF | ⇒ | Multilanguage Plugins Router / SEF |
Fixed @smz
Hi you created this issue sometime ago but have not provided any code for people to evaluate. As no one else has shown any interest in providing the code and you have not then I am closing this issue at this time. If code is provided (a pull request) it can always be re-examined.
Status | Confirmed | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-05-08 09:47:07 |
Closed_By | ⇒ | brianteeman |
I can't reproduce this issue (Firefox).