Dirk Eschler 1476e5483b Removed fix for grouped fieldsets committed in r124 because of a regression. This means grouped fieldsets are currently unsupported.		2012-02-23 09:53:56 +00:00
..
management	Improved performance of update_translation_fields command. Resolves issue 43 (thanks to adamsc).	2010-09-06 08:58:52 +00:00
static/modeltranslation	Changed jQuery search path. This allows use of a version of jQuery other than the one provided by Django. Users who want to force the use of Django's jQuery can include force_jquery.js.	2012-02-23 09:31:16 +00:00
__init__.py	Initial source and metadata import.	2009-02-17 21:08:19 +00:00
admin.py	Removed fix for grouped fieldsets committed in r124 because of a regression. This means grouped fieldsets are currently unsupported.	2012-02-23 09:53:56 +00:00
fields.py	Removed experimental support for related fields. The code is now available in a separate branch called django-modeltranslation-related-fields. To support related fields properly, deeper changes to the core of modeltranslation are required. These changes are beyond the scope of the next release.	2010-09-06 12:29:23 +00:00
models.py	Factored out settings into a separate settings.py and consistently used an app specific settings prefix, TRANSLATION_REGISTRY now deprecated in favour of MODELTRANSLATION_TRANSLATION_REGISTRY.	2010-06-26 08:54:08 +00:00
settings.py	Changed handling of supported fields. By default CharField, TextField and subclasses of these fields are supported. Supported fields can be extended through the setting MODELTRANSLATION_CUSTOM_FIELDS. Support for related fields is experimental and these fields explicitly raise a FutureWarning now.	2010-08-27 08:39:41 +00:00
tests.py	Added support for multi-table inheritance. Resolves issues 50 and 51 (thanks to Sébastien Fievet).	2011-06-01 15:25:40 +00:00
testurls.py	Code cleanups.	2010-03-02 22:17:39 +00:00
translator.py	Added support for multi-table inheritance. Resolves issues 50 and 51 (thanks to Sébastien Fievet).	2011-06-01 15:25:40 +00:00
utils.py	Fixed a bug in the admin integration where an emptied default language field (which has been defined with "blank=True") hasn't cleared the default field. Resolves issue 47.	2011-04-10 20:27:24 +00:00