Problem: The client is setting up a multi-domain and URL language switch for their site, with different domains and language folders for each language. Solution: We explained that it is not possible to mix different language formats; the client must choose either a domain per language for all languages or a directory for language mode. However, using subdomains like fr.houseofcufflinks.eu and de.houseofcufflinks.eu is feasible under the separate domain option. For detailed guidance on setting up different domains per language, we recommend visiting this documentation.
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 through the WPML support forum.
Problem: You are trying to send a field containing a form ID to Crowdin via WPML integration for translation, but the field does not appear in Crowdin's system nor in the source XLIFF file. However, using the WPML editor, both types of values (simple strings and form IDs) work without issues. Solution: We have adjusted the segmenter settings for your project. Please try to send another job to test and let us know if it works as expected.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket.
Problem: You are trying to access the German version of your site and encounter the error: net::ERR_CERT_COMMON_NAME_INVALID. This error typically indicates a mismatch between the domain name and the name listed on the SSL/TLS certificate. Solution: If you're running a multilingual website with WPML and using different domains for each language, you'll need to ensure that each domain has its own SSL certificate that correctly matches the domain name. This is essential to avoid common name mismatch errors.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client was experiencing an issue where an icon continuously rotated on the admin bar where the language icon appears. The client had deleted the "icl_background_task" table as suggested, which stopped the icon from appearing but raised concerns about the necessity of the table, potential impacts on the site, and whether the table might reappear.
Solution: We explained that the rotating icon is part of the WPML's "Translate Everything Automatically" mode, indicating background tasks updating content. To address the issue: 1. Ensure you have a full backup of your site. 2. If the icon reappears and is bothersome, you might consider disabling and then re-enabling the "Translate Everything Automatically" mode, which should recreate the "icl_background_task" table without needing to manually truncate it again.
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, please open a new support ticket.
Problem: You are trying to translate templates on your site using WPML and the newspaper theme. Although you have translated the Cloud library templates, they are not displaying correctly on the front end. Solution: We recommend checking the theme options for each language. Go to Newspaper > Theme Panel, switch the language in the top admin panel, and ensure that the correct header for the selected language, such as Polish, is active. This adjustment should resolve the display issue.
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 the WPML support forum.
Problem: You are trying to translate the Porto theme product filters to Bulgarian, specifically the 'by size' and 'by color' filters, and you want to correct the translation of the word 'by' which was incorrectly translated to 'по'. Solution:We have a workaround.
Go to WPML > String Translation and translate the new strings.
To correct the translation of the word 'by', you can adjust it directly in the WPML String Translation interface. Access it via this link: WPML String Translation.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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.
Problem: You want to add a different shipping class in translated products on your WooCommerce site, but the shipping class field is locked. Solution: In WooCommerce when integrated with WPML, product details including shipping classes are synchronized across translations. To have different shipping classes, you would need to create independent products for each language instead of translating them. Although there is an option to unlock specific fields at WPML > Settings > Custom Field Translation, we do not recommend altering these settings as it could lead to unexpected issues with how WooCommerce Multilingual & Multi-Currency functions.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client is developing a site and needs a separate payment gateway for each currency. The gateway is custom coded, and the client wants to make it compatible with WPML's multicurrency feature. Solution: We explained that any payment gateways set up in the Payments section of WooCommerce → Settings will be available for all site’s currencies. If the client wants to use different gateways with different settings for each currency, this is only compatible with a few gateways. For a custom-coded gateway, ensuring compatibility with WPML's multicurrency feature is not straightforward and requires complex compatibility collaboration with our developers. We recommend that if the client's plugin will be publicly available, they should consider joining our Go Global program to collaborate with our compatibility developers.
For more details on setting up payment gateways for each currency, please visit this documentation.
If this solution does not apply to your case, or if it 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.
Problem: The client is experiencing an issue where selecting the Spanish translation on a specific page redirects to the homepage instead of showing the Spanish translation. Additionally, there is confusion about why some links show as translated while others do not. Solution: 1. We recommend checking the page in an incognito window as it might display correctly. 2. The main menu, which includes parent menu items as Custom Links, needs translation. We advise translating the main menu and verifying the URLs. For guidance on translating menus, please refer to this documentation.
If this solution does not 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 the problem persists, please open a new support ticket.
Problem: If you're experiencing a conflict between the WPML plugin and the WordPress admin panel, where activating the plugin results in losing access to the admin panel while the website itself works correctly, this might be due to a PHP configuration issue. Solution: First, check your admin email for any full error log messages. If you don't find any, enable the debug log by following the instructions here: https://wpml.org/documentation/support/debugging-wpml/. After reproducing the issue, check the debug.log file in your ".../wp-content/" directory for a fatal error message. If you encounter an error like
, it indicates that the PHP eval() function is missing on your server. You can resolve this by contacting your hosting support to enable the PHP eval() function, which is required by WPML. For more details on WPML's minimum requirements, visit: https://wpml.org/home/minimum-requirements/.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket with us for further assistance: WPML Support Forum.
The client was experiencing an issue where the accordion widget displayed incorrect characters on the translated page on their website. Initially, the problem was resolved in two languages after updating the translation, but it persisted in the Catalan language.
Solution:
We recommended the following steps to address the issue: 1) Navigate to WPML>>Settings>>Custom Fields Translation. 2) Click on the Show systems fields link. 3) Search for the
*_eael_widget_elements*
field. 4) Set it as Copy and save the changes. 5) Open the page for editing in the original language and make a minor change to refresh the translation settings and update it. 6) Update the translation.
Additionally, to address the issue with the Catalan translation specifically: 1) Visit Essentials Addons>>Tools and click on the Regenerate Assets button. 2) Update the page and then update the translation.
If these steps do not resolve your 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: You are trying to display images on translated sites using WPML, but images are not displayed for new content in a specific taxonomy. Solution: We resolved this issue by ensuring that the custom fields associated with the images are set to "Copy" during the translation process. Here’s how you can do it: 1. Enable the option "Show 'Multilingual Content Setup' meta box on the post edit screen" in WPML → Settings → Custom Fields Translation. 2. Edit the portfolio post in the original language. 3. In the custom fields section, adjust the necessary custom field to "Copy". 4. Update the translation by making a slight modification to the original page, saving it, navigating to the WPML translation editor, and completing the translation. For subsequent items, you only need to follow step 4.
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, please open a new support ticket.
Problem: After deploying a staging site to live, you started receiving a message from WPML indicating a new address for the site. Solution: If you're experiencing this issue, we recommend re-registering your website with WPML. Here are the steps to follow: 1. Visit https://wpml.org/account/sites and remove your website from the list. 2. Add your website again and copy the newly generated key. 3. In your website's admin panel, navigate to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". 4. Register the website again using the key you copied in step #2.
This should resolve the message issue. If this solution does not apply to your case, or if it seems outdated, please check the 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client wants to maintain Dutch as the default language for backend operations and translations, while setting English as the primary language on the front end of the website. The client also wants the original URL to direct to the English version, with Dutch available in the language menu. Solution: We recommend two features to achieve this setup: 1. Change the display language of the Back End: You can change the display language in the backend by navigating to Users > Profile in your WordPress dashboard. This change will only affect the user interface and not the content language. 2. Create content in any language with WPML: By using the flag option in the top-bar on the website's backend, you can switch and create content in any language, such as Dutch. This allows content creation in Dutch while keeping the website's default language as English. Currently, there is no feature to permanently set a different default language for the backend, but setting it to Dutch will remain until changed again.
If this solution does not 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 the problem persists, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
