The taxonomy field handler fails on content created in a non-default language

Hey @dieterholvoet.
Did you look at the plugin system where you can hook in your own field handlers?
This starter kit shows how to do it.
While I get what your trying to do, changing this might break entity references for others.

Yes, I noticed the plugin system, but this sounds more like a bug then a feature. I personally think it's a reasonable change. It would only break things on sites where a certain term exists in different language versions of different terms, which seems unlikely. E.g. the NL version of term A has the same name as the FR version of term B. More unlikely than someone wanting to use associate translated terms with nodes.

An alternative solution that's less likely to break stuff would be to first query the specific language and if that doesn't yield any results, query without language. Does that sound like something you would agree to merge?

I think that might indeed be a good failsafe to add to it.
We can merge if this is added, thanks for understanding.

I updated the MR.

Merged and released in version 3.0.1

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