Home›Support›English Support›[Resolved] Long description of products not appearing translated in secondary language
[Resolved] Long description of products not appearing translated in secondary language
This thread is resolved. Here is a description of the problem and solution.
Problema: El cliente tenía problemas con la descripción de productos que no aparecían traducidos en el idioma secundario. Solución: 1. Pedimos al cliente que actualizara todos los plugins y temas desactualizados para evitar conflictos en el código. 2. Tradujimos dos cadenas de texto específicas y pedimos al cliente que confirmara si el problema se había resuelto. 3. Actualizamos la traducción al 100% de un producto y sugerimos al cliente que hiciera lo mismo con otro producto como prueba, asegurándose de descartar la traducción en la sección de traducción de cadenas por el momento.
Si estás experimentando este mismo problema, te recomendamos que sigas los pasos anteriores. Sin embargo, la solución podría no ser relevante para tu caso si es obsoleta o no aplicable. En ese caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins. Si necesitas asistencia adicional, por favor, contacta con nosotros en el foro de soporte de WPML.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
we translate a new product via Woocommerce Multilingual -> Products tab
There we translate all the fields to 100% and check translation is complete and save.
And that is all that we do.
I can't tell you about all the updates made to the plugins since we didn't detect issues until we manually checked products on front end and saw that translations are missing or in a default language. I cant say for how long these problems are occuring.
The only field that is affected is description field.
We have disabled themify builder a long time ago.
I don't think this is the problem since all the translations would then be missing because this code is on every product.
I have no clue how to solve this issue, there are a bunch of products with missing descriptions.
Is there a way we can retrieve missing translations from database?
I have searched for this id but found only: <!-- wp:themify-builder/canvas /-->
inside post_content.
When we save the product translation in Woocommerce Multilingual product tab, a new wp_post is made and description is saved inside post_content? Nowhere else?
Please check this product:
ID CRO: 63893 hidden link
There is correct translation inside post_content in the database:
<p>Dvije društvene igre u jednoj: Čovječe ne ljuti se i Mlin. Odlične su za zabavu djece starije od 3 godine. ˝Čovječe ne ljuti se˝ je igra za 2 - 4 igrača, ˝Mlin˝ je zabavna igra za dva igrača. Baci kockicu, pomakni figuricu i prvi dovedi sve figurice na cilj ili slaži pločice i pokušaj složiti mlin.</p>
<!-- wp:themify-builder/canvas /-->
----------------------------------------------------------------------------------------------
But if we go to Woo Multilingual Product tab and try to edit translation the description field is empty!
Where is this field taking the description from if we are seeing correct translation in the database?
This is serious problem since for updating the translation we need to copy description again, otherwise this will overwrite the post_content field with empty value. Is this correct?
To me it looks that in the Woocommerce Multilingual Product tab, some links between post_cotent, job ids etc. are missing and don't fill the description field even though post_content is correctly.
I would like to know if we add the description again and save product will these desciptions remain or would vanish again? We have no time to repeat translations again.
I suspect that the cause of this issue is related to a page builder deactivated some time ago. If you translate the post content again and save it, it should solve the problem.
Could you translate a product body again and check if the issue disappeared with that specific product?
If you delete a translation package a product/post/page with that ID would be empty if you opened its translation in the Classic Translation Editor. So there should be no translated strings there.
If you deleted a translation package and the issue was solved for the associated product, then something is wrong at a database level.
I would like to ask for your authorization to create a copy of the site in order to escalate this ticket to our 2nd tier of support.
Hi Jan,
Thank you very much for your authorization.
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue. Please don't delete the staging site until we solve the ticket.
I will get back to you as soon as I get an answer from our 2nd tier specialists.
Unfortunately, our specialists didn't find any solution for this case, except for updating the translation of the products.
They studied all scenarios, including this last one: https://wpml.org/forums/topic/long-description-of-products-not-appearing-translated-in-secondary-language/page/2/#post-10467533 and the answer to the question "is it possible to have a correct translated post_content field that is not picked up by the Classic Translation Editor?" is:
Yes, it is possible if the translation was made manually (or edited the product translation manually) or when WPML was disabled.
The source (original contents) are populated from the original post itself, while the translations are populated by the entries in icl_translate for the specific job that was created when was sent to translation (or clicked the plus button) and it can contain no data based on that.
Thank you very much for your patience and understanding.
Best regards,
Carlos
