[FIX] Follow up to !4877, if multilingual fields exist but are empty (which is...
- [FIX] Follow up to !4877 (merged), if multilingual fields exist but are empty (which is the case after activating multilingual, but before filling), use the original string. So now uses the same logic for setting when feature_multilingual===y than normally: Only use the string if it's not empty.
(cherry picked from commit 5e696af8) (!4923 (merged))
Co-authored-by: Benoit Grégoire benoitg@coeus.ca