Open alexalligator opened 1 year ago
I think if you also make ProductPageMaterial translatable it should show up?
The key doesn't get translated and will always point to the key in the locale the page was created in. You should be able to get the translated child object by localising it.
page.localized.material.localized
Thanks for your comments, I'll look into them and report back.
Creating issue after posting to slack #multi-language and discussing with @zerolab
I have a translatable snippet which I add to a page model via an inline model:
What happens:
I see that a new ProductPageMaterial has been created by wagtail/wagtail-localize. It's page foreign key field is pointing the new english version of the page as expected. The material foreign key field, however, is still pointing to a norweigan material. I would expect to see the local (english) material in the same way I see the local page.
I have made this temporary workaround but don't image it will be relevant for any long term solution: