Problem: You are trying to edit the menu on your WordPress site using WPML and expect to see different menus in different languages. However, all menus are appearing in one language only. Solution: We recommend temporarily disabling WPML for one or two minutes to test if the issue persists. This step will help determine if the problem is related to WPML or possibly another factor, such as a caching plugin. If the issue is resolved when WPML is disabled, it suggests that the problem might be related to how WPML interacts with other plugins or settings on your site.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
The client was experiencing a persistent error message "If you have used WPML to translate the tab custom content fields, please click on the button below to make them translatable in the Translation Editor." even after running an SQL query. The error was related to the WooCommerce Product Tabs plugin.
Solution:
We conducted tests on a clean installation and ran the following SQL query which resolved the issue:
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('wc_product_tabs_made_fields_translatable', 'on', 'yes');
This query ensures that the WooCommerce Product Tabs fields are translatable.
Additionally, we identified that the error message originates from the WooCommerce Product Tabs plugin, specifically in the file woocommerce-product-tabs-pro/src/Admin/Product_Editor_Tabs.php on line 345. The code responsible is:
echo '<div class="notice notice-info is-dismissible"><p>'. __('If you have used WPML to translate the tab custom content fields, please click on the button below to make them translatable in the Translation Editor.', 'woocommerce-product-tabs') .'</p><p><a href="' . esc_url( $url ) . '" class="button button-primary">Run Now</a></p></div>';
If the problem persists, don't hesitate to get in touch with the plugin author for further assistance.
Please note that this solution might be 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. If the issue continues, we encourage you to open a new support ticket at WPML support forum.
Problem: You are experiencing a persistent message in WPML that asks to make tab custom content fields translatable, and it reappears even after clicking 'Run Now'. Solution: We have identified that the issue is related to a missing option in your database. To resolve this, you can manually insert the necessary option by executing the following SQL command:
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('wc_product_tabs_made_fields_translatable', 'on', 'yes');
This action should prevent the message from appearing again. However, since there is no existing code that sets this option automatically, we recommend contacting the developers of the WooCommerce Product Tabs plugin to address this issue permanently.
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 problem persists, please open a new support ticket.
Problem: The client was experiencing an issue where some products were displaying in incorrect categories on their multilingual website. Solution: 1. We first checked if the issue occurred in the original language of the site. 2. We recommended increasing the WordPress memory limit to at least 256MB by adding the following code to the wp-config.php file:
3. We requested the client to ensure all plugins and the WordPress core were updated. 4. After updates, we identified that the theme was still outdated and needed updating. 5. Upon updating, we performed troubleshooting steps and corrected the slug for the shop page in both languages, which resolved the issue. 6. The problem was due to the shop page slug conflicting with the product slug.
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 highly recommend opening a new support ticket here.
Problem: The client is unable to see the 'Translate independently' option for posts in WPML and is experiencing issues setting posts to 'nofollow' using Yoast SEO, which leads to errors. Solution: 1. Ensure that the post is duplicated before trying to set it to 'translate independently'. This option appears only when editing the post in the secondary language. 2. To address the 'nofollow' setting, create a post in the original language and set it to 'no follow'. If this works without errors, the issue might be with the duplicated posts in other languages. 3. If encountering errors with duplicated posts, check if the template used by the original post still exists in the theme directory. If not, reassign a valid template and try duplicating again. 4. If problems persist, consider recreating the problematic post with the same content and settings to see if this resolves the issue.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing errors when trying to set a post as nofollow with Yoast, and encountering fatal errors after saving the post, it might be related to your WPML settings and configurations. Solution: The issue occurred only with specific custom post types, such as "Downloads" from "Download Manager Pro". Setting these custom post types in WPML to "Translate independently" instead of duplicating them resolved the issue. We also recommend updating all your plugins to verify if the issue persists. If it does, we can try to recreate the issue on a test site.
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 problem continues, please open a new support ticket at WPML support forum.
Problem: If you're trying to cache your website using a plugin while using domain names for translations instead of subdomains or directories, and you're not seeing cached versions for different domain names like heskins.de, heskins.es, etc. Solution: We recommend trying the following caching solutions that are compatible with WPML:
Please note that the solution might be irrelevant if it's 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. If the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing slow SQL queries during searches on their website, specifically when using the WPML plugin. The issue persists even when WPML is disabled, suggesting that the problem might not be directly related to WPML. Solution: We recommend addressing this issue with the theme developers, in this case, Avada. It appears that the SQL query itself is fundamentally expensive and inefficient. The client should demonstrate that the query performs well without WPML before considering it as a WPML-related issue. If after consulting with Avada the problem seems to be related to WPML, we encourage the client to contact us 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 at WPML support forum.
