Problem: The client reported that their homepage only displayed in English despite having translated the site into four languages using WPML. Additionally, they encountered an issue where the logo disappeared when navigating to a translated page. Solution: 1. We identified that redirections were causing the German and Portuguese versions of the homepage not to display. We recommended checking and adjusting these redirections and ensuring that all translations are published. 2. To address the site's performance and possibly related issues, we advised increasing the WordPress memory limit. This can be done by adding the following line to the wp-config.php file:
This line should be placed above the 'That's all, stop editing! Happy blogging.' line. Further verification of the WordPress memory limit can be done through WPML -> Support. 3. Regarding the disappearing logo on translated pages, we needed further investigation into the site's configuration. We requested access credentials to examine the settings more closely and asked the client to describe how they edit the logo.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client wanted to mask the name of the cookie 'wp-wpml_current_language' used by WPML to enhance security by hiding the use of WordPress. Solution: If you're experiencing this issue and want to rename the WPML cookie to hide the use of WordPress, you have two options: 1. If you do not need to propagate the current language to anonymous AJAX requests, you can disable the cookie in WPML > Languages. For more details, please see our documentation on Enabling language cookie to support AJAX filtering. 2. Alternatively, you can modify the cookie name directly in the plugin files. However, this is considered custom work and falls outside our support policy. You will need to maintain this custom code yourself and reapply it after each WPML update.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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. For further assistance, you can reach out to us on the WPML support forum.
