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
Is anyone successfully using wagtail-personalisation in a project that also includes wagtailtrans? I've come across two issues using the two together...
My variant pages never show. Stepping through the debugger, I found that serve_variant calls serve on TranslatablePage, which when passed a view in the serve_args by serve_variant ends up returning view(request, *args, **kwargs) on the canonical page instead of on the variant.
The second issue is that it seems it's not possible to create a variant of a home page when using both packages because wagtailtrans requires precisely one homepage per language.
If anyone has solved these issues, I'd love to know how.
The text was updated successfully, but these errors were encountered:
We have looked into this combination for one of our projects, and identified what needs to happen to make the modules compatible. However the project was canceled, so we never started/completed the work.
The page sync function doesn't work as expected in combination with Wagtailtrans and wagtail-personalisation.
For example;
When i create a page-variant in the default language (NL), that works well
Wagtailtrans also creates this page-variant for all the other languages (EN)
This isn't a problem, but they aren't linked to the TranslatablePage, so Wagtail responds like it are separate pages and not a variant.
The issues are:
They page-variant are displayed as separate pages in my page-tree.
They doesn't respond as a variant, that means they aren't active for the selected segments and never displayed.
Wagtailtrans Hide Translation tree
If WAGTAILTRANS_HIDE_TRANSLATION_TREES=True, WagtailTrans should display only one page tree, and a dropdown "Edit in" with all the available languages.
When i create a variant for the page, and i click on "Edit in", i see multiple times the "English" language.
I think they should be suffixed with the variant-name so we can see the differences between the pages.
Is anyone successfully using wagtail-personalisation in a project that also includes wagtailtrans? I've come across two issues using the two together...
My variant pages never show. Stepping through the debugger, I found that
serve_variant
calls serve on TranslatablePage, which when passed a view in theserve_args
byserve_variant
ends up returningview(request, *args, **kwargs)
on the canonical page instead of on the variant.The second issue is that it seems it's not possible to create a variant of a home page when using both packages because wagtailtrans requires precisely one homepage per language.
If anyone has solved these issues, I'd love to know how.
The text was updated successfully, but these errors were encountered: