- Issue created by @Shamrockonov
- 🇬🇧United Kingdom Shamrockonov
Added an issue fork with a possible solution?
The request is redirected back to the original domain on a finalRedirect multi_domain_login route to handle the URL generation on the original domain. - 🇬🇧United Kingdom Shamrockonov
shamrockonov → changed the visibility of the branch 1.0.x to hidden.
- Merge request !11Adds a final redirect route to handle the success redirect → (Merged) created by Shamrockonov
- 🇬🇧United Kingdom Shamrockonov
Not sure I like the additional redirect really. Open to suggestions.
- 🇧🇪Belgium kriboogh
Hi, if I understand correctly you have:
Language negotiation on domain level set to:
www.dutch.com => NL (alternative language)
www.english.com => EN (default language)You have a custom controller route:
/some/controller/englishA path alias:
/some/controller/english => /some/controller/dutch (langcode NL)Multidomain success url is set to:
/some/controller/englishWhen you login from EN domain you get:
www.english.com => www.dutch.com => www.english.com/some/controller/englishWhen you login from NL domain you get:
www.dutch.com => www.english.com => www.dutch.com/some/controller/englishBut you expected:
www.dutch.com => www.english.com => www.dutch.com/some/controller/dutchCorrect?
- Status changed to Postponed: needs info
16 days ago 1:39pm 20 January 2025 -
kriboogh →
committed de809159 on 1.0.x authored by
shamrockonov →
Issue #3476679: Incorrect Redirect Success URL generated on multilingual...
-
kriboogh →
committed de809159 on 1.0.x authored by
shamrockonov →
-
kriboogh →
committed 5524ee91 on 1.0.x
Issue #3476679: Add language in the login urls so we can redirect to the...
-
kriboogh →
committed 5524ee91 on 1.0.x
- 🇧🇪Belgium kriboogh
I added the langcode of the original referrer route to be passed along the login chain so that in the end the redirect url can be translated into this language. This eliminates the extra redirect.