django-modeltrans change log¶
0.1.0 (2017-10-23)¶
- Use proper alias in subqueries, fixes #23.
- Support lookups on and ordering by related translated fields (
.filter(category__name_nl='Vogels')), fixes #13. - Use
KeyTextTransform()rather thanRawSQL()to access keys in theJSONField. For Django 1.9 and 1.10 the Django 1.11 version is used.
0.0.8 (2017-10-19)¶
- Check if
MODELTRANS_AVAILABLE_LANGUAGESonly contains strings. - Make sure
settings.LANGUAGE_CODEis never returned fromconf.get_available_languages()
0.0.7 (2017-09-04)¶
- Cleaned up the settings used by django-modeltrans #19.
This might be a breaking change, depending on your configuration.
AVAILABLE_LANGUAGESis now renamed toMODELTRANS_AVAILABLE_LANGUAGESand defaults to the language codes in the djangoLANGUAGESsetting.DEFAULT_LANGUAGEis removed, instead, django-modeltrans uses the djangoLANGUAGE_CODEsetting.
- Added per-language configurable fallback using the
MODELTRANS_FALLBACKsetting.
0.0.6 (2017-08-29)¶
- Also fall back to
DEFAULT_LANGUAGEif the value for a key in the translations dict is falsy.
0.0.5 (2017-07-26)¶
- Removed registration in favour of adding the
TranslationFieldto a model you need to translated. - Created documentation.
0.0.4 (2017-05-19)¶
- Improve robustness of rewriting lookups in QuerySets
0.0.3 (2017-05-18)¶
- Add the
ginindex in the data migration. - Added tests for the migration procedure.