Jacek Tomaszewski

@romansemko You need to change `SegmentOptions` to NOT inherit from `BaseSegmentOptions`. That's because fields are inherited this way: http://django-modeltranslation.readthedocs.org/en/latest/registration.html#translationoptions-fields-inheritance And `SegmentOptions.fields == ('name', 'label', 'description')`. But `name` is the field...

Good point.

@deschler: I'm currently on a vacation, I'll take a look a bit later. ;)

@deschler It seems ok. I've tried fallback values and it works. But I fear that it may fail with fallback languages. Values in database would be different for each language...

If you want to show all fields, use `ModelForm`. `TranslationModelForm` is intended to hide all transaltion fields: http://django-modeltranslation.readthedocs.io/en/latest/forms.html Also please check if form is not being registered too early: http://django-modeltranslation.readthedocs.io/en/latest/registration.html#precautions-regarding-registration-approach

Use `title_ru`. The original field (`title`) is not containing any specific language. It rather shows/writes current active language.

No, you cannot stop it. Again, it's in the docs: http://django-modeltranslation.readthedocs.io/en/latest/usage.html#the-state-of-the-original-field However, you can always tweak the form to assign a value of your choice to `title` input/field

It should be as easy as this: ``` python from django.contrib.auth.models import Group from modeltranslation.translator import translator, TranslationOptions @register(Group) class GroupTranslationOptions(TranslationOptions): fields = ('name',) # or whatever these fields are...

Current RC should fix this.

What did you change, e.g. what were the values of `fields` before and after change? Which MT version are you using?