Skip Navigation

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
10:00 – 14:00 10:00 – 14:00 10:00 – 14:00 10:00 – 14:00 10:00 – 14:00 - -
16:00 – 20:00 16:00 – 20:00 16:00 – 20:00 16:00 – 20:00 16:00 – 20:00 - -

Supporter timezone: Asia/Jerusalem (GMT+03:00)

Tagged: 

This topic contains 2 replies, has 0 voices.

Last updated by Itamar 15 minutes ago.

Assisted by: Itamar.

Author Posts
July 3, 2025 at 2:04 pm

andrea

Background of the issue:
I'm trying to update the slug of a custom post type on my site hidden link using WPML, but the changes won't save.

Symptoms:
The WPML settings are not saving when I attempt to update the slug of a custom post type.

Questions:
Why are the changes to the custom post type slug not saving in WPML?

July 3, 2025 at 3:37 pm
July 3, 2025 at 5:06 pm #17198970

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I'm consulting our second-tier supporters about this case, and when I have their answer, I'll get back to you here.

I appreciate your patience.
Itamar.

July 6, 2025 at 4:22 pm #17205181

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

Our second-tier supporter investigated the issue with the JetEngine "type of machine" filter and found the root cause. Here are his findings.

Currently, the filter is based on a custom field called tipologia, which is set up as a select field with a label and a value.

The label is what visitors see on the site, and it should be translated.

The value (the data actually saved in the database) should not be translated, so that filtering works properly across all languages.

On your site, the tipologia custom field is incorrectly set to Translate, which causes the values to differ between languages (e.g., "Centralizzato" in Italian and "Centralized" in English). As a result, the filter fails because it looks for the Italian value ("Centralizzato") even on the English version.

Recommended solution:
1. Change the translation setting for the tipologia custom field from Translate to Copy. This ensures the field value stays the same across all languages.
2. Once you update this setting, the existing product data in English will still contain the wrong values ("Centralized" instead of "Centralizzato").
3. To fix this, the data needs to be corrected — either by re-translating the products or, more efficiently, by running a database query to update the field values automatically.

If you’d like, we can guide you through changing the field settings and help prepare the query to fix the existing data.

Please let us know how you'd like to proceed, and we’ll be happy to assist you further!

Regards,
Itamar.