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.

Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.
Sun Mon Tue Wed Thu Fri Sat
- 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 -
- 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 -

Supporter timezone: Europe/Vienna (GMT+02:00)

This topic contains 2 replies, has 0 voices.

Last updated by jeffreyB-17 13 hours, 38 minutes ago.

Assisted by: Bigul.

Author Posts
March 31, 2025 at 1:55 pm #16879325

jeffreyB-17

Background of the issue:
I'm running into an issue with translated filters on the English archive page of a site built with JetEngine and WPML. Archive templates load fine in English, and taxonomy filters like Discipline and Course Duration work and return the correct posts. All Meta Fields are set to Translatable, and on translated single post pages, all field values (like weekday, age group, teacher, etc.) display correctly.

Symptoms:
Filters for Weekday, Age group, and Teacher show only partial values or none at all, or show values but selecting them returns no results. For Teacher, names are shown in the filter, but filtering returns nothing. The Meta Field keys are identical in both languages, and translations are correctly added in the WPML editor.

Questions:
Why do these translated Meta Field values not work in JetSmartFilters on the English archive page?
How can I make filters based on Meta Fields (select type, like weekday or age) work in both languages, without having to manually reassign the values in every translated post?

April 1, 2025 at 6:21 pm #16884302

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Welcome to the WPML support forum. I will do my best to help you resolve the issue.

We hope you are following the steps described in the following documentation to translate the JetEngine Elements.

hidden link

hidden link

hidden link

This may be related to the following known issue with JetEngine. So please try the workaround suggested there after a full site backup {mandatory} and make sure the issue exists or not.

https://wpml.org/errata/jetengine-components-are-not-translated-on-the-frontend/

--
Thanks!

Bigul

April 7, 2025 at 11:46 am #16904022

jeffreyB-17

I did all these things but still, some filters are not translating... Can you let an expert check this issue on my specific website ASAP? Because it's definitely not working properly this way.

April 8, 2025 at 5:53 am #16906771

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. Please fill in the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our privacy information sharing policies.

https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

hidden link

--
Thanks!

Bigul

April 8, 2025 at 3:37 pm #16910222

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates and login information. FTP credentials are not required for the time being.

This looks like a compatibility issue. Now, you are using a bit of an older version of JetElements and JetEngine. So we would like to make sure the issue exists with the latest versions or not. Refer to the attached image.

Therefore, please upgrade to the latest version of the plugins after a full site backup {mandatory}

--
Thanks!

Bigul

2025-04-08_21h00_09.png
April 9, 2025 at 7:21 am #16911650

jeffreyB-17

Good morning Bigul! I've updated the plugin (JetEngine). I deactivated the JetElements plugin since we don't use that one.

Can you please check again to fix this issue? Thanks for you kind help, I appreciate it.