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
- 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 10:00 – 17:00 -
- 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 18:00 – 19:00 -

Supporter timezone: Asia/Kathmandu (GMT+05:45)

This topic contains 19 replies, has 1 voice.

Last updated by Shekhar Bhandari 1 month ago.

Assisted by: Shekhar Bhandari.

Author Posts
January 5, 2026 at 5:11 pm #17704832

irenek-4

don't close ticket, I am waiting for a reply, thanks

January 5, 2026 at 6:53 pm #17705156

irenek-4

well I think it's not theme's or elementor's issue. Something is happening with the translation.
You have told me to set the property_type to copy and update properties, which I did.

Also you told me to create labels like this:
"appartment : Apartment
detachedhouse : Detached House
maisonette : Maisonette
office : Office
plot : Plot
Once this saved on ACF field preferences, you have to update all the properties accordingly and it should work."
But it doesn't work.

The problem looks more weird and it looks like we are returning to previous problems and solutions. To understand me look at this property for example:
hidden link

In english its' property type is set to PLOT, but in greek when you edit the greek translation, the property type is not copied but it is set to Διαμερισμα (apartment) instead of Οικόπεδο (plot). If I try to correct the property type in greek translation (edit page) then the properties external features are gone and I have to go again to the english translation to trigger somehow the greek translation and resave (and some times the translated excerpt is gone and needs retranslate)
you can see that similar issue was resolved like this from previous supporter hidden link

I am really confused and frustrated because I don't know which is the solution to follow in order for my site to be functional. Please help

January 6, 2026 at 3:42 am #17705620

Shekhar Bhandari
WPML Supporter since 03/2015

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello there,

Until the theme developer provides an update if the acf choices are supported with labels or values, I would suggest you to perform the below steps:

- Set the property_type to translate
- Change the choices to the previous state with only values
- Set the property_type for the original and translations manually for each properties.

Let me know if this helps.

Thanks

January 14, 2026 at 5:23 pm #17730602

irenek-4

Hello,
The theme developer who searched the website to see what is happening replied:

"By analyzing the "main" language, I noticed that, in a strange way, some of the apartment fields are saved or stored differently from others. I have used both standard methods to retrieve the meta key values for the apartments from the database — get_post_meta($post_id, $item['select_field'], true) and get_field($item['select_field'], $post_id). Both methods return different meta key values for the same apartment field "property_type" in the main language: sometimes it is "Apartment" and sometimes "appartment".

I suppose that because of this inconsistency, there are issues with the second language as well. Could you please provide more details on how you initially created those custom fields, which resulted in the different meta key values for the apartment field?

Please also recheck your property posts, correct the selection of the respective custom field, and resave them so I can verify again on my end. Additionally, kindly provide access to your database management tool (phpMyAdmin or similar) so I can review those fields at the database level as well."

and after getting access to the database replied:

"I have checked the database and I can clearly see that the meta keys and values are saved there exactly in this strange "messed up" way. The theme itself outputs and displays the fields on the frontend exactly in the same way as it is stored in the database, so there is no issue with this. The problem is with how these posts and their fields have been created and assigned.

I can recommend you to create a completely new post from scratch and assign the fields and translations manually as suggested. After that we can check what is happening with the meta keys / custom fields and their translations in the backend and in the database. If everything will be fine, I suppose the only way would be to recreate the "weird" posts from the scratch. "

MY FINAL WORKAROUND:
after trying to create a post from scratch, the problem persisted. So I decided to use another method: I removed the field property_type from properties posts so it should not be visible, and set property_type to copy. Now it works, the search fields work correct and when I choose for example "plot" it returns plots and not apartments. The exact result happens and in the translation. So it works!

I don't know what happened to the database and why everything got messed like that.

January 15, 2026 at 3:40 pm #17734694

Shekhar Bhandari
WPML Supporter since 03/2015

Languages: English (English )

Timezone: Asia/Kathmandu (GMT+05:45)

Hello,

Thank you for the details.

So, it’s working properly now with help from the theme developer? However, I’m not sure I fully understand the workaround you mentioned.

I look forward to your reply.

Thanks.

The topic ‘[Closed] Translation problem, sorting doesn’t work in translated language’ is closed to new replies.