This thread is resolved. Here is a description of the problem and solution.
Problem:
The client experienced issues with the translation of filter labels in a bilingual website (Spanish to English). The labels were not saving correctly, and the translated values were not appearing on the site.
Solution:
We recommended manually adjusting the translated filter labels. However, upon further investigation, it was discovered that the JetFilters custom field translation settings had been modified incorrectly, setting many fields to "Copy". We compared these settings with a default installation and adjusted them on a staging site. We advised the client to apply the same settings from the test site to their production site by navigating to WPML → Settings → Custom Fields Translation and selecting 'Show systems fields'.
If this solution does not resolve your issue, or if it 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 persist, please open a new support ticket at WPML support forum for further assistance.
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: Exception
This topic contains 13 replies, has 1 voice.
Last updated by Dražen 1 month ago.
Assisted by: Dražen.
| Author | Posts |
|---|---|
|
June 6, 2026 at 7:25 pm
#18085306
|
|
|
June 7, 2026 at 12:25 am
#18085384
|
|
|
I changed some settings to 'Duplicate' instead of 'Translate' and it worked. But I still have to translate manually inside filters. Why? Also, some of my listings are not working on EN layer. Why can't it just be a 100% mirrored version of ES layer? ES: hidden link |
|
|
June 8, 2026 at 6:22 am
#18086123
|
|
|
Hello, Seems this is expected behavior and comes from how JetSmartFilters integrates with WPML. Please refer to the official JetSmartFilters multilingual guide: Regarding the listing that is missing data on the English version, WPML can only mirror content that is configured to be copied. If specific custom fields are set to translate instead of copy, the translated version may not display the same content automatically. Also note that listing needs to exist in that language (duplicate or translated) to work fine. Please let me know if this helps and if you have any other questions or doubts, and I will be glad to help. Kind regards, |
|
|
June 8, 2026 at 12:42 pm
#18087342
|
|
|
Hi Dražen Unfortunately, I seem to have run in to a wall with this site, as I've tried everything... It's a bit of an emergency, as the site cannot be published without the EN layers working. Any chance you can help me check on the issues? Best, |
|
|
June 8, 2026 at 12:56 pm
#18087382
|
|
|
Hi Dennis, Sure, no worries. Please share admin access to the site, and let me know exactly which issue you'd like me to check. Is it the missing "Highlights" data on the English translations, or you mean other EN-layer issues? Once I have access, I'll take a closer look and see what I can find. Best regards, |
|
|
June 8, 2026 at 1:59 pm
#18087718
|
|
|
Hello, You have mentioned multiple issues in this ticket. Please note that we generally handle one issue per ticket to keep troubleshooting clear and efficient. If you need further assistance with items 2 and 3, I will open separate tickets for them and help you investigate each one individually. 1. Regarding the visual filter names/fields, could you please clarify how these are being created? Where are these values managed on the site? For example, if you want to change "Renta" to something else, from which section are you currently editing those values? 2. I have fixed the gallery issue, and it should be working correctly now. As for the Highlights section, it appears to be working on the translated property itself just fine, in the backend. However, it seems that the translated template may not be configured to fetch the correct taxonomy. Please edit the translated template "Warehouse Characteristics Listing For Single Property Page" and verify that the correct source/taxonomy is selected. - hidden link I also checked the default-language template, but I couldn't find any output there either, so I'm not entirely sure what the intended configuration should be. 3. These are user meta fields. To make those translatable, you'll need to follow our documentation: Please review the guide and let me know if you need any further assistance. Kind regards, |
|
| June 8, 2026 at 2:31 pm #18087917 | |
| dennisB-32 |
Dražen, thank you so much. I truly appreciate you help here!! "1. Regarding the visual filter names/fields, could you please clarify how these are being created? Where are these values managed on the site? For example, if you want to change "Renta" to something else, from which section are you currently editing those values?" I edit those values in this filter: hidden link -- Gallery works perfectly now. Thank you! What did I do wrong? -- "As for the Highlights section, it appears to be working on the translated property itself just fine, in the backend. However, it seems that the translated template may not be configured to fetch the correct taxonomy. Please edit the translated template "Warehouse Characteristics Listing For Single Property Page" and verify that the correct source/taxonomy is selected." I'm not sure I understand this. Wouldn't it be possible to add settings to handle this, instead of manual translation of tax in EN template? I'm afraid that site will not stay 100% correct on translated layers, if they don't all just mirror default language. It uses a dynamic image with source "bodegas image" and a dynamic field with object field "Term name". Can you help get this one working? -- "3. These are user meta fields. To make those translatable, you'll need to follow our documentation:" I followed the documentation, and the user type 'Vendor' is already added. However, I cannot find the domain for this, as shown in documentation. Can you help see what I'm doing wrong? Sorry for all the tasks. Hoping you can get me to the finish line. New threads created by Dražen and linked to this one are listed below: |
|
June 9, 2026 at 6:10 am
#18088761
|
|
|
Hello, thanks for getting back. I have splited other 2 issues in new ticket: - https://wpml.org/forums/topic/split-highlights-section/ As for Visual filters, you need to manually adjust translated filter labels, and it should work fine. For example I have changed Rent / Sale label in EN fiter and it shows fine in front. - hidden link Unfortunately for Jetengine as it says in their documentation, you might need to check / adjust some values / translate some things manually for it to work correctly. That refers to filters etc you are buidlign as it does also for templates where you are selecting them. Regards, |
|
|
June 9, 2026 at 4:31 pm
#18091340
|
|
|
June 10, 2026 at 6:15 am
#18091942
|
|
|
Hello, Thanks for getting back to me. I checked the issue and noticed that when I change a label in the English filter, save it, and then refresh the page, the label reverts back to its previous value. This suggests that the label translations are not being saved correctly for some reason. Would it be okay if I temporarily disable plugins, switch themes if needed, and update the plugins as part of the troubleshooting process? If you'd prefer, you can also try this yourself, just to be on the safe side. Otherwise, let me know and I'll proceed with the testing. Best regards, |
|
|
June 10, 2026 at 4:43 pm
#18094223
|
|
|
Of course. Please help me set everything back to normal after testing. Alternatively, you can also test on this cloned site that I can delete when we're done testing. hidden link |
|
|
June 11, 2026 at 6:06 am
#18095171
|
|
|
Hello, I checked the issue on the staging site and also tried the setup on a clean test installation. What I found is that on your website, someone has modified the JetFilters custom field translation settings and set many of the fields to "Copy". After comparing the configuration with a fresh installation, I found that several of these settings differ from the defaults. I adjusted the relevant fields on the staging site, and after doing so I was able to translate the labels successfully. To be honest, I would not recommend changing a large number of custom field translation preferences without fully understanding how they are used by the plugin. Since many of these settings were modified, it is possible that other functionality may also be affected. If possible, I would suggest checking with the person who originally changed these settings and reviewing whether other fields were intentionally modified. For the label issue specifically, please compare the custom field translation settings between the test site and your production site: On test site go to WPML → Settings → Custom Fields Translation > Show systems fields ( hidden link) Then apply the same settings as on the test site to your website and it should be fine. I have confirmed that this works on the staging site. Regards, |
|
|
June 14, 2026 at 2:41 am
#18101749
|
|
|
Thank you, Dražen! This was great help. Please keep the test site available for a little longer, and I'll make sure everything is working next week. Appreciate you! |
|
|
June 15, 2026 at 6:06 am
#18102773
|
|
|
Hello, sure, no problem. Let me know how it goes and if any doubts or issues. Regards, |
|




