Problem: The client is experiencing issues with translating link targets and syncing menu items using WPML. Specifically, they encounter an error message 'Error! Reload the page and try again' when translating link targets and a 504 timeout error when syncing menu items, despite increasing the timeout limit. Solution: We identified that the issues occur when using WPML with the Breeze caching plugin and WooCommerce. Disabling the Cache System option in Breeze resolves the issue with translating link targets. For syncing menu items, if continuing with Breeze, we recommend adding the following code to the functions.php file of your Child Theme to handle currency switching for non-logged-in users:
Additionally, we suggest consulting the Breeze support to explore options for excluding specific scripts from caching. If Breeze support cannot provide a solution, please contact us for further assistance. 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 at WPML support forum.
Problem: The client is experiencing issues with locked translations on DE pages of their bilingual website (EN and DE). They are unable to edit translations directly and the fallback to the default language is not functioning on the frontend. Solution: We recommend checking if the attributes are added locally (directly in the product editor) or globally (via Products > Attributes). For global attributes, they should be translated using WPML's Taxonomy Translation, accessible at WPML > Taxonomy Translation. If translating a product using the WordPress Editor, ensure it uses global attributes. This approach should unlock the translations and allow the fallback to default language to function correctly on the frontend.
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 problems persist, please open a new support ticket.
Problem: The client needs to duplicate approximately 15,000 products to all languages on their WooCommerce site but finds the translation management page limiting as it only allows duplicating 100 products at a time. Solution: We recommend using the WPML hooks
wpml_make_post_duplicates
and
wpml_admin_make_post_duplicates
for bulk duplication of products. These hooks can help automate the process. However, implementing custom code using these hooks is outside our support scope. We advise testing the hooks on a staging or sandbox site first to ensure they meet your needs. For more details on these hooks, please visit the WPML Hooks Reference page at WPML Hooks Reference.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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: You want to translate a post using WPML, but the translation process gets stuck at 'in progress'. Solution: 1. Deactivate the GTranslate plugin on your site. 2. Make an edit to the content of the original post and save it. 3. Attempt to translate the post again. 4. Review the translation queue if necessary and complete any pending tasks. 5. Verify that the translations are now working. Note: The current language switcher in your menu, which is designed for GTranslate, will not work with WPML. Consider using one of the WPML Language Switchers.
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 the problem persists, we recommend opening a new support ticket here.
Problem: If you're experiencing a fatal error when switching languages on a product category page, specifically with the error message 'Fatal Error Illegal offset type in isset or empty' in
that retrieves a term named 'prod-cat__msg_banner'. The error occurs because the value returned is interpreted as an array with a blank element. Here are two solutions: 1. No code: Change the value in the database for the term ID to not be a serialized value. You can reference the original term ID 1135 to see how it is saved. 2. Using code: In
if (is_array($msg_banner)){ $msg_banner = $msg_banner[0]; }
Please test any of the solutions after making a full backup and let us know the results.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where the blue menu beneath the black header was not showing links to their respective translated categories. Instead, all links were directing to the English category permalinks. This issue started occurring after 29/04.
Solution: 1. Go to Appearance -> Menus, and copy the menu ID (for example, 37). 2. Navigate to WPML -> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the menu ID. 5. Select the string related to the menu ID. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the menu ID into the translated menus IDs.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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.
Problem: The client was experiencing an issue where product categories were showing duplicate products in different languages, alternating between German (DE) and English (EN), despite not being new products and having worked correctly for many years.
Solution: We identified that the issue might be due to a conflict with cache settings, specifically involving the Redis cache and the Breeze plugin with Varnish cache configured. We recommended the following steps: 1. Disable the Redis cache or configure it properly. 2. Disable the Varnish cache or configure it properly. As a workaround, we suggested changing the Product Category slug for the German version from
ktm-250-exc
to
ktm-250-exc-de
and then clearing the caches to see if the issue persists.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, 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 still exists, please open a new support ticket at our support forum.
Problem: The client's multilingual WooCommerce website experienced a disappearance of products in the translated languages (FR, DE, and USA). The issue was resolved by using the "Synchronize posts taxonomies" button, but the client sought an explanation for the cause and how to prevent it in the future. Solution: We explained that it is challenging to pinpoint the exact cause without further investigation. However, such issues may arise if: 1. Content was created while WPML or its add-ons, such as WooCommerce Multilingual (WCML), were disabled. 2. There is a conflict between WPML and another plugin, possibly a WooCommerce Addon. We recommended that if the issue reoccurs, the client should allow us to take a copy of their site for debugging and to attempt to recreate the issue. This would enable us to run troubleshooting steps to determine the cause. Please note that this solution 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. If you need further assistance, please open a new support ticket.
