Migrating away from modeltranslation #423
Conversation
|
|
||
| Now that you have a non-localised version of Wagtail running, you are ready to install `wagtail-localize`. | ||
|
|
||
| See [Step 2. Configure Wagtail Localize](../../tutorial/2-configure-wagtail-localize.md) to get started installing |
There was a problem hiding this comment.
I think we should link to the installation guide here: https://www.wagtail-localize.org/how-to/installation/
|
|
||
| !!! note "Careful with production data" | ||
|
|
||
| Make sure you run these steps in a testing environment first. Once the fields (above) are deleted from your |
There was a problem hiding this comment.
Do you think it would be possible to generate locale trees using the translations already created for the modeltranslation site?
There was a problem hiding this comment.
I am currently working on migrating a production site from wagtail-modeltranslation to wagtail-localize and might write up what needs to be done to migrate the existing translations.
There was a problem hiding this comment.
That is great to hear @saevarom! Looking forward to it
|
@KalobTaulien do you have time to revisit this PR? |
|
Thanks for starting this! I'm not sure how I would benefit from the current state of the guide -- I would like to know how to a) migrate the actual translations so they're not just deleted and b) some guidance on how the 1:1 translation of modeltranslation and wagtail-localize compare. |
|
@benjaoming have you seen https://www.cnc.io/en/blog/wagtailtrans-to-wagtail-localize-migration ? While not directly modeltranslation, it should hopefully provide a good starting point on the process. |
zerolab
force-pushed
the
main
branch
3 times, most recently
from
c7c2117 to
1fc56b0
Compare
Documentation on how to migrate away from wagtail-modeltranslation.