Problem: You have built a custom plugin for WooCommerce and added extra fields like 'Pieces per box', 'Enable custom calculation', 'Piece Height (cm)', and 'Piece Width (cm)'. You want these fields to remain consistent across all languages and be locked with a message indicating that WPML will copy its value from the original language. However, you are unable to lock these custom fields for all languages. Solution: To lock custom fields in WooCommerce to ensure they remain the same across all languages, you can use the
wcml_js_lock_fields_classes
filter. This filter allows you to specify which custom field classes should be locked in the WooCommerce native product editor for translated products. You need to add this code to the functions.php file of your theme or within your custom plugin.
/**
* Add this code to the functions.php file of your theme.
*/
add_filter( 'wcml_js_lock_fields_classes', 'add_js_lock_fields_classes' );
function add_js_lock_fields_classes( $classes ){
// Add 2 locked field classes
$classes[] = '_per_product_pricing_bto';
$classes[] = '_per_product_shipping_bto';
return $classes;
}
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the content of a form on your website using WPML, but the translation process does not complete and remains 'In progress' after you click save. Solution: We recommend applying the workaround provided in the following documentation: Divi PHP 8.2 Fatal Error. Our development team is aware of similar cases and is working on a permanent fix.
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 for further assistance.
Problem: The client was unable to see the English translations for the labels in the "ACF/Field Group/Fields/labels" on their website, even after translating them using WPML's String Translation.
Solution: We accessed the client's site and changed the return value for the ACF fields from 'value' to 'label'. This adjustment should ensure that the translated strings display correctly on the English version of the site.
If you're experiencing a similar issue with your ACF field labels not appearing in the translated language, we recommend checking the return value settings for your ACF fields. It should be set to 'label' to display the translated strings.
Please note that this solution might be irrelevant if it's outdated or not applicable to your specific case. If after trying this solution you still encounter issues, we highly recommend checking the related 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 with us.
Problem: The client was experiencing an issue where the Advanced Custom Fields (ACF) content was not translating correctly from Greek to English on their product pages, despite having translated all related strings in WPML's String Translation.
Solution: We resolved the issue by navigating to ACF > Field Groups and selecting the relevant field group. We then switched the translation mode to 'Expert' and changed the translation preference for the specific SELECT option from 'COPY' to 'TRANSLATE'. After making a minor edit to the product and saving, we allowed the automatic translation to process the changes. For further details on using the Expert Translation Mode with ACF and WPML, please refer to our documentation: Expert Translation Option.
Please note that this solution may not apply to your situation if it's outdated or not relevant to your case. If you're still encountering issues, we encourage you to open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
The client wants to translate the Terms of the attributes, not the names of the attributes.
Solution:
Please go to WPML-> String Translation and search for the attributes' names. Also, please go to WooCommerce Multilingual-> Attributes tab, select the attribute, and translate its name and slug.
