Problem:
The client was experiencing issues with caching and had questions about migrating to a new server with WPML, including updating the domain and preserving WPML settings.
Solution:
1. We suggested that the issue might be related to caching settings or a caching plugin, not WPML directly. If WPML is uninstalled and reinstalled, settings remain since they are saved in the database. A WPML reset would remove all settings.
2. To disable Language Switcher caching, navigate to WPML > Support > Troubleshooting and use the provided option.
3. After migrating to a new domain, remove the old key and generate a new key for the production domain at WPML.org > Account > Sites. Then, register WPML with the new key in the website backend.
4. To migrate the site, we recommended using the Duplicator plugin, which handles URL replacement and preserves WPML settings. Documentation for Duplicator can be found at https://snapcreek.com/duplicator/docs/.
5. Clearing WPML cache is only necessary when caching issues are suspected. There is no cron job for this; it must be done manually in WPML > Support > Troubleshooting.
6. We are not aware of any unique setup required for WPML when configuring the LSCACHE plugin.
7. If the client needs to update the pre-prod environment to remove a notice, they should open a new ticket closer to the migration date.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also 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.
