Fallback value explained

[schumannd]

I am having trouble understanding fallback behavior of this project.

If I translate e.g. a field "name" into "name_en" and "name_de", but leave both empty. Should the value in the "name" column be displayed?

I noticed that after running the migrations all translated fields were displayed as empty in the admin. Only after running

./manage.py update_translation_fields

Were the default strings displayed. This is because all strings in "name" were copied into "name_de".

Is there a fallback setting, that would cause the content of the "name" column to be displayed if the other columns are empty?

[rubenanapu]

I just had the same requirement (or expected behavior) as yours, @schumannd

What I did was the following:

Just modified the last line of TranslationFieldDescriptor.__get__ to the following

-           return default
+           return default or instance.__dict__[self.field.name]

In my tests, it seems to be working as I expected.

[alirezaemami]

return default or instance.dict[self.field.name]

Yes that works nice, did you sent a merge request?

[last-partizan]

Running ./manage.py update_translation_fields after adding a field is recommended way to solve this issue.

Suggested patch might work, but I'd prefer to keep things as is. Or maybe there's cases where something prevents you from running update_translation_fields?