You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each site should have it's own translations. Site A might be in English and Spanish. Site B might be English and French.
Is this a supported workflow? I don't see any means of making a "languageless" Site A with a nested English home page and Spanish home page. Without this concept, translating a nested Site A English page to Spanish will create a new root level site. This causes the translated page to not be part of the Wagtail Site at all.
Unwanted tree structure after making a translation:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Related to #380
I have a use case like this
Wagtail Root
Each site should have it's own translations. Site A might be in English and Spanish. Site B might be English and French.
Is this a supported workflow? I don't see any means of making a "languageless" Site A with a nested English home page and Spanish home page. Without this concept, translating a nested Site A English page to Spanish will create a new root level site. This causes the translated page to not be part of the Wagtail Site at all.
Unwanted tree structure after making a translation:
Wagtail Root
Site A a.example.com
Site B b.example.com
Site A (Spanish)
Example project showcasing the issue https://gitlab.com/thelabnyc/wagtail-localize-multisite-demonstration
Beta Was this translation helpful? Give feedback.
All reactions