Problem: You are encountering an issue where, after running a job every hour to update products and attributes in the primary language, the translated products appear without attributes despite having translated attributes created. Solution: We recommend using WPML API hooks to update the attributes of translated products programmatically after updating the attributes of default language products. Here is an example code designed for a cron job context:
1
add_action('wssupp_custom_cron_job', 'wssupp_custom_task_function');<br />functionwssupp_custom_task_function() {<br /><br /> // update the product attributes of a specific product as a demo<br /> $product_id = 21;<br /> $attribute = 'pa_color';<br /> $term_slug = 'yellow';<br /><br /> $original_term = get_term_by( 'slug', $term_slug, $attribute );<br /> $default_language = apply_filters( 'wpml_default_language', NULL );<br /><br /> // Step 1. Programmatically set product attribute for sample default-language post<br /> wp_set_object_terms( $product_id, $term_slug, $attribute );<br /><br /> // Step 2. Get the translations of the product to other languages<br /> $product_trid = apply_filters( 'wpml_element_trid', NULL, $product_id, 'post_product' );<br /> $product_translations = apply_filters( 'wpml_get_element_translations', NULL, $product_trid, 'post_product' );<br /><br /> // Step 3. Get the term translations<br /> $term_trid = apply_filters( 'wpml_element_trid', NULL, $original_term->term_id, 'tax_'.$attribute );<br /> $term_translations = apply_filters( 'wpml_get_element_translations', NULL, $term_trid, 'tax_'.$attribute );<br /><br /> // Step 4. Iterate over the product translations and update product attribute for each<br /> foreach ($product_translations as $lang => $product_translation) {<br /><br /> if ( $lang == $default_language ) {<br /> continue; // skip default language<br /> }<br /><br /> wp_set_object_terms( $product_translation->element_id, $term_translations[$lang]->term_id, $attribute );<br /> }<br />}<br />
For further details, refer to our WPML Hooks Reference. You should adjust the code to your needs.
If this solution does not resolve your issue or seems outdated, 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. We highly recommend opening a new support ticket if needed.
Problem: The client was experiencing a 502 error when trying to update a product through the admin and save the changes by clicking the update button. This issue was not occurring with every product, only some of them. The problem was found to occur when WPML Multilingual CMS was active. Solution: We ran the WPML troubleshooting options, which resolved the issue. We recommend the client to edit the product again to check if it works correctly. For further guidance on WPML troubleshooting options, please refer to our guide: WPML Troubleshooting Options.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we suggest opening a new support ticket. We also highly recommend checking related known issues at WPML 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 contact us through the WPML support forum.
Problem: The client is experiencing issues with product translations in WooCommerce using WPML. Specifically, attributes created directly within products are not appearing in the Advanced Translation Editor or in WooCommerce Multilingual > Attributes or String translations.
Solution: We recommend creating attributes globally in Products > Attributes rather than within individual products. This ensures that they are available for translation in the Advanced Translation Editor and in WooCommerce Multilingual.
Problem: The client is trying to translate products from Greek to English and encounters an issue where the Save button is missing in the translation tool.
Solution: 1. We recommend deactivating all plugins except for WPML, String Translation, WooCommerce, and WooCommerce Multilingual to check if the issue persists. 2. If the issue is resolved, reactivate the plugins one by one to identify the conflicting plugin. 3. Since the client identified 'Custom Product Tabs for WooCommerce' by Code Parrots as the conflicting plugin, we suggest trying to replicate the issue on a sandbox site provided by us. The client should complete the setup, install the plugin, select Classic Translation Editor as the default editor from WPML Settings, and attempt to recreate the issue. 4. If the issue is reproducible in the sandbox, the client should inform us for further assistance. 5. As a temporary solution, the client can switch to the "Advanced Translation Editor" by going to WPML > Settings > Translation Editor on the live site.
