Problem: You have translated some theme strings using WPML, but they are not appearing on the frontend of your site in the respective languages. Solution: First, ensure that you are translating the correct strings. We recommend activating the option 'Look for strings while pages are rendered' to help identify and register the correct strings for translation. Here are the steps you should follow: - Go to WPML → String Translation - Enable the 'Look for strings while pages are rendered' option - Open the page where the untranslated strings are displayed - Return to WPML → String Translation and check if the string has been registered - Proceed with the translation For more detailed guidance, visit finding strings that don't appear on the string translation page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues where strings are not rendering correctly in WPML, even though they work fine on other sites. You are also looking to export specific strings from one site and import them into another. Solution: We recommend using PO files to manage your string translations. To export your current translations, navigate to WPML → String Translation. If you are exporting strings without translations, save the file with a .pot extension (Portable Object Template). If you include translations, use the .po extension. When importing translations to another site, ensure you select the appropriate language for the translations. For detailed guidance, visit WPML String Translation documentation.
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 open a new support ticket at WPML support forum.
Problem: The client is experiencing slow saving times in the WordPress dashboard when editing slugs with Yoast SEO, with saving operations taking up to 4 minutes. Solution: We recommend trying the workaround provided in the WPML errata for backend slowness and duplicated queries. You can find the details here: WPML Backend Slowness Workaround. After applying the workaround, please test the saving speed while other plugins are deactivated to ensure that no other plugins are affecting the performance.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend 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. If the problem persists, please open a new support ticket at WPML Support Forum for further assistance.
Problem: The client is experiencing slow loading and saving times for pages and posts after installing WPML, along with technical errors reported by WordPress.
Solution: We recommend trying the minimum environment procedure to identify if the issue is due to a conflict with the theme or another plugin. Here are the steps: 1. Switch to a default WordPress theme, such as TwentyTwenty-Four. 2. Deactivate all plugins except for WPML and its add-ons. 3. Check if the problem persists. If it does not, reactivate the plugins one by one to identify the problematic plugin.
It's crucial to make a full site backup before proceeding with these steps. If your site is live, consider performing these tests in a staging environment.
If the issue persists even when WPML is deactivated, it suggests that the problem might not be with WPML. In this case, enable WordPress's debug log to gather more information about the errors. You can enable debugging by modifying your wp-config.php file:
After enabling debugging, reproduce the actions causing the slowness and check the debug.log file in the /wp-content/ directory for errors.
If these steps do not resolve the 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 with us for further assistance.
Problem: The client wants to change the language code for Chinese simplified and Portuguese Portugal without affecting the existing content Solution: We recommend creating a new custom language with the desired language code instead of changing the existing one, as altering the language code directly in the database could break your site. For Chinese, you can create a language with the code 'ZH'. Please refer to our documentation on editing WPML's languages table and watch this helpful video: video guide. For the existing translated content in 'zh-hans' or 'pt-pt', you can duplicate them in bulk to the new languages using the WPML Translation Management Dashboard. For more details, check out how to duplicate pages and posts in bulk.
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 you still need assistance, please open a new support ticket.
Problem: The client needed to update WPML on a new domain and edit the site key after moving their installation from redfoxlotto.eu to redfoxlotto.org. Solution: 1. We instructed the client to create a new key by visiting https://wpml.org/account/sites. 2. We guided the client to add the new key by navigating to Plugins > Add new > Commercial, then un-registering WPML from the old key and re-registering WPML with the new key.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we recommend opening a new support ticket. We also highly suggest 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.
