A missing field should not cause an exception when trying to save a translation

Is this issue still being worked on? I am facing this issue too often.

I have provided a setting in admin to enable and disabled to throw this error.

Thanks @vikramsaini1609 for this patch.

It worked well for me.

I don't get the setting. It's not an exception anymore, just a warning, and I think it's worth to always do that, don't see the benefit of hiding the fact that some provided translations couldn't be saved.

The second part of my review in #22 wasn't applied and tests weren't added either as I asked in back in #15.

ioana apetri → made their first commit to this issue’s fork.

Hello, I have provided the changes discussed in #24. Thanks

Amazing, a test :)

Thanks, merged.

Automatically closed - issue fixed for 2 weeks with no activity.