Problem: If you're experiencing an MD5 error when saving ACF field groups in non-primary languages, particularly with nested fields such as a group containing a sub-field, this might be due to a bug in ACFML versions 2.2.2 and 2.2.1. Solution: We recommend applying a temporary workaround until a permanent fix is available. Please edit the file
This adjustment should prevent the error from occurring when saving in secondary languages.
Please note that this 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: When you create a product translation in WooCommerce, it imports all the data, but the page only works after you open the product in the WordPress editor and click Save. Without this step, it results in a 404 error, even after trying to 'Recreate permanent links'. Solution: We recommend following the steps outlined in the documentation to address issues with .htaccess that might be causing the 404 errors. Please check the solution provided here: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/
If this solution does not resolve your issue or seems irrelevant due to being 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 for further assistance at WPML support forum.
Problem: If you're experiencing orders stuck on hold and encountering a database error indicating that the table 'dbuwnruvbop5cs.bfs_icl_strings' doesn't exist, this might be due to a missing table in your WPML setup. Solution: First, ensure you have a full backup of your site. Then, attempt the initial debugging steps by following the workaround provided here: Missing _icl_strings and _icl_string_translations data tables. Next, update all outdated plugins and themes. You can check for updates on your site's update page. If the issue persists, it might be necessary for our support team to access your site to make direct adjustments in the database, specifically within the languages table of the WPML plugin, by adding the missing information.
Please note that this 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 problem continues, please open a new support ticket.
Problem: The client is unable to activate the OTGS plugin despite receiving a 'Plugin activated' message, and continues to receive a message to activate the WPML String Translation plugin for Rank Math settings, even though it is already active. Solution: The OTGS Installer plugin is only necessary during the initial installation of WPML. Since WPML plugins are already installed on your site, the OTGS Installer is no longer needed and can be safely deleted. It is expected behavior that it cannot be activated in this case. The issue with the Rank Math plugin displaying a message to activate the WPML String Translation plugin is a known issue. This is a false-positive notice and is expected to be resolved in future Rank Math releases. As a temporary workaround, please refer to the following guide: https://wpml.org/errata/rank-math-seo-false-string-translation-activation-notice/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing issues where the bundle ID is not correctly pointing to its translated version in WPML, despite being set to copy, this might be similar to the issue we encountered. In this specific case, the bundle ID 20 was not automatically pointing to its translated counterpart, ID 21. Solution: We recommend checking the settings to ensure that the IDs are correctly linked for translation. If the problem persists, it may require further investigation by our compatibility team. We will keep the client updated on any progress.
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 continues, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are facing an issue where product bundles are not being copied over to translations in WooCommerce. Even manual additions disappear upon publishing. Solution: This problem stems from a function in the WooCommerce core, not the WooCommerce Product Bundles plugin. Currently, there's an internal ticket reviewing potential changes to this behavior. Meanwhile, you can prevent the duplication of translations when duplicating a product by adding the following code to your theme's functions.php file:
/** * Prevent WCML from also duplicating the translations * when duplicating a product. */ add_action( 'admin_init', function() { /** @var \woocommerce_wpml $woocommerce_wpml */ global $woocommerce_wpml; if ( isset( $woocommerce_wpml->duplicate_product ) ) { remove_filter( 'woocommerce_product_duplicate', [ $woocommerce_wpml->duplicate_product, 'woocommerce_duplicate_product' ] ); } } );
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.
Problem: You are experiencing an issue where a single block template created in the Site Editor, when translated, receives a different slug, causing the front end page not to recognize the template. Solution: We recommend following the workaround described in our errata to address the slug mismatch issue. Please visit the following link for detailed steps: https://wpml.org/errata/template-is-not-applied-to-translated-page/ If the problem persists after implementing these steps, we encourage you to open a new support ticket for further assistance. 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.
If you need further assistance, please contact us through our support forum: WPML Support Forum
