Problem: The client's high-traffic corporate website experienced a downtime due to an unexpected traffic spike, with potential issues related to WPML observed in the SQL query logs. It was unclear whether the problem stemmed from WPML or another plugin affecting WPML’s performance. Solution: We recommended increasing the WordPress memory limit to at least 256 MB as WPML requires a minimum of 128 MB. The client was advised to add the following code to the wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
just before the comment:
// That's all, stop editing! Happy blogging.
Additionally, we suggested ensuring all themes, plugins, and WordPress itself are updated to their latest versions to avoid bugs or performance issues. We also recommended checking for any conflicts by switching to a default WordPress theme and deactivating all plugins except WPML and its add-ons and Elementor. If the problem persisted, the client was to activate plugins one by one to identify the problematic plugin. For further details on managing translations and optimizing WPML with caching, we provided links to our documentation:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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.
Problem: You need to configure the WPML language switcher to redirect users between two separate WordPress domains (glginsights.com and glginc.cn) based on the selected language, while maintaining consistent permalinks. Solution: We recommend implementing a custom redirect using the
wpml_language_has_switched
hook. This hook activates after WPML switches the language context, allowing you to redirect users to the corresponding page on the other domain. Here is a basic example of how you can set this up:
Ensure that both domains use matching permalinks and slugs, and adjust the language codes to match your WPML configuration. This solution is custom and may require further adjustments based on your specific setup.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After migrating a production site to a staging site using Updraftplus, the client encountered an error indicating that the table 'wp_glg_stage.wp_icl_strings' does not exist. They also inquired about the specific process to follow when migrating WPML with Updraftplus. Solution: If you're experiencing a similar issue after migration, we recommend trying the following steps: 1. Attempt to remove the warning message by clicking the small 'x' icon on the message. 2. Refresh the dashboard to check if the warning message persists. If the message disappears, then everything should be in order. However, if the issue persists, it might indicate a deeper problem. For more detailed information, please refer to our documentation on how to deal with error messages about a broken table that needs fixing: WPML Documentation on Database Errors.
Please note that this solution might be irrelevant if it's 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 an issue where a warning box appears when editing a page using Elementor, and they want to make WordPress Editor the default editor instead. Solution: To disable the WPML Editor and make WordPress Editor the default, follow these steps: 1. Edit a post/page in the original language. 2. Go to the right column and find the Language block. 3. Click on WordPress Editor. 4. In the popup window, select the scope of the change to 'All Site Content' and save the changes. This will apply the WordPress Editor for future edits, but it will not affect existing translations. For detailed guidance, refer to the documentation here: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please contact us through the WPML support forum.
