Skip to content Skip to sidebar

Home › Support › English Support › [Resolved] Split: Highlights section

[Resolved] Split: Highlights section

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

Problem:
The client reported an issue where the 'Highlights' section appeared correctly in the backend of the translated property but not on the front end. The translated template was not fetching the correct taxonomy, and there was confusion about handling settings for dynamic fields and images in the translated template.
Solution:
We reviewed the translated template and corrected the source selection for the taxonomy. This resolved the display issue on the front end. However, the custom fields related to the 'Listing Source' and 'Query' values were not automatically copying from the default language due to their absence in the WPML → Settings → Custom Fields Translation. We suggested contacting the plugin author to inquire about setting these fields to Copy for WPML compatibility or to include the necessary WPML configuration in a future plugin update. If further assistance is needed, we recommend opening a new support ticket. Additionally, it's advisable to check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.

If this solution does not resolve your issue or seems irrelevant, please do not hesitate to contact us for further assistance by opening a new 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.

This topic is split from https://wpml.org/forums/topic/jet-filters-are-copied-translated-but-no-content-inside-no-settings-or-texts-are-copied-over-just/

Tagged: 

This topic contains 3 replies, has 0 voices.

Last updated by Dražen 1 month ago.

Assisted by: Dražen.

Author Posts
June 9, 2026 at 6:01 am #18088756

dennisB-32

"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?
June 9, 2026 at 6:26 am #18088795

Dražen
Supporter

Languages: English (English )

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

Hello,

I checked the issue and found that in the translated template, the source was not selected correctly (please see the attached screenshot).

After correcting this, the content appears as expected.

I also tried to locate the custom fields related to this setting so I could configure them to use the Copy translation preference, but I was unable to find them. The only related field I could identify was `query_id`.

You may want to contact the plugin author and ask them either:

- which custom fields should be set to **Copy** for WPML compatibility, or
- to include the necessary WPML configuration in a future version of the plugin so these settings are copied automatically during translation.

Let me know if this helps and if you need any further help from our side.

Regards,
Dražen

Edit-Item-“Warehouse-Characteristics-Listing-For-Single-Property-Page”-‹-Spaace-Mexico-—-WordPress-06-09-2026_08_18_AM.jpg
June 9, 2026 at 1:07 pm #18090525

dennisB-32

Amazing. Looks like highlights are working perfectly now. Thank you.

Not sure which custom fields we're talking about here. Sorry.
Do you see anything that is missing from working regarding this matter?
June 9, 2026 at 2:14 pm #18090926

Dražen
Supporter

Languages: English (English )

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

Hello,

I was referring to the custom fields that store the Listing Source and Query values selected in the sidebar settings. These values were missing from your translated template.

As mentioned earlier, I edited the translated template in the secondary language and manually selected the correct Listing Source and Query values, which is why it is now working correctly.

For these values to be automatically copied from the default language to the translation, we would normally set the corresponding custom fields to "Copy" under WPML → Settings → Custom Fields Translation. However, I cannot find these fields there, which suggests they may be stored differently by the plugin or builder used for this template.

If you'd like, I can try to reproduce the issue and escalate it to our 2nd Tier team for investigation and contacting author. However, I believe it would be faster to first check with the plugin author whether this part is officially supported for translation or if these settings are expected to be configured manually on translated templates.

Best regards,
Dražen