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.
Problem: The client was experiencing a performance issue with a slow WPML query on their WooCommerce site, which took 3.5 seconds to complete. The query involved a
1
SELECT COUNT(...)
check that was identified as problematic.
Solution: We recommended the client to update all outdated WPML plugins and to revert the site to a minimal setup to ensure there were no performance issues. We then advised the client to activate only the plugin responsible for creating the Cars and Models to determine if the performance problem would reoccur.
If you're experiencing similar issues, we recommend you try the following steps: 1. Update all outdated WPML plugins. 2. Revert your site to a minimal setup and check for performance improvements. 3. Activate plugins one by one to identify the source of the problem.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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 in the WPML support forum.
Problem: The client has a multilingual website with different language configurations for each country-specific domain. They encountered an issue where the default language for product creation was set to Latvian (LV), which is not available on the Lithuanian (.lt) and Estonian (.ee) versions of the site. This caused difficulties when editing products, as the WP-admin needed to be switched to a different language.
Solution: We explained that it is not possible to change the default language for all products directly. With WPML, products can be created in any language and then translated into other languages. However, changing the default language of a site does not alter the original language of a post. To change the original language of a product, the client would need to disconnect the product from its translations and then reconnect them, choosing the desired default language during the process. Any other method of changing the original post language would require custom programming.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly advise checking the related known issues, verifying the version of the permanent fix, and ensuring that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client was experiencing an issue where all products were being skipped during an import from a Google Sheets file, even after replicating all import settings from the provided video and manual.
Solution: We investigated the issue and found that the problem persisted even when WPML (and/or WPML Export and Import) was deactivated. This indicated that the issue was unrelated to WPML. We suggested that the client should look into the WP All Import plugin or the import settings as the likely source of the problem.
If you're experiencing a similar issue with products being skipped during import, we recommend checking your WP All Import plugin and import settings. It's important to note that the solution provided here might be outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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 with us.
Problem: The client wants to know if it's possible to import product descriptions in different languages from a single Google Sheet document, instead of using separate files for each language linked by a unique ID.
Solution: We recommend adding a unique identifier to your spreadsheet to connect the default language content with its translations. It's important to use an ID number and not other custom fields like SKU. Here are the steps to follow: 1. Ensure each product has a unique ID number in the spreadsheet. 2. Do not use the SKU as a unique identifier. 3. Refer to our documentation on how to add a unique identifier to your spreadsheets for detailed guidance. 4. Consider our new Add-On, WPML Export and Import, which has reached version 1.0 and offers additional solutions for importing content. You can find more information in our recent newsletter or on the compatibility announcement page.
If this solution doesn't seem relevant to your situation, please open a new support ticket in our support forum.
Problem: The client is experiencing issues with automatic translation of products in bulk through Translation Management. The products added for translation are stuck in the queue and not being processed. Solution: We recommend the following steps to resolve the issue: 1. Go to WPML > Support > Troubleshooting in your WordPress dashboard. 2. Scroll down and click on the button labeled "Cancel in-progress Automatic translation job." 3. Then, navigate to WPML > Translation Management > Jobs. 4. Delete any Jobs that are marked with an "in progress" status.
After completing these steps, clear both the site and browser caches, and then try to resend the Jobs for Automatic translation.
Problem: The client is trying to replace the word "Starpsumma" with "Summa" in the PDF invoice generated by WooCommerce. Despite adding the translation in the String Translation, the issue persists. The correct word appears when downloading the invoice directly from WooCommerce, but not when the customer receives the PDF via email.
Solution: 1. We suggested deactivating the WPML plugin to check if it affects the issue. 2. If the problem remains, we recommended contacting the support team of the PDF Invoice plugin for further assistance. 3. If deactivating WPML resolves the issue, we asked the client to replicate the problem on a provided sandbox site to allow us to investigate further. [Client reported that updating the PDF invoice plugin seems to solve the issue.] If this solution doesn't look relevant, please open a new support ticket.
