Problem: The client is using the Uncode theme with WPBakery Page Builder and has an issue with the 'Pricing Table' shortcode not translating correctly in WPML. Specifically, the 'body' attribute in the shortcode does not retain line breaks when shown in the translation editor. Solution: We recommend modifying the WPML configuration XML to specify the attribute type and encoding for the 'body' attribute. Here are the steps: 1. Update the WPML configuration XML as follows:
2. Make a minor change in the default language page to trigger the translation reload, then attempt to translate the page again. For more detailed information, please refer to the following documentation:
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the vc_progress_bar shortcode using WPML, but the value and label fields do not appear in the translation editor despite following the steps in the documentation. Solution: We recommend adding specific code to your functions.php file to handle the encoding and decoding of the vc_progress_bar shortcode. Here is the code you should add:
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with conditions being stripped from HTML code during translation in WPML, specifically with the '==' and '!=' conditions in Advanced Product Fields Pro for WooCommerce, this might be due to limitations in the Advanced Translation Editor (ATE).
Solution: We recommend switching to the Classic Translation Editor for cases where specific conditions like 'equal' are not appearing correctly in ATE. Here’s how you can do it: 1. Navigate to WPML > Settings and switch to the Classic Translation Editor. 2. When translating a product, use the 'Copy all fields from original' option, then manually translate text fields while leaving rule-based fields unchanged. 3. Manually add the 'Equal' condition in the translated product to ensure it functions correctly. 4. If using ATE and encountering issues with automatic translations, you will need to manually update the condition rule for 'equal' in the translation. 5. For issues like the required field marker appearing incorrectly, manually save the translated product to ensure that changes propagate correctly.
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: You are using the Advanced Product Fields plugin for WooCommerce and have successfully translated the product options on the product page. However, when products are added to the cart, the option values still appear in the original language, not the translated version. Solution: We recommend adding the following code to the
functions.php
file of your theme. Please ensure you perform a full site backup before implementing this code:
// Add the filter with a higher priority (lower number) than the plugin's filter
add_filter('get_post_metadata', 'translate_wapf_fieldgroup_post_meta', 10, 4);
function translate_wapf_fieldgroup_post_meta($value, $post_id, $meta_key, $single) {
if ($meta_key === '_wapf_fieldgroup') {
// Temporarily remove the filter to avoid infinite loops
remove_filter('get_post_metadata', 'translate_wapf_fieldgroup_post_meta', 10);
// Get the original meta value
$fieldgroup_meta = get_post_meta($post_id, $meta_key, false);
// Re-add the filter
add_filter('get_post_metadata', 'translate_wapf_fieldgroup_post_meta', 10, 4);
if (!empty($fieldgroup_meta) && is_array($fieldgroup_meta)) {
foreach ($fieldgroup_meta as &$group) {
if (isset($group['id']) && preg_match('/p_(\d+)/', $group['id'], $matches)) {
$post_id = $matches[1];
$translated_post_id = apply_filters('wpml_object_id', $post_id, 'post', true);
$group['id'] = str_replace("p_$post_id", "p_$translated_post_id", $group['id']);
}
}
}
return $fieldgroup_meta;
}
return $value;
}
This solution addresses the issue where the plugin stores the Advanced Product fields in _wapf_fieldgroup as a multidimensional array, which may not update correctly across different languages in the cart.
Please note, this workaround may not function correctly if languages are switched on the Cart or Checkout pages. To prevent potential issues, enable the "Prompt for a confirmation and reset the cart" option. For more details, see this article.
If this solution does not resolve your issue or seems outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket at WPML support forum.
