Skip Navigation

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

The client uses the legacy Views editor to create a View to display taxonomy terms.

The texts from the View are translated via String Translation, but on the translated page the View query returns no results, unlike in the default language where all of the taxonomy terms are shown.

The problem was that the output of the View is ordered by a taxonomy custom field, and in WPML settings that term field is set as Do not translate. That means that in the secondary language the terms have no values for that custom term field.

It is a quirk of WordPress that when ordering by some thing, and potential results that have no value for that thing will be excluded from the results.

The solution is to copy or translate the custom term fields.

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 contains 14 replies, has 2 voices.

Last updated by matthewL-3 2 months, 4 weeks ago.

Assisted by: Nigel.

Author Posts
February 26, 2024 at 12:09 pm #15344007


I've figured it out need to resave each category, thanks a lot for your help with this!

matthewL-3 confirmed that the issue was resolved on 2024-02-26 12:09:51.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.