unique_together on translated fields about django-parler HOT 6 CLOSED

Good point! That information is hidden from the untranslated model/form, so it makes sense the admin doesn't check this. I think we'll have to override the Model.validate_unique() method, to add this additional check.

Sending a pull request is welcome, if you like to have this fix in django-parler quickly! 👍

from django-parler.

I'm struggling to find the best approach to this.
In the clean phase, the shared model has no access to the translated models (TranslatableModel._translations_cache is still empty / populated with the original values of the translated models), and in the Model.save() phase is too late for the form to catch and manage the ValidationError.
The only stable solution would be to managed the translated models via a ModelForm, but I admit I got lost in the chain of on-the-fly models and form creation process

from django-parler.

@vdboor
It would be great, if you could add that extra meta argument to the documentation for the TranslatedFields. Today I came to the same solution as @yakky pointed out, by reading the source code.

@yakky
do you think it is safe to apply the patch from PR #22 ?

from django-parler.

I'm running #22 on a couple of websites with no issue raised
If @vdboor likes it I can rebase it anytime

from django-parler.

Hi @yakky! Sorry for not getting back to this before! Based on your comment, I think the solution could be a bit more improved. After that we can merge. Shall we continue the discussion in #22?

from django-parler.

@vdboor sure

from django-parler.