django-translated-fields | Django model translation without magic-inflicted pain | Translation library

Please take a look at this issue:

How do I use ModelForm with django-translated-fields?

Do you have any solution?

In short, I'm trying to convert Speedy Net from using django-modeltranslation to django-translated-fields. I defined the models and forms and everything works in English, but in another language (Hebrew) I have a problem that the form fields are defined in English instead of Hebrew (the current language). What did I do wrong and how do I define the form to work in the current language? (the fields defined by TranslatedField in the model should be visible only with the current language in the form SpeedyMatchProfileActivationForm).

I want to clarify that the desired definition is not as above. The desired definition is to use the current language in the form and not always English. Using English when the current language is not English is a bug.

You can see the code here:

tree

forms.py

models.py

The problem right now is with the class SpeedyMatchProfileActivationForm (defined in forms.py). I think it is mainly because the class is defined before get_language() returns anything. But when the class was defined with django-modeltranslation (for example in branch staging), it worked.

By the way, one of the reasons I want to switch to django-translated-fields is because it defines only 2 (the number of languages) fields in the database, and django-modeltranslation defines 3 fields - one of them (the main field without any language) seems to me not necessary at all. Take a look at: Remove original language field on migrations

class SpeedyMatchProfileActivationForm is defined now (with django-translated-fields, link):

I have a ModelForm with Django 2.1, and I moved a few fields to another model. Calling make_migrations causes an error because these fields don't exist in the current model. I added some of the fields to the form, but one of the fields is a TranslatedField (from django-translated-fields) and therefore there are currently 2 fields, and in the future there might be more, depending on the number of languages. The name of the field is city, and currently I get an error message "Unknown field(s) (city_en, city_he) specified for SiteProfile" (because I'm using 2 languages - "en" and "he") - but I want to create all the fields dynamically with a for loop over the languages we use in the project. Can I override (and is it a good programming method) the __new__ method or is there another way? I prefer not to hard-code the specific field names (city_en and city_he) because they may change in the future, depending on how many languages we use.

You can see my current commit (not working) on GitHub.

And the current code of this branch.

I would like to know what is the best programming method to define a dynamic list of fields (which are all identical, and only one of them will be used, the other are removed in the __init__ method) in a ModelForm where the fields are saved in another model (there are 2 models but only one form).

I still didn't commit the migrations because of this error when running make_migrations.

(I defined a command make_migrations which only does makemigrations)

The form (with my trying to override __new__):