Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by Dražen 2 years, 2 months ago.

Assisted by: Dražen.

Author Posts
August 25, 2023 at 1:52 pm #14292309

philippM-11

The following issue can be reproduced on a brand new WordPress (6.3) installation with the latest versions of WooCommerce (8.0.2), WPML (4.6.5), WPML String Translation (3.2.7) and WooCommerce Multilingual & Multicurrency (5.2.0).

WPML is set up to be German by default, having English as a secondary language.

1) I'm creating a new product attribute named "XXX".
2) I head to the WooCommerce Multilingual menu (tab "Store URLs") where the base language is marked as English, even though it should be German.
3) I switch to the tab Attribute and select the "XXX" attribute.
4) On the bottom I change the base language to German.
5) The base language in the "Store URLs" tab is still marked as english.
6) In the WPML String translation a new string can now be found with the name "URL pa_xxx tax slug", which is correctly marked as German.
7) Upon further inspection of the plugin's code I noticed it tries to find the source language using the name "URL attribute slug: xxx", which does not exist and it therefore falls back to english.
8) I head to the database and override the name of the string from "URL pa_xxx tax slug" to "URL attribute slug: xxx".
9) Now the attribute is correctly marked as German and I can create the translations.

It seems the problem is no translation string is added upon creation of the product attribute. Manually setting the language of this taxonomy does add the missing entry with the correct language set, but it has a different name than the one queried from the WCML plugin.

I found a programmatically working temporary fix using the filter "wpml_get_string_language" and overriding the queried name which seems to work for now, but I would like this issue to be fixed as multiple stores are affected by it.

August 28, 2023 at 8:59 am #14298767

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

thanks for contacting us and reporting.

I have checked and I can see what you described in your steps, It seems this issue has already been reported to our developers.

I have added your ticket also to the tracker and will update you when I have more news. Please note it will take some time.

In the meantime, you can use your workaround if it works for you.

Regards,
Drazen

December 6, 2023 at 1:30 pm #15008101

philippM-11

Are there any updates in regard to this issue?

December 6, 2023 at 2:11 pm #15008643

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

the ticket is in the dev queue and is scheduled for one of the future releases of WCML.

I can not give any ETA or similar but I will update you once the versions with permanent fix is out.

Regards,
Drazen