News:

You may pay someone to create your store, or you visit our seminar and become a professional yourself with the silver certification

Main Menu

VirtueMart 2.02: Problem saving data in several languages

Started by Enforced, April 01, 2012, 16:14:39 PM

Previous topic - Next topic

Enforced

Hello,

I'm using Joomla 1.7 and Virtuemart 2.02 in catalog mode. Because my site uses serveral languages (Dutch, French and English), I want my catalog to use the same languages.

When I input the text in Dutch, everything works fine, but than when I try to add the French or English text, I recieve an error: "No FR translation in product (category), please fill in the fields with a flag".

After I fill in these fields; I try to save. Joomla tells me everything has been saved correctly, but when I return to the product, the changes have dissapeared.

Any tips on how to fix this? Thanks in advance!

Best regards



acortes

Hello,
I have the same problem. my environment is joomla 2.5.4 and virtuemart 2.0.6

I have 2 languages installed on joomla and virtuemart. All the joomla side is running right on multilanguage (menus, articles, modules, language switcher).

In virtuemart side I have these languages activated, but in any multilanguage field I have the save behaviour: right saving the main language, with the second language I entry the data and save (debug is saying that data is stored in the second language tables) but when reopen the data for second language has disappeared and appears the same message " No EN translation in product (category), please fill in the fields with a flag". The problem is in products, categories, shop information, in any place with a multilanguage field, and always the same behaviour.

Is there any solution? or what I'm doing wrong?

DaggaTora

I have the same problem since i've updated to 2.0.6... can't go online because of this.
Joomla 2.5.17 | VM2.0.26d | PHP 5.3.28

nobynobs

Hi,

faced the same issue. Solved it by using the virtuemart tool "install tables or if necessary update them". This updated some corrupt tables and fixed the issue - without any data loss!
however, as always, update is strongly recommended before doing that.

this worked for me on joomla 2.5.6 and vm 2.0.6