Problem: The client is experiencing poor PageSpeed results for the English version of their multilingual website, while the Hebrew version shows good performance. Solution: We noticed that the Chat VS widget, which loads on the Hebrew site, does not appear on the English site. This could potentially cause loading issues. Additionally, the client might need a separate license for each domain to ensure optimal caching with WP Rocket, as per their support comment from 2019. WP Rocket's compatibility with WPML Here are further steps to improve performance: 1. Disable "display as translated" in WPML > Settings. 2. Turn off "Adjust IDs for multilingual functionality" at WPML > Languages. 3. Disable “Track where strings appear on the site” in String Translation. 4. On the WPML->Support-> troubleshooting page, run:
Cleanup and optimize string tables
Clear invalid strings
Remove ghost entries from WPML tables
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You need to restrict admins and editors to a specific language in WPML, but cannot find a built-in solution. Solution: While WPML does not provide a direct feature for this, you can achieve it by using user roles and capabilities. We recommend using a role management plugin like Members or User Role Editor. Here’s how you can set it up: 1. Install a role management plugin. 2. Create custom roles and define capabilities that restrict access to specific languages. 3. Assign these roles to your admins and editors. This setup requires custom work, which is outside our standard support scope, but we hope this guidance helps you move forward.
If this solution does not apply to your case, or if it becomes 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 was experiencing a 404 error when trying to access a translated post on a website using a toolset plugin with a custom post type. Despite trying to save the permalinks in the settings, the issue persisted. Solution: We discovered that the issue was due to incorrect slug settings in the 'WPML settings' page, which added an extra '/he/' to the URL. We recommended the client to remove this erroneous part from the URL settings. After making this adjustment, the website began to function normally.
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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
