Problem: The client is experiencing an issue where attempting to validate the Litespeed extension with QUIC.cloud results in a 404 error page when WPML is activated. This problem persists even after resaving permalinks with WPML deactivated, indicating a potential redirect issue caused by WPML. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Deactivate WPML and connect to the Litespeed Cloud. If successful, reactivate WPML and check if the issue reoccurs. 2. If the problem persists, create a sandbox site with a fresh WordPress, WPML, and Litespeed installation to verify if the issue is specific to the client's current site setup. 3. Consult with the hosting providers to check for any server-side configurations, firewall rules, or security directives that might be causing the redirect issue. Additionally, reviewing server logs may provide further insights into the problem.
If these steps do not resolve the issue or if the solution 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing a 404 error when trying to link the Litespeed extension with QUIC.cloud, caused by WPML redirecting the request to an error page. Solution: We initially tested the process without WPML activated and encountered a similar issue, indicating that the problem might not be solely related to WPML. After reactivating WPML and resaving the permalinks, the connection to QUIC.cloud was successful. We recommend the client to: 1. Deactivate WPML temporarily to check if the issue persists. 2. Resave the permalinks in WordPress, which can often resolve incorrect routing issues. 3. Reactivate WPML and test the connection to QUIC.cloud again.
If this solution does not resolve the issue or 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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to separate languages for different countries on your WordPress site using WPML, similar to the language switch on the Logitech website, and want to have specific domains like .ch for Switzerland and .fr for France. Solution: First, you need to add custom languages to your WPML setup. You can do this by following the documentation here: Editing WPML's Languages Table. After setting up the custom languages, you should create a custom language switcher to accommodate the separate languages and countries. Guidance for creating a custom language switcher can be found here: Custom Language Switcher. Please note that creating custom solutions might fall outside our standard support service.
If this solution does not fully resolve your issue or seems outdated, we 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.
Problem: You are building a website using Bricksbuilder and Bricksforge to create a form with Pro Form, but you are unable to translate the form fields as they do not appear in the translation interface and remain in English. Solution: Since Bricksforge has not yet been tested for compatibility with WPML, we recommend trying to replicate the issue on a test site we have created for you. In the meantime, you can manually translate the page without using the Advanced Translation Editor by following the steps described here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/ Additionally, consider using one of the form plugins that are fully compatible with WPML, which you can find here: https://wpml.org/plugin-functionality/form/
If this solution does not apply to your case, or if it becomes 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. If you still need assistance, please open a new support ticket.
Problem: The client is using a custom field from ACF (True / False) for Pages to define if the header of Bricksbuilder is an overlay or a standard header. The CSS code is set to change styles based on the 'True' value. However, when translated to French, 'True' becomes 'Vrai', causing the CSS not to apply correctly. Solution: We recommend checking the 'True' string in WPML → String Translation. Search for 'True', and if found, copy the original value into the translation field and save it. This action should prevent the translation of 'True' to 'Vrai' and maintain the correct functionality of your CSS.
If the problem persists, please provide more details about how you are using this ACF field in your template or code, how you output its value, and when and where the problem occurs. Uploading relevant screenshots could also help us better understand and address the issue.
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 issue persists, we encourage you to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the homepage using the Advanced Translation Editor and notice unrelated text appearing, including dummy content.
Solution: This issue is related to the Bricks builder where orphaned content may not be deleted properly. We recommend checking the following documentation on known issues with Bricks builder regarding orphaned elements: Bricks Builder Known Issues. This problem is expected to be resolved in the next release of the builder.
If this solution does not apply to your case, or if it seems outdated, please open 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. For further assistance, you can contact us directly through our support forum.
Problem: The client needs help customizing the WPML language switcher dropdown to match a specific style shown in an example image, but only found a troubleshooting guide and not a tutorial. Solution: We recommend following these steps to customize your WPML language switcher dropdown: 1. Navigate to WPML >> Languages >> Menu Language Switcher. 2. Edit the language switcher settings to choose a similar option as shown in the example. 3. To achieve the same arrow and border style, copy the CSS from the Twenty Sixteen theme. For more detailed guidance on styling issues, please refer to our documentation: How to fix styling and CSS issues for the language switchers.
If this solution does not fully resolve your issue or 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to create a staging website using WPvivid and encountered an issue where WPML was not activated on the staging site. They were concerned about how the choice between 'This is only a copy' and 'I changed the address of the site to this new one' would affect the WPML license on the live site. Solution: We advised the client to re-register WPML after every website migration or domain change. Here are the steps to follow: 1. Visit https://wpml.org/de/account/websites/ 2. If the site URL is already registered, delete it from the list. 3. Enter the site URL again to create a new site key. 4. Click on "Show key" and copy it. 5. Enter the key under Plugins > Install > Commercial (tab) to re-register WPML. If WPML is still registered, de-register it first. If you do not register WPML with a valid site key, you might not be able to use the Advanced Translation Editor and will not receive automatic updates. Your Multilingual CMS account allows you to register 3 production sites and 9 development sites. Please read this guide for more details: https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/#what-are-production-and-development-websites
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is attempting to create a staging site for a multi-lingual website using WPML with the WPvivid backup plugin. However, they encountered an issue where WPML was not activated on the staging site created with WPvivid Pro version, although it worked with the free version. Solution: We have escalated the issue to our compatibility team to discuss with the plugin author about the compatibility of the WPvivid Pro version with WPML. In the meantime, we recommend using the free version of WPvivid for creating the staging site. Please keep an eye on the related compatibility page for any updates: https://wpml.org/plugin/wpvivid-backup-plugin/.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
