Filter Options Not Working on Translated Archive Page (JetEngine Custom Fields)

This thread is resolved. Here is a description of the problem and solution.

Problem:

The client is experiencing issues with translated filters on the English archive page of a site built with JetEngine and WPML. Specifically, filters for Weekday, Age group, and Teacher either show partial values, no values, or the values do not return the correct results when selected. The Meta Field keys are identical in both languages, and translations are correctly added in the WPML editor.

Solution:

To resolve the issue with the Weekday filter, we:
1) Changed the Weekdag field ID of the Course post type from 'weekdag' to 'weekdag_course'.
2) Updated the query variable of the Weekdag filter from 'weekdag' to 'weekdag_course'.
3) Set the 'weekdag_course' field to Copy in WPML>>Settings>>Custom Fields Translation.
4) Reverted the translations of Weekdag field option values in String Translation — the values should be the same in both languages (e.g., "woensdag").
5) Updated the Weekdag field values for the first nine Course posts.
6) Updated the translations for those posts.

For other filters like Age, Daypart, Duration, and Teacher, follow similar steps. Ensure that the field settings are adjusted to either 'Copy' or 'Translate' as appropriate, based on whether the field values need to be the same or different across languages. You do not need to rename all custom field IDs unless they conflict with others.

For detailed guidance on translating custom fields, visit WPML documentation on translating custom fields.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.

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.

Tagged: Bug

This topic contains 4 replies, has 0 voices.

Last updated by Bigul 1 month 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 WPML Supporter since 01/2013 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 WPML Supporter since 01/2013 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 WPML Supporter since 01/2013 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
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.
April 10, 2025 at 6:08 am #16916576
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for the updates. I had a quick check, but this requires further checking. So please allow me to make a copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the issue without affecting your live site. -- Thanks! Bigul
April 11, 2025 at 8:01 am #16921457
jeffreyB-17	Sure Bigul, do everything so we can fix it all ASAP.
April 11, 2025 at 5:13 pm #16923929
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for the permission. I made a copy of the site, we will debug it further and get back to you as early as possible. Please wait. -- Thanks! Bigul
April 15, 2025 at 4:07 am #16931515
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Sorry for the late response becuase of the holidays. The issue is existing after the initial checks, so consulting with our team for an expert opinion now. We will get back to you as soon as possible. Please wait. -- Thanks! Bigul
April 15, 2025 at 7:10 am #16931864
jeffreyB-17	Hi Bigul, I hope our site won't take too long to fix because we want to finish the project with our client and now we can't... How long do you think it'll take? Will the holidays be a huge problem? Thanks! Jeffrey
April 15, 2025 at 7:24 am #16931988
jeffreyB-17	Now it takes pretty long after each response, we're already talking from the 31st of March and it's now more than two weeks later. We haven't even made any steps yet (what I know about). Please prioritize my problem because I'm a client for a long time already.
April 15, 2025 at 2:18 pm #16934582
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for the updates. Unfortunately, the possible workarounds are not helping in this case. We are still working on it and will get back to you as soon as possible, most likely by tomorrow evening. Please wait. -- Thanks! Bigul
April 16, 2025 at 7:37 am #16937094
jeffreyB-17	Hi Bigul, thanks for your reply and I'll wait for your solution. Hope we can get this done ASAP.
April 16, 2025 at 10:20 am #16937745
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for your kind understanding. The ticket has now been forwarded to our second-tier team. We will get back to you as early as possible. Please wait. -- Thanks! Bigul