Skip to content Skip to sidebar

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

Problem:
The client is experiencing issues with JetSmartFilters not displaying correctly on the French version of their 'Find Jobs' page, despite appearing correctly in Elementor. The filters sometimes show in English or French but do not render correctly on the live page.

Solution:
We recommend the following steps to resolve the issue:
1. Increase the WordPress memory limit to at least 256MB by adding

define('WP_MEMORY_LIMIT', '256M');

in the 'wp-config.php' file before the '/* That's all, stop editing! Happy blogging. */' line.
2. Configure custom field translation for filter data:
- Go to WPML → Settings.
- In the 'Custom Fields Translation' section, locate the custom fields for 'Vacancy Type job', 'Vacancy format', 'Job Language', and 'Vacancy language requirement', and set their translation preference to 'Copy'.
3. Translate filter options:
- For taxonomy-based filters, use WPML → Taxonomy Translation, select the relevant taxonomy, and translate each term.
- For string-based filters, use WPML → String Translation to translate the filter options.
4. If issues persist, consider changing the taxonomy settings in WPML → Settings → Taxonomy Translation to 'Translatable – use translation if available or fallback to default language' and refresh the page.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, 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 problems continue, please open a new support ticket at WPML support forum.

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: 

This topic contains 6 replies, has 1 voice.

Last updated by Carlos Rojas 6 months, 1 week ago.

Assisted by: Carlos Rojas.

Author Posts
October 24, 2025 at 3:07 am #17514381

Kim

Background of the issue:
I am trying to display the translated JetSmartFilters (Select filters) correctly on the French version of my 'Find Jobs' page. The English version is available at hidden link and the French version at hidden link. The translations of the pages are now being handled by WordPress, not the Advanced String Translation Editor.

Symptoms:
The translated Select filters (Vacancy Type job, Vacancy format, Job Language, and Vacancy language requirement) are not showing on the front end of the French page. In Elementor, the French version of the filters appears in the sidebar, but they don’t display properly on the front end. Sometimes the filter options appear in either English or French, but they never render correctly once the page is live.

Questions:
Why are the translated Select filters not displaying on the French version of the page?
How can I ensure the filters function properly on the front end?

October 24, 2025 at 2:28 pm #17517059

Kim

Following up on my previous ticket, I wanted to share more context on what I did to be able to translate the Smart Filters, maybe the errors I was seeing are related to this issue.

After trying to use the advanced string translation editor for French JetSmart Filters, all of these translation jobs got stuck with the message “French translation assigned to local translator.” The translations were completed on the back end but showing the "wheel", and they were not showing on the front end.

I decided to remove the translation jobs that were stuck from the job board, and tried translating the filters manually (by creating the french version separately and then assigning the translated version to english), I often got a critical error while saving, but after refreshing the page, the filters showed as saved and properly linked. So the translations are now complete.

Here are the most relevant error logs (according to ChatGPT, i put the error logs there to try to understand what went wrong):

[24-Oct-2025 00:40:56 UTC] WordPress database error Commands out of sync; you can't run this command now for query
SELECT t1.language_code as languageCode, t2.element_id as elementId
FROM wp_icl_translations as t1
INNER JOIN wp_icl_translations as t2 ON t1.trid = t2.trid
WHERE t1.element_id = 13993
AND t1.element_type = 'post_jet-smart-filters'
AND t1.element_id != t2.element_id
AND t2.source_language_code IS NULL
made by shutdown_action_hook, do_action('shutdown'), ... ItemUpdateEventListenerAdapter->getItemByPost, ... Links\Repository->get

[24-Oct-2025 00:40:56 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT meta_id FROM wp_postmeta WHERE meta_key = '_wpml_word_count' AND post_id = 13991 made by shutdown_action_hook, ... update_post_meta, update_metadata

[24-Oct-2025 00:40:56 UTC] WordPress database error SHOW FULL COLUMNS FROM `wp_postmeta` made by shutdown_action_hook, ... ItemWordCountService->calculatePost

____

Hopefully this helps!
Thanks

October 24, 2025 at 10:10 pm #17517947

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

It seems the minimum requirements on the server are not met:
https://wpml.org/en/home/minimum-requirements/

Could you please increase the WordPress memory limit (WP Memory Limit) to at least 256 MB? WPML requires at least 128 MB.
Your current values ​​are:

PHP Memory Limit 512 MB
WP Memory Limit 40 MB

To do this, you need to connect to your website's server and open the wp-config.php file in a text editor. The file is located in the WordPress root directory.

Add this code to the wp-config.php file to increase WordPress memory:

define ('WP_MEMORY_LIMIT', '256M');

Add this just before this comment:

// That's all, stop editing! Happy blogging.

The current values ​​can be viewed under WPML > Support > WordPress.

These settings can be restricted directly by your hosting provider. Therefore, I recommend contacting them and asking them for assistance.

---

After the limit has been adjusted, edit the original JetSmartFilters in WordPress, then save them again.

This will update the translation status and create new translation jobs.

Then make sure to update their translations to 100% using the WPML Translation Editor.

If this does not solve the issue, please let us know.

Best regards
Andreas

October 24, 2025 at 10:11 pm #17517948

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Additionally, please take note of the following known issue:
https://wpml.org/errata/jetsmartfilters-elementor-widgets-strings-not-translatable/

October 25, 2025 at 1:37 am #17518042

Kim

Hi Andreas,

Thanks for your reply. I updated the PHP and WP memory limits as suggested and also reviewed the known issue you shared, but unfortunately, nothing changed. The translated JetSmartFilters still don’t display correctly on the French version of the page.

What would you recommend as the next step?

Thanks

October 25, 2025 at 1:54 am #17518043

Kim

Hi Andreas,

I wanted to share an update on my testing.

I noticed that in WPML → Settings → Taxonomies Translation, all my JetEngine taxonomies (Vacancy Type, Format, Language, etc.) were set to “Translatable – only show translated items”. The only taxonomy that was showing correctly on the front end was “Vacancy Location,” which was set to Not translatable.

As a test, I changed just one taxonomy (Vacancy Type) to “Translatable – use translation if available or fallback to default language”, saved the changes, and then refreshed the French version of the page. After doing that, all the translated filters started displaying correctly — not only the one I changed.

It seems that switching one taxonomy to the fallback mode affects the way WPML handles all taxonomy queries from JetSmartFilters. I’ve attached a screenshot of my taxonomy settings for reference.

Could you please confirm if this behavior is expected, or if it points to a deeper issue with how JetEngine taxonomies interact with WPML?

Thanks!

Screenshot 2.png
Screenshot 1.png
October 27, 2025 at 10:03 am #17521050

Carlos Rojas
WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

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

Hello,
My name is Carlos, and I will continue working on this ticket

Yes, it is possible that the query used to show the taxonomies gets updated when you change the configuration in WPML -> Settings -> Taxonomy translation and make it work correctly.

After you changed the configuration for 'Vacancy Type', did the problem disappear?