Problem: You have a custom taxonomy called 'fitment' assigned to WooCommerce products, set as Not Translatable in WPML. Terms are created in Polish and work correctly in Polish products, but in the English product edit screen, the taxonomy is visible without any terms to select. You want the same taxonomy terms to be shared across all languages without needing translations.
Solution: The issue might be related to the
meta_box_cb => 'post_categories_meta_box'
in your custom code. This meta box forces WordPress to render the classic Categories-style checklist metabox for this taxonomy, which relies on wp_terms_checklist() → get_terms(), and WPML filters get_terms() in wp-admin to the current admin language. If your Fitment terms are created only in the default language and don’t have term translations, the checklist in the secondary language can appear empty. To resolve this: 1. Remove the
meta_box_cb => 'post_categories_meta_box'
from your custom code to test if the terms show in the translation without it. 2. Register the taxonomy on init with priority 0 to avoid issues with it being registered too late.
If these steps do not resolve the issue, or if the solution becomes 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 the problem persists, please open a new support ticket.
Problem: If you're using WPML for multilingual support in your WooCommerce store and notice that stock updates via the Baselinker API only reflect in the default language (Polish) and not in the translated versions (e.g., English), this might be due to the Baselinker API not being integrated with WPML. As a result, updates made through the API do not trigger WPML's synchronization processes. Solution: We recommend contacting the Baselinker developers to suggest integration with WPML through our Go Global Program, which helps ensure compatibility: Go Global Program. For a temporary workaround, you can try to implement custom development to hook into WPML's synchronization processes. Specifically, you can use the
wpml_sync_custom_field
hook, detailed here: wpml_sync_custom_field. Additionally, you might consider creating a custom function to trigger stock synchronization across translations. Below is a conceptual example of how you might approach this:
function my_trbl_sync_stock() {
global $sitepress;
$results = get_original_products_and_variations();
foreach ( $results as $product ) {
if ( get_post_meta( $product->ID, '_manage_stock', true ) === 'yes' ) {
$translations = $sitepress->get_element_translations( $product->trid, $product->element_type );
$min_stock = false;
$stock_status = 'instock';
// collect min stock.
foreach ( $translations as $translation ) {
$stock = get_post_meta( $translation->element_id, '_stock', true );
if ( ! $min_stock || $stock < $min_stock ) {
$min_stock = $stock;
$stock_status = get_post_meta( $translation->element_id, '_stock_status', true );
}
}
// update stock value.
foreach ( $translations as $translation ) {
update_post_meta( $translation->element_id, '_stock', $min_stock );
update_post_meta( $translation->element_id, '_stock_status', $stock_status );
}
}
}
return true;
}
function get_original_products_and_variations() {
global $wpdb;
$results = $wpdb->get_results(
"
SELECT p.ID, t.trid, t.element_type
FROM {$wpdb->posts} p
JOIN {$wpdb->prefix}icl_translations t ON t.element_id = p.ID AND t.element_type IN ('post_product', 'post_product_variation')
WHERE p.post_type in ('product', 'product_variation') AND t.source_language_code IS NULL
"
);
return $results;
}
You can then call my_trbl_sync_stock() after your programmatic update.
Please note that this is a conceptual example and not officially supported or tested. Always back up your site before implementing custom code.
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 issues persist, please open a new support ticket at WPML support forum.
