- Posts: 31
- Thank you received: 3
Where are store Product Translations in database ?
3 years 7 months ago #349568
by _Pascal_
Where are store Product Translations in database ? was created by _Pascal_
Hi
I would like to mass update products and I'm looking for translation but I don't know in what tables they are ?
Could you help me ?
Regards
I would like to mass update products and I'm looking for translation but I don't know in what tables they are ?
Could you help me ?
Regards
Please Log in or Create an account to join the conversation.
3 years 7 months ago #349569
by _Pascal_
Replied by _Pascal_ on topic Where are store Product Translations in database ?
Ok, I think it's overwride .ini files if Falang is not installed...
Please Log in or Create an account to join the conversation.
3 years 7 months ago #349571
by nicolas
Replied by nicolas on topic Where are store Product Translations in database ?
Hi,
Indeed. The translations you add in HikaShop are stored in the translation override file of your website if you're not using Falang.
With Falang, it's in the #__falang_content table.
Indeed. The translations you add in HikaShop are stored in the translation override file of your website if you're not using Falang.
With Falang, it's in the #__falang_content table.
Please Log in or Create an account to join the conversation.
3 years 6 months ago - 3 years 6 months ago #349646
by _Pascal_
Replied by _Pascal_ on topic Where are store Product Translations in database ?
Thanks Nicolas
I have a question about falang_content table...
How is calculated the original_value column ?
I put reference_id + reference_table = hikashop_product + product_name + language_id but there is no change
Is this a problem of variants in my product ?
I have a question about falang_content table...
How is calculated the original_value column ?
I put reference_id + reference_table = hikashop_product + product_name + language_id but there is no change
Is this a problem of variants in my product ?
Last edit: 3 years 6 months ago by _Pascal_.
Please Log in or Create an account to join the conversation.
3 years 6 months ago #349650
by nicolas
Replied by nicolas on topic Where are store Product Translations in database ?
Hi,
reference_id is auto_incremented by MySQL when you insert an entry in the table. It's the id of the translation. You don't need to provide it when you add an entry to that table
language_id is the id of the language in Joomla
reference_table is the name of the target table. For a product, it should be hikashop_product
reference_field is the name of the target column in the target table. For a product description, it should be product_description
original_value is the original text to be translated.
value is the translated text
published needs to be set to 1
The rest of the columns in falang_content are not important.
First, you need to make sure your can translated a Joomla article in the different languages on your frontend. Once that's working, and the Falang driver system plugin is enabled, it will translate the content of HikaShop based on the entries in the falang_content table.
reference_id is auto_incremented by MySQL when you insert an entry in the table. It's the id of the translation. You don't need to provide it when you add an entry to that table
language_id is the id of the language in Joomla
reference_table is the name of the target table. For a product, it should be hikashop_product
reference_field is the name of the target column in the target table. For a product description, it should be product_description
original_value is the original text to be translated.
value is the translated text
published needs to be set to 1
The rest of the columns in falang_content are not important.
First, you need to make sure your can translated a Joomla article in the different languages on your frontend. Once that's working, and the Falang driver system plugin is enabled, it will translate the content of HikaShop based on the entries in the falang_content table.
Please Log in or Create an account to join the conversation.
Time to create page: 0.244 seconds