Problem: The client reported that two of their multilingual URLs set up using WPML on their WordPress site suddenly became non-functional, displaying an 'SSL handshake failed Error code 525'. However, one URL remained operational. Despite the SSL certificates passing tests on ssllabs.com, the issue persisted. Solution: We analyzed the situation and determined that the issue was not related to WPML. The 'SSL handshake failed' error indicates that Cloudflare could not establish a secure connection with the origin server. We recommended: 1. Verifying that the origin server has a valid SSL certificate installed and is correctly configured to serve HTTPS traffic. 2. Ensuring that the SSL/TLS settings in Cloudflare match the setup on the server (e.g., Full vs. Full (Strict)). 3. Contacting Cloudflare support for further assistance to identify where the connection is failing.
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. Additionally, if further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using WPML for translations on your development site. After translating a page, you need to partially modify the text and change the picture, but changes are not reflected after saving. Solution: First, ensure that any active local/server caching is cleared as it might be preventing the changes from showing up. Here are the steps you can follow: 1. Navigate to WPML > Media to check if the image is already translated. You might be able to change the translated version of the image there. 2. Switch the language from the top bar while in the backend of the site, go to Pages, find the translated version of the page, hover your mouse over it, and try to edit it with the page builder used in the default language.
If these steps do not resolve your 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 at WPML support forum for further assistance.
Problem: The client is working on a site under development and needs to register the WPML key to the website. Additionally, the WPML plugin cannot connect to wpml.org, which is necessary for checking new releases and security updates. Solution: To register the WPML key: 1. Ensure you are logged into wpml.org. 2. Navigate to WordPress Dashboard > Plugins > Add New > Commercial (Tab). 3. Click on "Register WPML" at the right section of the screen. 4. Click on "Get a key for this site". A new page will open, and the auto-generated key will appear. 5. Copy the key and paste it into the "Site Key" input box. 6. Click the "OK" button. For more information, visit https://wpml.org/faq/install-wpml/#register
For the connection issue: 1. Contact your hosting service provider and request them to whitelist the following URLs: - wpml.org - cdn.wpml.org - api.wpml.org - api.toolset.com - cloudfront.net For more details, visit https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/
Regarding plugin installation, the client does not need to install all plugins shown. Essential ones include WPML String Translation and WPML Multilingual CMS.
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 for further assistance.
Problem: The client is developing a site and wants to add the Danish language. They encountered issues where 'Validate on save' shows 'Not valid', and the backend won't open after attempting to deactivate WPML. Solution: First, ensure that the subdomain for the Danish language points correctly to the root folder. This involves configuring the DNS settings. You can find detailed instructions on how to do this here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/#2-configure-the-dns-settings. Once the DNS settings are correctly configured, try to validate the site again. If the problem persists or the solution provided here is not applicable due to being outdated or not matching your case, we recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also contact our support team directly at the WPML support forum.
