-
Notifications
You must be signed in to change notification settings - Fork 87
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
Translation path from wagtailtrans to wagtail-localize #297
Comments
There's not really any overlap between Wagtail Localize and Wagtail trans since Wagtail Localize is a UI built on top of Wagtail's builtin translation models. Documentation for this is coming though! I expect the move from Wagtail Trans to look like:
|
Thank you for the quick reply. I think I got the idea.
Hmm, that's not possible as wagtailtrans prevents the installation of wagtail 2.11. So I will try to fork wagtailtrans first and change that limitation to install it. |
I finally managed to create a migration path. Because it finally needed some more steps as expected I wrote a blog post about it. I also created the necessary fork of wagtailtrans at https://github.com/carrotandcompany/wagtailtrans If anyone has any suggestions, improvements, bugfixes to the migration path or the migration fork, I am happy to update the migration guide. Hope this is helpful for others as well. @kaedroho thanks for the initial idea on how to execute the migration |
@ceelian Hi, didn't you received an error like |
@mentecuantica I don't think so, at which step did the error occur? |
@ceelian Hi, i'm following the steps on your blog post to migrate from wagtailtrans, but when i run the modified migration on step 4 i get the following error:
|
Is there a migration path from wagtailtrans for existing installations to the new native translation system with wagtail-localize?
(As I am not aware to which project it may concern also added this in wagtail/wagtailtrans#208)
The text was updated successfully, but these errors were encountered: