[Closed] Error on the product types translations

Thank you for sharing the details.

I haven't been able to login, though. When inserting the credentials you shared and clicking "Se connecter", the pages that refreshes and I get back to the login screen.

Can you please check? If you need to share new credentials, the fields are enabled. Thank you.

Hi there,

First, a quick note about scope: we can’t provide support for custom code. That said, I’m happy to share some pointers so you can move forward. Anything deeper would require adjusting and testing the code, which is outside our support scope.

Why it likely only works in the default language

1. Custom field not copied: the `_preorder_goal` value may exist only on the default-language product if the field isn’t set to Copy in WPML’s custom fields settings. If it’s empty on the translation, nothing shows.

2. Attribute/variation language mismatch: you hard-code decoration slugs (default-language) and count only variations for the current product. In WPML each translation has different product/variation IDs and attribute slugs can change per language—so orders placed in other languages won’t be included. You need to map all translations of the product (and its variations) before counting. (See `wpml_element_trid` / `wpml_get_element_translations`.)

You have for example, on line 38 of Pre-Order System:

$slugs = ['remax-crystal', 'remax-dici', 'remax-crystal-dici'];

The slugs are necessarily different on other languages.

Suggestions on how to make it multilingual-safe

1. Check category via translated ID, not slug

Get the base term ID (default language), then resolve the current language term with `wpml_object_id( $base_id, 'product_cat', true )`; pass that term ID to `has_term`.

2. Ensure `_preorder_goal` is available on translations

Go to WPML > Settings > Custom Fields Translations, click on "Show system fields", and set that custom field to Copy so translated products read the same value. Check the image attached.

3. Derive decorations dynamically and in the current language

Don’t hard-code slugs, like I showed on line 38. Read the product’s `pa_decoration` terms for the current language, and render their names (already translated). If you must compare across languages, map term IDs with `wpml_object_id` (or use translated slugs via `wpml_get_translated_slug`).

_____________________________________

Overall, your code is not adapted to work in a mul-lingual scenario, along with WPML. Also, it has hard-coded information, which can lead to errors like the ones you are having. It's always best to use IDs, instead of strings like slug names.

My best suggestion is that you verify the product information (products, slugs, IDs, etc ) that's being pulled, and check how it behaves in terms on language. If it's only pulling single language data, check our hooks reference for developers, so it works with WPML:

https://wpml.org/documentation/support/wpml-coding-api/wpml-hooks-reference/

Let me know if you have other questions.