![]() ![]() ![]() Someone have the same problem and he can help me to solve it? I've looking for into the drupal site and commerce guy site to find if there was some other issue with the same problem but without result. If I put on the server EntityAPI - RC1 i see the "selection field" translated, if I put a new version of EntityAPI from RC2 to latest DEV the the "selection field" are not translated. ![]() I've make a lot of test to understand if there was some wrong configuration. I've create a new clear installation of drupal with "Drupal Commerce" - "Internationalization" - "Entity Translation" - "Entity API" to replace the problem (see the attached image). If I configure the "product reference" field to "Render fields from the referenced products when viewing this entity." I see the option into the node correctly translated. I've checked the products and they are translated. When the version of EntityAPI has been update to version RC2 (I've tested it also with the latest dev version) the "Selction Form" of variant product don't translate more the vocabulary terms. When I've started to develope the project this system was working correctly and translation was showed correctly also inside the "selction form" of product variants. The view node use Multilingual Support of Internationalization to translate it (there is not enable Entity Translation). When all variants are created and translate this products are connectde to a "View Node" using a "Product Reference" Field. The user create the Products and later translate it using "Entity Translation". The Products Types was created using "Term Reference" Field connected to a "Localized" taxonomy vocabulary. I've developed a Commerce Site using Drupal Commerce. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |