You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think, that in admin: user (who use admin) must understand, what fields must be translated, and what fields are "static" (without translation).
Maybe, addition separator (between "static" and "tranlsation" fields) or some highlighting title - good idea.
The best (IMHO): add some highlighting title and don't change order (same fields order, like in model). Thanks^)
The text was updated successfully, but these errors were encountered:
this is something the developer of a multilingual app can do using use_fieldsets. I'm not too happy with the idea of an automated way to do this, maybe I'll think of some 'default' way in case you don't specify your own fieldsets...
Since Django maintains model fields order, leaving the translation fields unordered breaks expectations, which is wrong (TM).
The fieldset part should indeed be the developer's job. Unless you consider issue #10.
Well this would be a optional 'auto-fieldsetting' anyway. I would not enforce this. You can always provide your own fieldsets.
I personally think that some sort of smart default fieldset would be nice. But it has no priority for me at the moment. If someone want's to write up some code for this, go right ahead though.
I think, that in admin: user (who use admin) must understand, what fields must be translated, and what fields are "static" (without translation).
Maybe, addition separator (between "static" and "tranlsation" fields) or some highlighting title - good idea.
The best (IMHO): add some highlighting title and don't change order (same fields order, like in model). Thanks^)
The text was updated successfully, but these errors were encountered: