-
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
Migrating away from modeltranslation #423
Open
KalobTaulien
wants to merge
1
commit into
wagtail:main
Choose a base branch
from
KalobTaulien:modeltranslation-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
# Migrate from wagtail-modeltranslation | ||
|
||
|
||
### Remove wagtail-modeltranslation | ||
|
||
|
||
The package wagtail-modeltranslation, when installed and used, will add a new column in your database for every field | ||
you have. | ||
|
||
So if you have: | ||
``` | ||
class MyPage(Page): | ||
custom_field = models.CharField(...) | ||
``` | ||
|
||
It will generate `custom_field_en`, `custom_field_de`, `custom_field_fr`, and so on for every field in your page. | ||
|
||
We need to remove the package and then remove the fields to clear out the database. | ||
|
||
!!! note "Careful with production data" | ||
|
||
Make sure you run these steps in a testing environment first. Once the fields (above) are deleted from your | ||
database, the translations will be lost forever. | ||
|
||
|
||
### Remove the packages from your INSTALLED_APPS | ||
|
||
Find your ``INSTALLED_APPS`` and delete the following lines (if they are present): | ||
```python | ||
'wagtail_modeltranslation', | ||
'wagtail_modeltranslation.makemigrations', | ||
'wagtail_modeltranslation.migrate', | ||
``` | ||
|
||
### Remove translation options | ||
|
||
If you have any ``TranslationOptions`` used in any of your files, delete those classes too. They often look something | ||
like this: | ||
|
||
```python | ||
from modeltranslation.translator import TranslationOptions | ||
from modeltranslation.decorators import register | ||
|
||
@register(MyWagtailPage) | ||
class MyWagtailPageTR(TranslationOptions): | ||
fields = ('title', 'body',) | ||
``` | ||
|
||
Deleting these classes will prevent Wagtail from trying to translate your content. | ||
|
||
!!! note "A common practice..." | ||
|
||
A common practice with wagtail-modeltranslation is to use a ``translation.py`` file. If you only have translation | ||
classes in this file, you can delete the entire file. | ||
|
||
|
||
### Make migrations and apply them | ||
|
||
At this point your wagtail-modeltranslation code should be removed from your code base. The last step is to create | ||
new migration files, and apply them to your database. | ||
|
||
```bash | ||
python manage.py makemigrations | ||
python manage.py migrate | ||
``` | ||
|
||
!!! note "Don't forget to update your requirement files" | ||
|
||
Make sure you update your requirment files, Pipfiles, and other source files so you aren't accidentally | ||
installing wagtail-modeltranslation again. | ||
|
||
|
||
### You're ready to install wagtail-localize | ||
|
||
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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should link to the installation guide here: https://www.wagtail-localize.org/how-to/installation/ |
||
wagtail-localize. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am currently working on migrating a production site from
wagtail-modeltranslation
towagtail-localize
and might write up what needs to be done to migrate the existing translations.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is great to hear @saevarom! Looking forward to it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so... how did it turn out 😛 ?