Not sure if this is a bug in Wagtail trans, or if we are doing something wrong with our configuration:
Issue summary
When a user visits the site with their browser set to a language that is in Draft state, the site fails to route to the user to the default language. Instead, it tries (and fails) to load the Draft language version, resulting in 404 error. This is particularly a problem because the translators need to have the translated pages in Draft state while they work on the translations.
Steps to replicate:
Create a translation of your site home page in Spanish (or another language you don't have yet)
Save as Draft (don't publish)
Change your language setting in your browser to Spanish (or chosen test language)
Restart browser to apply the setting
Open an incognito browser window (to ensure you don't have cookies set)
Open site
View error
Other Note
This only happens when the "Live" checkbox on the language setting is selected. If you uncheck "live", it does successfully reroute to default language site. However, this is not a solution to this problem because when "Live" is unchecked, pages do not give you the option to "translate into" that language - which is needed to create a Draft translated page for translators to work on.
It's possible that rather than fix the routing as is (with "live"), the solution is actually to uncheck "live" and then fix the "translate into" menu options so that admins can create translated pages of non-Live languages.
Technical details
Does not seem browser-specific, but I've been mostly testing in Firefox
Not sure if this is a bug in Wagtail trans, or if we are doing something wrong with our configuration:
Issue summary
When a user visits the site with their browser set to a language that is in Draft state, the site fails to route to the user to the default language. Instead, it tries (and fails) to load the Draft language version, resulting in 404 error. This is particularly a problem because the translators need to have the translated pages in Draft state while they work on the translations.
Steps to replicate:
Other Note
This only happens when the "Live" checkbox on the language setting is selected. If you uncheck "live", it does successfully reroute to default language site. However, this is not a solution to this problem because when "Live" is unchecked, pages do not give you the option to "translate into" that language - which is needed to create a Draft translated page for translators to work on.
It's possible that rather than fix the routing as is (with "live"), the solution is actually to uncheck "live" and then fix the "translate into" menu options so that admins can create translated pages of non-Live languages.
Technical details