Problem: After migrating a website and changing its URL, the client faced issues with WPML registration and visibility of translations on the frontend, despite being able to edit and save them in the backend. Solution: 1. We recommended temporarily disabling the firewall to allow changes to be saved and to ensure connectivity with WPML services. 2. We suggested adding specific code to the theme's functions.php to test server connectivity with WPML's services:
3. To further diagnose connectivity issues, we advised using cURL to test access to external URLs, including a specific WPML URL, with the following code:
4. After making the main changes, the client planned to re-enable the firewall and whitelist IPs associated with the domain names, expecting them to be static.
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 problems persist, please open a new support ticket.
Problem: You are trying to register your website with WPML but are unable to do so because the site key does not match. Additionally, there is a connection error indicated in the 'Advanced Translation Editor Error Logs' showing a cURL error, suggesting that WPML cannot connect to its servers.
Solution: First, ensure that there are no security modules on your website that might be blocking requests. You may need to whitelist the following domains with your hosting provider:
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 needed, please open a new support ticket at WPML support forum.
Problem: The client wants to test the 'fallback function' for displaying untranslated content in secondary languages using the default language as a fallback, and is concerned about whether they can revert the settings back to the original state without any residual changes. Solution: We assure the client that they can safely test the fallback function without risking permanent changes to their website. This function is ideal if the client has content that is not yet translated and prefers to show content in the default language temporarily rather than showing nothing. The settings for this function can be easily switched back and forth without any risk of losing data or leaving residual settings. Once a translation for a page becomes available, WPML will automatically display the translated content instead of the fallback.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to continue translating strings after moving their site to a new URL and selecting the option in WPML to treat it as a new location. They were concerned whether the local hosts file was causing the issue and whether it would resolve itself after updating the DNS. Solution: We advised the client to mark the site as a copy using the option provided in WPML, which would allow them to access the Advanced Translation Editor and continue making translations. This step is detailed in the documentation on handling site moves with WPML, which can be found here: Using Advanced Translation Editor when you move or use a copy of your site.
If this solution does not apply or is outdated, or if further issues arise, 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 these steps not resolve the issue, please do not hesitate to open a new support ticket with us for personalized assistance.
