Problem: The client has a multilingual WooCommerce site and needs to use different SKUs for products translated into Latvian, without losing the language switcher functionality. The client also inquired about managing SKUs in different languages using WPML. Solution: We explained that in WPML, product translations must share the same SKU to sync stock and prices effectively across different languages. To use different SKUs, the client would need to create separate, original products for each language, which would not be linked as translations and thus would not support the default language switcher functionality. However, the client can create a custom language switcher or button that links to the respective products in different languages. We also provided links to documentation for further customization using hooks:
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: Der Kunde hat ein Problem mit der Lifting Charge-Funktion in WPML unter WooCommerce Multilingual & Multicurrency. Ein Aufschlag von 5 % wird nur im Checkout angewendet, nicht auf der Produktseite. Der Kunde sieht zunächst den gerundeten Preis, aber im Checkout wird der Preis um 5 % erhöht, was auch auf der Rechnung erscheint, jedoch ohne Rundung. Solution: Wir haben empfohlen, die Rundungsregeln in den Currency Settings für jede Währung individuell anzupassen. Eine detaillierte Anleitung dazu finden Sie unter: Währungsoptionen und Rundungsregeln festlegen.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: You are trying to retrieve a single attribute in a specific language via the `wc/store/v1` API endpoint, but you are receiving the attribute name in the default language (German) instead of the requested language (English). Solution: Attributes themselves are not translatable via the REST API, only their labels. To translate attribute names, navigate to WooCommerce → WooCommerce Multilingual & Multicurrency. In the 'Attributes' tab, scroll down to the 'Translations of taxonomy labels and slug' section and add the translations. As a workaround, you can use localized data to parse an object with all product attribute taxonomy names and their
$tax->labels->singular_name
, since labels are well translated thanks to WPML. This localized data is stored as a transient per language and deleted when their terms or taxonomies are edited/created/deleted.
If this solution seems outdated or does not apply to your problem, we recommend checking the known issues, verifying the version of the permanent solution, and confirming that you have the latest versions of themes and plugins installed. Don't hesitate to open a new support ticket if you still need help. Visit our support forum.
Problem: The client reported an issue where the admin received an order confirmation email in the HR (Croatian) language, but the customer received the same email in SI (Slovenian), despite all strings being translated correctly in WPML. Solution: We first recommended testing with only the default WordPress theme and essential plugins (WooCommerce and WPML) to ensure that the issue wasn't caused by any other plugin or theme conflicts. Upon testing, it was confirmed that the HR email was sent correctly to the customer under these conditions. Further investigation revealed that the issue was due to the use of a custom string added in the email content in SL (Slovenian), which was not translated. We advised the client to either translate these custom strings via WPML > Translation Management or to delete the custom strings and revert to using the default provided strings.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with automatic translations not covering the entire website and products in some languages not being able to be added to the cart. Specifically, the client mentioned that on the staging site, the 'add to cart' button was unresponsive, and on the production site, the quantity appeared as 0 instead of replicating the main language quantity. Solution: We reviewed the client's staging site and confirmed that the issue with adding products to the cart was not present in all languages, but only when the stock quantity for certain product variations was set to "0".
We advised the client to check the original product in the WordPress Editor and ensure that the stock quantities are correctly set for all variations. If the stock is not empty, the product should be addable to the cart in all configured languages.
In case the stock is not synced then it might be that systems fields have been altered at WPML > Settings > Custom Field Translation. We recommended ensuring that the WPML configuration changes made to 'copy' settings are correctly applied across all environments for fields like "_stock" to maintain consistent behavior.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client was unable to access certain translation features in WPML after an update, specifically encountering issues with translating taxonomies and products. Additionally, the client could not add a translation manager as no user was found. Solution: We recommended the following steps to resolve the issue: 1. Ensure a complete site backup is taken. 2. Open the
functions.php
file of your theme in a code editor. 3. Insert the following function to expand translation manager capabilities:
/**
* Expand translation manager caps to be able to translate taxonomies
*/
add_filter( 'user_has_cap', 'wssupp_boost_caps', 10, 1 );
function wssupp_boost_caps( $allcaps ){
$newcaps = array();
if ( isset( $allcaps['manage_translations'] ) && $allcaps['manage_translations'] ) {
$newcaps = [
"wpml_manage_taxonomy_translation" => true
];
}
return array_merge( $allcaps, $newcaps );
}
4. Save changes to the file. **** Important! Please make a full site backup (files and DB) before you proceed with these steps**** After applying these changes, check if the issue with the 'Translate Products >' button is resolved.
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.
Problem: If you're experiencing issues where product category images are not the same height across different language versions of your site, it might be due to custom CSS not being applied to the translated template. Solution: We recommend checking your default language category template for any custom CSS. If found, ensure this CSS is also added to the translated templates. Alternatively, for better management and consistency, add your custom CSS in a centralized location such as Elementor > Custom code, or Appearance > Customize > Additional CSS. Here is an example of CSS that you might need to apply:
.woocommerce ul.products li.product-category a img {<br /> width: 300; /* Ensures the image fills the container width */<br /> height: auto; /* Adjusts height to maintain aspect ratio if needed */<br /> aspect-ratio: 1 / 1; /* Forces a square format */<br /> object-fit: cover; /* Crops the image without distortion */<br />}
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.
