Problem: You are trying to translate Contact Form 7 using WPML and facing two issues: 1) The auto-translation isn't working correctly in some languages, showing the contact form shortcode on the frontend. 2) The
<[your-email]>
placeholder is missing in the message body for secondary languages after auto-translation. Solution: We have released a new version of the translation editor. We recommend re-translating your Contact Form 7 to check if the issues are resolved. For the missing email placeholder, ensure that your Contact Form settings under the Mail tab are correctly configured with the message body format as: From: [your-name]
<[your-email]>
.
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 at WPML support forum.
Problem: You are trying to translate custom product attribute names in a WooCommerce multilingual setup using WPML tools, without using String Translation. The custom attributes do not appear translated on the frontend in secondary languages, although they are visible and translatable in the Advanced Translation Editor.
Solution: We are planning to implement a feature to properly import local translated attributes in a future update of WPML. Meanwhile, we recommend a workaround: 1. Ensure you have a full website backup. 2. Add the following code to your functions.php file:
/**<br /> * Force unserializing of meta data in WC importer.<br /> */<br />add_filter('woocommerce_product_importer_parsed_data', function ($data) {<br /> if (isset($data['meta_data']) && is_array($data['meta_data'])) {<br /> foreach (array_keys($data['meta_data']) as $k) {<br /> $data['meta_data'][$k]['value'] = maybe_unserialize($data['meta_data'][$k]['value']);<br /> }<br /> }<br /> return $data;<br />});
3. Add an extra column 'Meta: attr_label_translations' to your CSV file. 4. Populate this column with serialized values for the attribute label translations. Use the structure [ 'LANGUAGE_CODE' => [ 'ORIGINAL-ATTRIBUTE-NAME-SLUG' => 'TRANSLATED ATTRIBUTE NAME', ], ] and serialize the array using this link. 5. Follow your usual workflow to import products.
This solution might be outdated or not applicable to your specific case. If it doesn't resolve your issue, 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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client is unsure about the function of the 'Synchronize attributes and update product variations' button in the context of translating variable products. They are confused because they thought variations were automatically generated when translating variable products. Solution: We explained that the 'Synchronize attributes and update product variations' button is crucial for keeping original variations and their translations up-to-date. This button becomes particularly useful when there are changes in attributes or variations that require updates. In the client's scenario, the presence of 118 variations needing creation suggests that these are updates rather than entirely new variations. By clicking this button and allowing the process to complete, the client should see their product variations correctly synchronized. We recommend regularly checking this function when updating or creating new attributes, or when making changes to variable products, to ensure all translations are current.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please visit our support forum. 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.
Problem: The client is unable to see the translated string "month" in secondary languages on their website, despite using JavaScript to append this string and the
wp_localize_script
function for localization.
Solution: 1. Ensure all strings are registered: - Navigate to WPML > Theme and plugins localization and scan your themes and plugins. 2. Re-register and translate strings: - Go to WPML > String Translation, delete all occurrences of the problematic strings, enable the "Look for strings when rendering pages" option, visit the frontend, and then add translations. 3. Check database charset configuration: - Ensure the database charset in
wp-config.php
is set to
utf8mb4
. 4. Regenerate .mo files: - Use the troubleshooting section under WPML > Support to regenerate .mo files.
If these steps do not resolve the issue, it may be necessary to use custom CSS for translation or further debug the JavaScript implementation. Custom programming, however, falls outside our support policy. For more complex issues or custom implementations, consider hiring a WPML contractor from https://wpml.org/contractors/.
Please note that this solution might be outdated or not applicable to your specific case. 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 https://wpml.org/forums/forum/english-support/.
Problem: After auto-translating a product, it remains unpublished and appears as a draft in the 'yoast_indexable' table. Solution: If you're experiencing this issue, we recommend that you publish the translated products manually. You can do this by navigating to Products, switching to the desired language using the language switcher at the top bar, and then selecting the products to publish in bulk. This action should update the post status in the 'yoast_indexable' table to reflect the published state.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related 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 for further assistance at WPML support forum.
