Problem: If you're experiencing issues with WPML String Translation on WordPress VIP, where WPML is trying to write .mo files to the non-writable /var/www/wp-content/languages directory, thus blocking translations from appearing on your site, we have a workaround for you. Solution: First, please check our documentation on handling issues with WordPress VIP hosting at https://wpml.org/errata/wordpress-vip-hosting/. If the error message is still visible and causing issues, you can add the following CSS code to hide it:
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 persists, please open a new support ticket.
Problem: You are trying to register WPML in a local development environment using Docker containers for nginx, PHP, MySQL, etc., but encounter an error stating that the site key doesn't match. Solution: If you're experiencing this issue, it's likely because the URL of your local environment differs from the one registered with the site key. We recommend obtaining a new site key for the new URL. You can follow the instructions here to re-register: How to re-register a site key for a new URL. Additionally, consider using the automatic WPML registration feature, which might be more suitable for your setup. Details can be found here: Automatic WPML Registration Using PHP.
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.
