Problem: The client is experiencing an issue where footer translations in a multilingual WordPress site using WPML revert to the source language in the admin area after updates, despite displaying correctly on the front-end. Solution: 1. **Scan your theme for strings**: Ensure WPML has scanned the 'Bootstrap Basic New' theme for all translatable strings. * Go to WPML → Theme and plugins localization. * Under the Strings in the themes section, select your Bootstrap Basic New theme. * Click the Scan selected components for strings button.
2. **Check for your footer text in String Translation**: After scanning, search for your footer text. * Go to WPML → String Translation. * Search for a unique part of your footer text. * If found, ensure the translation is correctly entered and marked as Translation complete.
3. **If not found, check Admin Texts Translation**: Footer content might be in theme options, considered 'admin texts'. * On the WPML → String Translation page, scroll down and click the Admin Texts Translation link. * Look for your footer text under theme or customizer settings, select it, and click Add to String Translation. * Search again in String Translation, enter the translation, and mark it as Translation complete.
4. **Clear Caches**: Clear any caching plugins or server-level caching.
If these steps do not resolve the issue, or if the solution seems 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 the problem persists, please open a new support ticket for personalized assistance at WPML support forum.
Problem: If you're experiencing issues with WPML not automatically translating content when clicking the + sign to create a German version, it might be due to the settings or the need for an update. Solution: We recommend updating the page in the original language first. Once updated, WPML should automatically translate the content if 'Translate Everything Automatically' mode is enabled. Alternatively, you can manually send the page for automatic translation from the WPML → Translation Dashboard.
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 issue persists, please open a new support ticket.
Problem: The client was experiencing an issue where the WPML installer was stuck in a loop during installation on their staging environment. Solution: We resolved the issue by taking the following steps: 1. We removed the existing copies of the WPML plugins. 2. We uploaded freshly downloaded versions of the WPML plugins. 3. We accessed the database and deleted the problematic option in the
wp_options
table named auto-translation-job-creation-error. After these steps, we successfully activated the WPML plugins on the staging site.
Please note that this solution might be outdated or not applicable to your specific case. 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 issue persists, please open a new support ticket.
Problem: You are managing a large number of string translations (over 29,000 records) on your site and are unsure how to handle or reduce them. You are also concerned about the effects of deleting strings that are fully or partly translated. Solution: To manage or reduce the number of string translation records, we recommend the following steps: 1. Turn off auto-registration of strings in WPML -> String Translation -> Utilities to prevent unnecessary accumulation of new strings. 2. Use the "Cleanup and optimize string tables" and "Clear invalid strings" options in WPML -> Troubleshooting to clean up your database. 3. Manually check for unnecessary strings in the String Translation section and delete them, especially those that are not translated. You can filter strings by text-domain and remove them in bulk if they are not needed.
Please ensure you have a full backup of your website and database before making any changes. It is highly advised to perform these actions on a staging or development site first.
If you decide to delete strings, be aware that this action will also remove their translations. This will affect only the translations of the specific strings you delete.
If the solution provided here 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 needed, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an Error 500 when trying to edit the Dutch homepage of their site. This issue is linked to a PHP memory limit being exhausted, as indicated by the error log showing a fatal error in
wp-includes/meta.php
. Solution: We recommend increasing the PHP memory limit. You should contact your hosting provider to request an increase of the PHP memory limit to 512MB. Concurrently, adjust the WordPress memory limit to 512MB in your
wp-config.php
file. This adjustment should help resolve the Error 500. If the issue persists, consider disabling other plugins temporarily to reduce memory usage, allowing you to edit the homepage.
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 continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with the menu structure not being translated, even though the settings are on automatic. Solution: If you're experiencing this issue with your menu not being translated, we recommend that you manually translate the custom menu items. You can do this in WPML -> Strings Translation. For detailed guidance, please refer to our documentation on Translating Menus. Additionally, we have manually edited the English and German menus to correct this issue. It's important to manually translate the menus when using custom items, especially when adding relative links instead of full links. Note that the 'TH Advance Search bar' option should only exist in Dutch.
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 open a new support ticket at WPML support forum.
