Custom field values translation

Hi,

If you're using non latin characters for the original values, you need to activate the "Non-latin translation keys" setting under the Languages tab of the HikaShop configuration.
Note that this is not only for the custom field values, but for anything you translate in your shop.
Note also that you'll loose the translations you've already done with the setting turned off when you activate it as HikaShop will search for new keys adapted to non latin texts.
Otherwise, another solution is to use the English text as your original values title and enter the other language text as translations. That way, the system will be able to use latin translation keys and it will work fine.

Hi,

Sure. Please provide a backend access and the URL of the page on the frontend via our contact form:
www.hikashop.com/support/contact-us.html
Please make sure you include a link to this thread for reference.
Also, if we need to debug the situation we will probably need a FTP access.

Hi,

I think you're mixed up with your custom fields.
The URL of the page you provided doesn't have an custom field with values.
All the custom fields there are of the type "text".
To translate them, you need to activate the "Translatable" setting of the custom field and then configure the translation in each product.
And for the "ΣΧΗΜΑ" custom field you've configured in your backend, while you can select it in each product in the backend, you didn't activate its "frontend" display setting so it actually doesn't appear on the product page of the frontend.
If you activate it, you'll see it at the top of the list of the custom fields and you'll see the value selected is properly translated.
So it's working fine as far as I can see.

Hi,

I've done some debugging and the conclusion I came up to is that it must be an issue in Falang.
We do a MySQL query to load the data of the menu item from the joomla table and between the Greek and the English, we get a different "params" and the HikaShop params from the menu are missing.
I suppose that it's a combination of factors: the fact that you have Maximenu CK adding its parameters for the menu items might interfer with the translation mechanism.

I've made a patch to forcibly load the parameters from Joomla in case the parameters are missing and this circumvents the problem.
We'll add the patch on our end.