VirtueMart Forum

VirtueMart 2 + 3 + 4 => General Questions => Topic started by: effettoMapet on April 26, 2023, 06:18:01 AM

Title: Virtuemart custom fields in multi language
Post by: effettoMapet on April 26, 2023, 06:18:01 AM
Hi, I have enabled multilingual on joomle and virtuemart platform. Everything works fine. The problem is not being able to handle languages ​​for CUSTOM FIELDS.
Custom fields do not give the possibility to be translated ?

Can you tell me how I can manage the language of the custom fields I created for my site?

Thanks a lot for your help.
Title: Re: Virtuemart custom fields in multi language
Post by: Jumbo! on April 26, 2023, 17:29:42 PM
You can use custom language constants as the custom field value and then translate the language strings using the Joomla language override.
Title: Re: Virtuemart custom fields in multi language
Post by: balai on April 27, 2023, 16:29:02 PM
Check Custom Fields For All
https://breakdesigns.net/extensions/customfields-for-all

Multi-lingual custom fields is a core feature.
Title: Re: Virtuemart custom fields in multi language
Post by: effettoMapet on April 29, 2023, 08:58:15 AM
Quote from: Jumbo! on April 26, 2023, 17:29:42 PM
You can use custom language constants as the custom field value and then translate the language strings using the Joomla language override.


JUMBO THANK YOU for your reply!
If I understood correctly, I use a language constant from the language file, translate it with an override, and finally insert this language constant in the product's custom field.

I'm sending you a photograph of a test I did.
As you can see in the picture I only entered the language constant but it doesn't work like that.
I guess because I have to write more to retrieve the language constant. Can you PLEASE write me the correct string that I have to write in the custom field of the product? Thanks for your important help.
Title: Re: Virtuemart custom fields in multi language
Post by: Jumbo! on April 29, 2023, 10:05:28 AM
Do not use Editor and textarea type custom fields as they do not get translated. You need to use string type custom fields.