Problem: You are experiencing a timeout error when updating product categories with translations using the sitepress-multilingual-cms plugin. This issue occurs in the backend and sometimes deactivates some plugins. Solution: First, ensure you have a full website backup. Then, follow these steps: 1. Navigate to WPML > String Translation and deactivate the auto-register of strings. 2. Go to WPML > Support > Troubleshooting and click on the buttons as indicated. If the problem persists, consider modifying a specific function in your plugin files: 1. Locate the file at
This modification should help alleviate the timeout error. If these steps do not resolve the issue or if the solution becomes 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 still persists, please open a new support ticket.
Problem: If you're experiencing a timeout error when updating product categories with translations on your website, and this issue only occurs when the sitepress-multilingual-cms plugin is active, it might be due to a plugin conflict.
Solution: We recommend following these steps to identify and resolve the issue: 1) Ensure you take a full backup of your site and database. It's advisable to perform these tests on a development or staging site. 2) Enable debugging on your site to log errors. Details on how to do this can be found at https://wpml.org/documentation/support/debugging-wpml/. 3) Deactivate all plugins except for WPML, String Translation, WooCommerce, and WCML. 4) Switch to a standard theme like 2024 or 2021. 5) Check if the issue persists. If not, reactivate plugins one by one to identify the conflicting plugin. 6) If the issue does not reoccur after all plugins are activated, switch back to your original theme to check for theme conflicts.
If this solution does not resolve your issue or seems outdated, please check 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. We highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: You are encountering an error in your logs indicating that the cache keys 'product_cat' and 'product_tag' are incompatible with prefetching, and the group 'WPML_Slug_Translation_Records::taxonomy' should be added to the list of non-prefetchable groups. You are concerned about the importance of this error and how to resolve it. Solution: We have consulted with our second-tier team and discovered that the WPML plugin defines cache groups for various text domains, which might be causing the notices from Object Cache Pro. The current constant used might not support wildcards, unlike the 'WP_REDIS_CONFIG' which does. We recommend defining this in your wp-config.php file:
This configuration should address all variations of the cache group names. However, these warnings might be informational and may not require action if your system operates normally. We suggest verifying this with Object Cache Pro support. If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure you have the latest versions of themes and plugins installed. If further assistance is needed, we highly recommend opening a new support ticket with us.
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.
