Problem: The client was concerned about a missing 'Flavor' attribute in WooCommerce >> WooCommerce Multilingual > Attributes tab, which was not appearing alongside another attribute 'HS Codes'. Additionally, the client noticed values like '18 left' on the troubleshooting page, which they thought should be '0 left', and was unsure whether to address these.
Solution: We advised the client that if an attribute does not appear under Products -> Attributes in the WordPress dashboard, it will not be visible in the WooCommerce Multilingual -> Attributes tab. To resolve this, the client should manually add the missing 'Flavor' attribute from the product edit screen. However, this will not make it appear in the WooCommerce Multilingual -> Attributes tab. If the client feels that something might be wrong due to the missing attribute, we recommend adding it manually.
For the values like '18 left' seen on the troubleshooting page, these indicate items that may need attention. We suggest the client review each option that does not show '0 left' and press 'Start' to address them.
If the solution provided here is not relevant due to being outdated or not applicable to your case, please open a new support ticket. 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client has a variable product with translations, but not all attributes are showing in the attribute dropdown on the translated pages.
Solution: If you're experiencing missing attributes in the dropdown of your translated variable products, we recommend you try the following steps:
1. Ensure you have a complete backup of your site.
2. Navigate to WPML >> Support >> Troubleshooting page and click the following buttons: - Clear the cache in WPML - [Products] Synchronize posts taxonomies - Remove ghost entries from the translation tables - Synchronize local job ids with ATE jobs - Synchronize translators and translation managers with ATE - Assign translation status to duplicated content - Fix post type assignment for translations - Set language information
3. Go to WooCommerce >> WooCommerce Multilingual >> Attributes tab, select the problematic attribute, and click the "Synchronize attributes, and update product variations" button if available.
4. If the problem still exists, navigate to WooCommerce >> WooCommerce Multilingual >> Settings tab >> Troubleshooting link (bottom right), select the “Sync products variations” option, and click on the 'Start' button.
file. 2. Locate the SQL query around line 88. 3. Replace the existing SQL query with the following code, which includes a filter for the current language:
$current_language = apply_filters( 'wpml_current_language', NULL ); <br /> $sql = "<br /> SELECT l.ID, post_title, post_name, post_parent, post_date, post_type, l.post_modified<br /> FROM (<br /> SELECT DISTINCT p.ID, p.post_modified FROM {$wpdb->posts} as p<br /> LEFT JOIN {$wpdb->postmeta} AS pm ON ( p.ID = pm.post_id AND pm.meta_key = 'rank_math_robots' )<br /> INNER JOIN {$wpdb->prefix}icl_translations AS icl ON ( p.ID = icl.element_id AND icl.language_code = %s AND icl.element_type LIKE 'post_%' )<br /> WHERE (<br /> ( pm.meta_key = 'rank_math_robots' AND pm.meta_value NOT LIKE '%noindex%' ) OR<br /> pm.post_id IS NULL<br /> )<br /> AND p.post_type IN ( %s ) AND p.post_status IN ( '" . join( "', '", esc_sql( $statuses ) ) . "' )<br /> ORDER BY p.post_modified DESC<br /> ) o<br /> JOIN {$wpdb->posts} l ON l.ID = o.ID " . $get_child . " ORDER BY " . $sort['field'] . " " . $sort['order']; // phpcs:ignore<br /> $sql = $wpdb->prepare($sql, $current_language, $post_type);<br /> return $wpdb->get_results( $sql ); // phpcs:ignore
4. Remember that Rank Math uses cache, so you may need to reset your sitemaps after making this change. To do this, go to Rank Math SEO > Sitemaps settings, modify a setting, revert the change, and save it.
Please note that this solution might be outdated or not applicable to your case. If it doesn't help, 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 issue persists, please open a new support ticket with us.
Problem: The client received a message with translation information in a table and was confused about the meaning of the 'Deadline' column, which showed the year 0001. Solution: 1. Upon reviewing the email, we suggested that the issue might be related to the server since a deadline is typically set to 0000-00-00 when not defined, but the email showed 30.11.-0001. We requested a screenshot of the wp_icl_translate_job database table to investigate the dates stored there. 2. We reassured the client that the translation process should not be hindered by this date issue and that they should be able to complete translations without any problems.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, 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 with us.
