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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: America/Los_Angeles (GMT-07:00)

This topic contains 3 replies, has 2 voices.

Last updated by Bobby 1 year ago.

Assisted by: Bobby.

Author Posts
August 19, 2024 at 11:21 pm #16085400

firmaD-2

Background of the issue:
I am using WPML with a theme on my site hidden link. Under WPML > Settings in the section Taxonomies Translation, there are custom fields specific to the theme that are currently set to not translate. These fields include Makes, Bodies, Models, Model Style, Conditions, Years, KM, Fuel types, Transmission, KW, Exterior color, Interior color, Engine, Price, Drives, Supplier offer number, and Additional features. I import different inventories for each language using WP All Import and want to keep inventories independent between languages. I noticed that taxonomies under Listing categories got duplicated.

Symptoms:
Taxonomies under Listing categories got duplicated after importing inventories for different languages.
I received a critical error via email from WordPress who detected it on the site (images 4 and 5).

Questions:
Should I set these custom fields as translatable or keep them as they are?
Am I doing something wrong with the current import process?
Do I need to activate anything else under the section Taxonomies Translation?

August 20, 2024 at 3:20 am #16085600

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Regarding the error it is curious that it shows up during the import process, however, it does not point to WPML in the log.

What is the theme you are using that the taxonomies are coming from?

Typically these are set by default that way and we don't recommend changing them, however, if they are set to "do not translate" they will not be included in the translation process.

Now could you elaborate on the desired effect with maybe an example.

For example let's say you import a product the following should most likely be the same in the translation as well. If the EN version is showing let's say, Mercedes, SUV, Good, 2010, GAS, AUTO, etc.

Makes, Bodies, Models, Model Style, Conditions, Years, KM, Fuel types, Transmission, KW, Exterior color, Interior color, Engine, Price, Drives, Supplier offer number, and Additional features.

September 2, 2024 at 12:06 am #16129715

firmaD-2

Hi Bobby, I double checked after your reply. I wanted to come back to you with the following information:

- the theme used is hidden link
- I realised that if I keep in the WPML setting listings as not translatable (for instance this is a listing page hidden link) by importing one csv or excel in WP All Import this creates all listing and these are shown in all languages but there are parts that cannot be translated this way.
For instance:
- now I am trying to set listing as translatable, but I am still not sure about the correct setting for:

1) custom field translation
2) taxonomies translation

I am trying to figure out things

Screenshot 2024-09-02 at 00.42.28.png
September 5, 2024 at 8:40 pm #16146848

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi there,

The Motors theme is compatible with WPML, however, there are known issues.

See here: https://wpml.org/theme/motors/#ki

Please review them and see if possibly you are experiencing on those issues.

If settings are set to not tranlsatable, then that is expected as they would not be able to be translated or linked to a translation thus they all are imported under the same language (default language)

Is there a way you can switch these settings back to default?

I would highly recommend not changing the default settings as they are set that way to ensure maximum compatibility.

The topic ‘[Closed] I want to understand if with this theme I do need to activate the translation of some custom fields …’ is closed to new replies.