Aliases are not created for affected translations

#4 Worked for me too !

Patch #4 works great for me as well. RTBC ++

Thanks for the work.

Thanks for the work.

Patch #4 works great for me as well.

Can also confirm that #4 works.

This is a 5 year old patch that multiple people have mentioned works.
What is holding it back to get it in the next release ?

Patch #4 works great

Re #12:

It would need to be within the loop, but as commented by others, there are cases where aliases still need to be updated even if the translation didn't change, so I suppose not much can be done about that.

#28: The performance concerns, mostly.

This might hurt sites with a lot of languages quite a bit. There are now 3 places with this loop, the first one is in bulk generate. Also, we have issues like #2946354: Alias not using language undefined when alias is not translatable → with the goal of supporting language-neutral aliases. This change is going to make that more complicated because then we'd call it multiple times but really will always create/update the same alias. So this loop should possibly be within updateEntityAlias(), after checking the language setting of the field and depending on that once the other issue lands.

Thanks for the patch/MR.
I've applied the MR diff to one of our sites, and the issue has been resolved.

Hopefully this finds its way into a release 🙏