Problem: The client is experiencing issues with URLs and an image in the sidebar slider not translating correctly after updating WPML and Elementor. The URLs used to appear in the Advanced Translation Editor (ATE) and the image used to translate both the URL and the image itself. The client has added XML for other translations but is unsure if the same approach can be applied to the sidebar image and URL, which are managed via String Translation. Solution: We recommend translating the strings associated with the sidebar image and URL in the 'widgets' text-domain. This should resolve the issue with the translations not appearing correctly on the frontend. If you're experiencing this issue, ensure that you translate both the URL and the image source strings.
Please note that this solution might be outdated or not applicable to your specific case. We 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 the problem persists, please open a new support ticket.
Problem: You are updating posts and adding new content but have noticed that images with URLs are no longer visible in the Advanced Translation Editor (ATE) for URL translation. Although images are translated in Media Translation, their URLs remain in the primary language, and this issue does not affect older posts.
Solution: We recommend adding the following XML configuration to your WPML settings under the Custom XML tab to address this issue:
After applying this XML, you should be able to see the URLs correctly in the ATE. Please complete the translation of the post and verify if the URLs are translated correctly on the front end.
If this solution does not resolve your issue or seems outdated, we 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 the problem persists, please open a new support ticket.
Problem: You are trying to translate new listings and update translations of old listings, but the Advanced Translation Editor (ATE) is not loading. Instead, you see a spinning wheel with a message: 'Unable to retrieve job details.' Solution: We have confirmed that all systems related to the ATE are now functioning correctly. However, there might be a short delay as the system processes a backlog of accumulated jobs. We recommend trying to access the ATE again now. If you continue to experience issues, please check the related known issues and verify that you have installed the latest versions of WPML and its extensions. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: The client was experiencing an issue where a post appeared twice in the Advanced Translation Editor (ATE), leading to an incorrect calculation of translation credits. This duplication only affected the Spanish translation and was not visible on the front end. The client was concerned about being overcharged for translation credits due to this duplication. Solution: We investigated the issue and confirmed that the duplication was due to strings appearing under the wrapper tag twice. We suggested that the client delete the duplicate packages in WPML->Packages by locating the packages listed by the page ID and then deleting them. After making a small change in the default language page and updating it, the client should access the translation again to see if the issue persists. Additionally, we confirmed that the client was indeed overcharged and proceeded to refund the excess credits. For future translations, we recommended keeping an eye on new content to ensure this issue does not recur. If the problem persists or if this solution does not apply due to updates or different circumstances, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
Problem: After adding custom code to functions.php to populate post grids in a second language, the 'Intro' field from Unlimited Elements Post Grid is not translating correctly and is pulling data from the original language post. Solution: We recommend the following steps to address the issue: 1. Navigate to WPML > Settings and temporarily switch to the Classical Editor. 2. Complete the translations that were problematic. 3. Return to WPML > Settings and switch back to the Advanced Translation Editor (ATE). 4. Continue and finish translating the post.
If this solution does not resolve your issue or seems outdated, we highly recommend checking for 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. Should the problem persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You need to translate scripts within a post, such as iframes or shortcodes, for different languages. However, when using the Advanced Translation Editor (ATE), you encounter issues where the original language script appears blank and modifications in the new language do not save correctly. After editing and saving the post, scripts revert back to the original language. Solution: We recommend not using the ATE for pages that contain scripts you need to translate. Instead, use a different method to manage translations for these specific pages to avoid the issues you're experiencing. For detailed guidance on how to implement this, please refer to our documentation on using different translation editors for different pages: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is using the Unlimited Elements Post Grid in Elementor to display posts via Manual Selection. In the primary language, adding Post IDs or Post Names works correctly, but these do not display in the Advanced Translation Editor (ATE) for translation, causing no posts to display in the second language. Editing the post in the second language and adding Italian post IDs or Post Names works until the ATE is accessed again, after which the posts revert to English Post IDs or Titles. Solution: We recommend inserting the following custom PHP code into your theme's functions.php file to ensure that post IDs are correctly translated and maintained across language changes:
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, we 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 the problem persists, please open a new support ticket with us.
Problem: The client is experiencing an issue where unrelated SEO meta fields are appearing in the Advanced Translation Editor (ATE) when translating Elementor Templates. This happens specifically when a template is created from a section within a page or post, where SEO meta fields are included. Solution: 1. If you're experiencing this issue, first check if the SEO meta fields are necessary for your translation. If they are not, you can set them to 'Don't Translate' by following these steps: - Go to WPML > Settings and scroll to the Custom Field Translation section. - Click on Show System Fields. - Search for 'seopress' in the search box. - Set the translation preference for the fields you don’t want to see in the Translation Editor to 'Don’t Translate' and save the changes. 2. If the fields are appearing because they were included in a template created from a page or post, you can remove them directly in the Elementor editor before translating. For guidance on removing these fields, please refer to this guide.
If the solution provided here does not resolve your issue or seems irrelevant due to updates or differences in your case, we 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 open a new support ticket.
Utilizamos cookies para optimizar nuestro sitio web y nuestros servicios. Su consentimiento nos permite procesar datos como el comportamiento de navegación. No dar su consentimiento puede afectar a algunas funciones.
Funcional
Siempre activo
Necesario para que nuestro sitio web funcione y se comunique correctamente.
Preferencias
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Estadísticas
Las utilizamos para analizar las estadísticas de nuestro sitio. La información recopilada es totalmente anónima.El almacenamiento o acceso técnico que se utiliza exclusivamente con fines estadísticos anónimos. Sin una citación, el cumplimiento voluntario por parte de su proveedor de servicios de Internet, u otros registros de terceros, la información almacenada o recuperada solo para este propósito generalmente no puede usarse para identificarlo.
Marketing
Estas cookies rastrean su navegación para proporcionar anuncios relevantes para usted.
