I'm trying to create a bilingual shop with i18n and eCommerce. I'm not sure, whether this is a i18n or eCommerce issue, though...
When I create an eCommerce product, I can choose its language. Now, when I select «translate» from the tabs I get sent to a page where I can select what type of product I want to create instead of right to the page where I can enter information. I know, what product I want to create (the end user won't), but this step shouldn't be necessary. Anyway, I select my product-type and create a translation. Unfortunately, by this time, i18n seems to have forgotten, that I'm trying to translate something and the products' translated counterpart doesn't show up. I now have to manually select, what node is the translation of my original node. This just isn't an acceptable workflow for my end users.
So, I figured out, that translate.module, when creating an «add translation» link, only puts «product» as node type into the url, what would be needed is something like «node/add/product/apparel/translation/63/add». But that wouldn't work because translate.module gets its arguments via the arg() function.
Now, I don't know, whether this is an i18n (or eCommerce) thing that can be fixed. Should I better give up and create separate shops (maybe via taxonomy)? Or can anyone point me into the right direction? Thanks!
Comments
Comment #1
jose reyero commentedWell, this is a 'i18n module not dealing with some e-commerce features' :-)
I've changed the url handling for translations in the latest release and I think it might help -now it's handled using query string-. However I havent tested yet with e-commerce.
Please, let me know if it gets any better.
Comment #2
jose reyero commentedFixed. You can translate products now. Please confirm
Comment #3
(not verified) commentedComment #4
binhcan commentedNot fixed. It's translating products but doesn't allow synchronyzation of product details such as SKU and Price... It's very important to have those synced because then we have the same product on multilingual, otherwise it's just duplicated products with the same SKU.
This is the biggest concern: SKU and Price. Another concern is price should be converted using the Currency module as well, otherwise please allow to change.
Comment #5
BernardGatt commentedAny update on the issue binhcan?? Still having the same problem here.
Thanks,
Bernard.
Comment #6
ossama.selim commentedComment #7
ossama.selim commentedwhere is the italian translation of the ecommerce module?help!!sorry i forgot to say for drupal 6.20