Problem: You are using GoDaddy's managed hosting and encountering a 'cURL error 28: Failed to connect to api.wpml.org port 443 after 10001 ms: Timeout was reached' when trying to register with WPML's automatic installer. Solution: 1. This error typically indicates that your server is unable to reach our API (api.wpml.org) within the allowed time. It might be due to a temporary slowdown between your server and WPML.org. Please try registering again to see if the issue persists. 2. If the problem continues, ask GoDaddy to allow outbound requests to https://api.wpml.org. You may need to temporarily disable any CDN or security layers and ask GoDaddy to specifically whitelist api.wpml.org.
If these steps do not resolve the issue, or if the solution seems 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client was unable to translate certain elements on their website, such as reservation form fields and the 'Call us' button, even after attempting to use WPML's String Translation. The site was offline, which limited troubleshooting options. Solution: We recommended the following steps: 1. Ensure the site is online to proceed with troubleshooting. 2. Navigate to WPML → Theme and plugins localization. 3. Select the active theme and any plugins related to the reservation form or footer content. 4. Click on Scan selected components for strings button. 5. After scanning, search for the untranslated texts in WPML → String Translation. If these steps do not resolve the issue, it might be due to the strings not being registered or hardcoded in the theme or plugins. In such cases, contacting the theme or plugin author might be necessary to make the strings translatable.
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 at WPML support forum.
