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 with us for further assistance.
Problem: You are trying to translate content on your site using WPML and encounter an error where everything appears blue, but it still shows 99% done for each language. Solution: We recommend you go to the translation editor and from the top right section click the Settings icon. Enable the previous version of the translation editor and click save. Then, please refresh the page and make sure everything is completed.
If this solution does not resolve your issue, or if it 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is migrating their website from an old WordPress environment using Elementor Builder to a new one using Oxygen Builder, and they are facing issues with importing content in multiple languages using the WPML import-export plugin. Additionally, they are encountering compatibility issues with the Oxygen Builder when translating pages. Solution: 1. Use the WPML Export & Import plugin for migrating content between environments. Ensure to use the same export and import method for consistency. Follow the detailed guide here: WPML Export & Import documentation. 2. For taxonomy issues during import, refer to: Reconnecting taxonomy translations. 3. If using Oxygen Builder, note that it is not fully compatible with WPML. Translations might need to be done manually using the WordPress Editor. Set Oxygen Templates in WPML settings to "Translatable - or fallback to default language if a translation is not available" to avoid issues. For more details, visit: Using different translation editors and Oxygen compatibility issues. 4. For specific template translation issues with Oxygen, consider the workaround provided by the Oxygen team: Oxygen template translation workaround.
If these solutions do not resolve your issues or if they seem outdated, we recommend opening a new support ticket. We also advise checking related known issues at WPML known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum: WPML support forum.
Problem: The client is building a new website and wants to use WPML again but is facing issues with the site key not working on the new WordPress. They are also inquiring about transferring existing translations to the new website without additional costs. Solution: If you're experiencing issues with your site key on a new WordPress installation, it's important to note that site keys are domain-specific. You will need to generate a new site key for your new site. If you continue to face issues, we recommend contacting us with the site link for further assistance. Regarding the transfer of existing translations, translations cannot be transferred alone. You must transfer the default content along with their associated translations to ensure proper connection. You can use the default WordPress exporter/importer or WP All Export/Import tools. Additionally, make sure to use the WPML Export/Import addon on both sites. For more details, please refer to our guide: WPML Export and Import.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 further assistance is needed, please feel free to open a new support ticket.
Problem: The client reported an intermittent issue where the toggle to change pricing from monthly to yearly breaks on the Spanish version of their page. This issue does not occur consistently but appears sporadically, making it difficult to diagnose. The client mentioned that all plugins are up to date according to their WordPress dashboard. Solution: We suggested that the issue might be related to a caching or performance optimization plugin, or a compatibility issue with WPML and another active plugin or theme. We recommended the following steps: 1. Create a full website backup. 2. Disable all plugins except for WPML and its add-ons. 3. Check if the issue still occurs. 4. If the issue does not occur, reactivate the plugins one by one to identify the problematic plugin. 5. If the issue persists with only WPML plugins active, switch to a default WordPress theme like TwentySeventeen and check again. We also advised performing these tests in a staging environment if possible and ensuring that all plugins, especially WPML, are updated to the latest versions by checking for updates in the 'Commercial' tab under 'Plugins > Add new'.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 at WPML support forum.
Problem: The client has custom HTML added to their blog for an author box, which is not translating in the Advanced Translation Editor (ATE).
Solution: Firstly, we advised the client that it is not necessary to include meta tags and font links within the custom HTML block, as WordPress adds this information to the site. Instead, we recommended enqueuing the fonts file in the functions.php file of the child theme and adding CSS rules to the style.css file of the child theme.
We then instructed the client to simplify the custom HTML block to only include the necessary divs and paragraphs, which will allow the strings to be automatically translated in the ATE. The client should remove unnecessary HTML tags and structure, leaving only the content that needs translation.
If this solution does not apply to your case, or if it seems outdated, 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 our support forum.
Problem: The client has translated their categories but the URLs are not translated as desired. The issue is that the translated category slugs are appending a language code at the end, which the client wants to remove.
Solution: We explained that WordPress requires each taxonomy term's slug to be globally unique, which means one taxonomy term cannot have a matching slug with another taxonomy term across all taxonomies. To allow for duplicate slugs in different languages, we recommended checking out a post that provides a solution for allowing duplicate taxonomy slugs in WordPress. Here is the link to the post: https://stackoverflow.com/questions/12806409/allow-duplicate-taxonomy-slugs-wordpress
Please note that the solution provided might be outdated or not applicable to your case. If after checking the known issues and confirming that you have the latest versions of themes and plugins installed, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
Problem: The client has translated their pricing page, but the FAQ section did not translate along with it. Even after manually translating the content in Elementor, it reverted back to the default language. Additionally, the advanced translator did not show the text. Solution: 1. We recommended installing the Multilingual Tools Plugin. 2. We identified a server permission issue that prevented the installation of the plugin, which was indicated by the error message "Could not create directory. /var/www/html/wp-content/plugins/multilingual-1/". 3. After resolving the server permission issue, we added the correct custom XML configuration for Elementor, which should allow the client to translate the content properly. 4. We provided a link to the page where the client can translate the contents using the options in the sidebar: WPML Compatibility Test Tools Plugin.
If this solution doesn't look relevant, please open a new support ticket in the WPML support forum.
Problem: The client was experiencing issues with some pages still opening in the Classic Translation Editor instead of the Advanced Translation Editor after switching back to the Advanced Translation Editor in the settings. Solution: 1. We accessed the WPML settings. 2. We changed the option under WPML --> Settings --> Editor for translations previously created using Classic Translation Editor from "Classic Translation Editor (recommended)" to "Advanced Translation Editor". 3. We advised the client to delete any translation jobs that were in progress with the Classic Translation Editor from WPML --> Translation Management --> Jobs. 4. We provided a video tutorial for further assistance: https://komododecks.com/recordings/Mx0Gt88nPAgGvmfj0QDO.
