Problem: The client encountered a WPML message in their WordPress dashboard asking if their main site laspeziaguide.com is a duplicate of a non-existent domain wpml.wpml.laspeziaguide.com. This message was confusing as the domain mentioned does not exist and the client had not recently created a staging site with that URL. Solution: We determined that the message was not generated by WPML but possibly by other plugins (Admin Site Enhancements or Unlimited Elements for Elementor) that check for a license. The client should verify which plugin generated the notice by following any available links in the message for more information. If the issue persists, the client should contact the support for those plugins. Additionally, we resolved the issue from our side by adjusting the organization IDs and merging them in our system, ensuring the client can continue using the Pay as you go system for translations. To prevent future issues, follow the steps outlined in the WPML documentation on handling site copies: Using Advanced Translation Editor when you move or use a copy of your site.
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. If issues persist, please open a new support ticket.
Problem: You are experiencing issues with symbols being incorrectly inserted in Italian translations using WPML, such as unnecessary spaces and quotation marks instead of apostrophes. This problem is attributed to the translation engines, particularly Deepl, which interprets these insertions as correct grammar. Solution: We recommend using Microsoft or WPML AI for translations as these engines do not frequently exhibit this issue. We are actively working to improve our systems to gain more control over translation outputs. In the meantime, if possible, manually correct the errors in the translated content. Additionally, we have added 3000 credits to your site for testing purposes. If the problem persists, please provide temporary access (wp-admin and FTP) to your site for further investigation. Ensure to back up your site files and database before providing access, and verify that you are using the private fields for submitting sensitive information. For more details on privacy and security, please visit: Privacy and Security Policy.
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 necessary, please open a new support ticket for further assistance.
Problem: If you're experiencing issues with the primary category not being correctly represented in the Language Switcher for Spanish URLs, leading to incorrect URL structures on page load, particularly after updating to version 4.7.4, this might be due to a compatibility issue with the Only Top Category option of the Grid Post widget from the Unlimited Elements for Elementor (Premium) plugin.
Solution: First, we recommend replicating the issue on a clean installation to confirm it's a compatibility issue. Here are the steps: 1. Install Unlimited Elements for Elementor (Premium) on a clean WordPress installation with Elementor, Yoast, WPML, and all necessary WPML add-ons. 2. Create the same situation and try to replicate the issue.
Additionally, there is a workaround provided by our compatibility team: 1. Open the file
function on line 574. 3. Replace the existing code with the new code provided, which includes a WPML filter to ensure the primary category ID is correctly translated. 4. Clear Elementor's cache by going to "Elementor > Tools > Clear Files & Data" and ensure the translation is 100% complete.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
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.
