Problem: You are trying to configure different domains for each language on your site using WPML, but encounter a 'not valid' error when saving the settings. The domains include thermex.ee for Estonian, thermexlt.lt for Lithuanian, and ru.thermex.lv for Russian, all pointing to the same IP as the main site. Solution: 1. Check if the error is a false positive by unchecking the validate checkbox and saving the settings. If your site functions correctly afterwards, the error may not be significant. 2. Ensure there are no static constants for WP_SITEURL or WP_HOME in your wp-config.php file, as these could interfere with validation when using different domains for each language. 3. Verify that there are no separate websites running on the additional domains. All domains should display the main website when WPML is disabled. If this is not the case, it might be a misconfiguration in your DNS settings. 4. Once your domain configuration is correct and all domains display the default language version of your site without WPML, you can re-enable WPML. If issues persist, contact us for further assistance.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: The client needs to add German translations for over 1,000 existing product categories on their multilingual website, which are already translated into four languages. They attempted to import the German categories as translations of the Latvian terms using WP All Import, but the translations were not linked correctly. Solution: We recommend following the specific workflow outlined in our guide for importing multilingual content. Ensure that you use the WPML Export and Import add-on and adhere to the process described to correctly link the imported categories to the existing translations. You can find the guide here: Importing Multilingual Content. If this method does not resolve the issue, another approach involves exporting all language data, ensuring the CSV file aligns with our documentation, and then re-importing each language. This should allow WPML to correctly connect the default language and its translations. Alternatively, for manual assignment of a large number of categories, consider developing a custom code solution. Use our hook wpml_set_element_language_details to connect the German categories as translations of the default language.
If these solutions do not apply to your case, or if they seem 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 at WPML Support Forum.
Problem: The client is experiencing an issue where the language parameter is being added to the .htaccess file on multiple sites using WPML, causing the website to become unusable. The altered .htaccess file includes a language base such as /en/, /ru/, or /lt/ which disrupts the site's functionality. Solution: If you're encountering this issue, we recommend following the workaround provided in the WPML documentation. Please visit the following link for a detailed guide and explanation of the root cause: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.
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 for further assistance.
Problem: You are experiencing issues with redirects on your multilingual site, where users and Google bots are redirected to the incorrect language domain when visiting old URLs with language parameters. This problem arises after moving each language to a separate domain. Solution: Our investigation confirmed that WPML does not trigger redirects between languages when 'display as translated' mode is used. Instead, the same product is displayed on all language URLs without altering the slug or structure. We recommend implementing custom redirection rules in your redirection plugin or .htaccess. For example:
This approach depends on how your server handles redirects and the availability of target slugs. Additionally, check any server-level rewrites or caching layers that might enforce canonical redirects. If further customization is needed, consider contacting one of our certified partners: https://wpml.org/contractors/
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 for further assistance.
Problem: You need to configure WPML to use a different domain for the French language while keeping other languages under the existing domain. However, when trying to save the settings, the 'Auto sign-in and sign-out users from all domains' feature keeps spinning and does not complete. Solution: We have identified that the issue arises because you are trying to mix different URL formats for different languages, which is not supported by WPML. Specifically, you cannot use both 'Languages in directories' and 'A Different Domain per Language' simultaneously. To resolve this, you should choose one URL format for all languages. If you decide to use different domains for each language, ensure that all languages are set up in this manner without mixing with directory-based URLs.
If this solution does not 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 at WPML support forum.
Problem: The client is trying to register WPML on their site but encounters a connection error stating 'Unable to get data from service. Detailed error: cURL error 28: Operation timed out after 45001 milliseconds with 0 bytes received.'
Solution:
If you're experiencing this issue, it might be due to a temporary problem blocking the connection to our servers. We recommend trying the workaround suggested in a similar case. Please ensure to back up your site before proceeding. You can find the detailed steps here: WPML support forum post.
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, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with media attachments not automatically uploading to custom product galleries in the translated versions of their 'Accessories' custom post type. Despite images appearing translated in Media Translation, they are not uploaded to corresponding posts. Solution: We recommend the following steps to potentially resolve the issue: 1. Navigate to WPML → Settings → Custom Fields Translation. Activate the option "Show 'Multilingual Content Setup' meta box on the edit screen" and save your changes. 2. Go to the "Accessories" post type and edit a custom post. 3. While editing, scroll down to the bottom of the "Custom Fields" section. 4. Click on "Show system fields" to locate the related fields.
5. Set those custom fields to "Copy".
Please note that the plugin used for the custom post type has not been tested for compatibility with WPML, which might lead to compatibility issues. Check the plugin's compatibility at this link.
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 at WPML support forum.
Problem: You are managing a multilingual WooCommerce site using WPML and have encountered an issue where some taxonomies are forced to be untranslatable, as indicated by a message in wp-admin. Solution: We recommend navigating to WPML > Settings > Taxonomies Translation and selecting the option that allows taxonomies to be translatable. This adjustment should remove the message about untranslatable taxonomies in wp-admin and resolve the issue.
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 the problem persist, please do not hesitate to open a new support ticket for further assistance. You can do so at WPML support forum.
Problem: The client is experiencing issues with products not displaying correctly in all languages on their category page. Additionally, there are stylistic differences between the production and staging sites. Solution: 1) For the issue with products not showing in all languages, ensure that all product attributes are correctly translated. This can be done via WooCommerce > WooCommerce Multilingual & Multicurrency, focusing on taxonomies and attributes. After translating, update or re-translate the products to ensure the correct taxonomies and attributes are assigned. 2) Regarding the stylistic issues, these appear to be present in the default language and might not be related to WPML. We recommend disabling WPML temporarily to check if the issue persists. If it does, it suggests the problem is not caused by WPML, and the client should open a new ticket for further assistance.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If necessary, do not hesitate to open a new support ticket with us.
