Problem: The client was unable to use the automatic translator to translate pages from English to Slovenian, receiving an error message stating that content can only be automatically translated from the site's default language to other languages.
Solution: 1. We asked the client to first resolve any issues from the original support ticket, as the translation problem could be related. 2. We identified that the homepage was built using widgets and that the Slovenian version of the homepage did not display any content because the appropriate widgets for the Slovenian language were not displayed. We advised the client to go to the widgets section and set up the widgets to display in the Slovenian language, providing screenshots as an example.
We also cautioned that if there are compatibility issues with the client's custom theme, we may not be able to debug it, as it falls outside the scope of our support.
If this solution is not relevant to your situation, because it's outdated or not applicable to your case, we recommend opening a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please contact us in the WPML support forum.
Problema: Si estás experimentando dificultades para traducir diferentes tipos de menús en WordPress, incluyendo varios elementos del menú. Solución: Te recomendamos seguir esta guía para aprender a traducir diferentes tipos de menús en WordPress, utilizando WPML: https://wpml.org/documentation/getting-started-guide/translating-menus/.
Es posible que esta solución no sea relevante debido a que está desactualizada o no se aplica a tu caso. Si es así, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos relacionados en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins.
Problem: The client was able to translate most of the theme strings but had issues with some content not showing up. After re-translating the page or making a small change and updating, the content would appear. However, the client was unable to find and translate some strings on the homepage. Solution: We recommended the following steps to locate and translate the missing strings: 1. Navigate to WPML → String Translation. 2. Enable the option "Look for strings while pages are rendered". 3. Visit the page with the untranslated strings or refresh it. 4. Return to WPML → String Translation and check if the string has been registered. 5. If found, search for the strings in the table and translate them. For more detailed instructions, please refer to our documentation on Finding strings that don’t appear on the String Translation page.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we encourage you to open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please contact us in the WPML support forum.
Problem: The client reported that after using automatic translation, some content on the product pages, such as custom fields and images, was not translated, and some strings were not available for translation. Solution: 1. We advised the client to make custom fields translatable by following the guide at https://wpml.org/documentation/getting-started-guide/translating-custom-fields/. 2. We suggested enabling the "Show 'Multilingual Content Setup' meta box on post edit screen" option in WPML → Settings → Custom Fields Translation to manage custom fields settings directly when editing products. 3. We reminded the client to back up their database before making any changes. 4. We informed the client that media (attachments) set to be untranslatable in WPML → Settings → Post Types Translation would not appear in translations. To fix this, the client should adjust the setting, slightly modify the original product, save it, and then save the translation in the WPML translation editor.
If the provided solution does not apply to your case, or if it's outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us in the WPML support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with automatic translation after duplicating a website and deactivating two languages. They encountered a connection error when accessing 'Tools' for automatic translation and were unable to translate content from English to Slovenian. Solution: 1. We asked the client to provide a screenshot of the error message "There is a problem connecting to automatic translation." 2. We recommended deactivating all plugins except for WPML to see if the issue persists. 3. If the problem remained, we instructed the client to navigate to WPML → Support → Advanced Translation Editor > Error Log and send us a screenshot for further analysis. 4. We created a new support ticket specifically for the issue of translating pages from English to Slovenian to assist the client and help others with similar problems.
Please note that the solution provided might be outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.
