-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move tree synchronisation feature into Wagtail core #386
Comments
Need to consider if this is a blocker too: #469 |
Page tree sync added to core simple_translation in wagtail/wagtail#7548 |
The code in wagtail/wagtail#7548 is something of a partial solution. It adds the |
I agree. I suppose I was thinking for new sites when I posted the comment above. We do have a note to add a background worker mecahnism for the full tree sync to avoid the performance issues. This is where wagtail/rfcs#72 would come in handy |
The tree synchronisation feature creates alias pages of all the content in one locale into another. This is configured using the "Synchronise from" field on the locale.
Merging this feature into Wagtail core will simplify things a little bit. Firstly it removes the need for the
wagtail_localize.locales
app and makes Wagtail Localize purely a translation app. This change would also allow the tree synchronisation feature to be used by other translation appsWe should add this field directly on Wagtail core's
Locale
model (currently it's onwagtaillocalize.LocaleSynchronisation
) and move thesynctree.py
module into Wagtail core somewhere.Before this move, we should solve the following issues:
The text was updated successfully, but these errors were encountered: