Problem:
Client is trying to query child-pages using the post_parent parameter in custom code. When WPML is activated, where the query returns no values when there should be some.
Solution:
We recommend the following workaround:
1. Add this code to your theme's functions.php file:
add_filter('wpml_pre_parse_query', function($q){
if (empty($q->get('wpml_do_not_adjust_name'))) {
return $q;
}
$name = $q->get('name');
unset($q->query['name']);
unset($q->query_vars['name']);
add_filter('wpml_post_parse_query', function($q) use ($name){
$q->set('name', $name);
return $q;
});
return $q;
});
2. Then, in the WP_Query, pass wpml_do_not_adjust_name parameter as true, for example:
$args = array(
'wpml_do_not_adjust_name' => true,
'post_type' => $post_types,
'post_parent' => 59,
'name' => 'child-page-b',
'no_found_rows' => true, // used to improve performance.
'update_post_meta_cache' => false, // used to improve performance.
'update_post_term_cache' => false, // used to improve performance.
);
Please note that after making these adjustments, WPML will stop translating the slug to the secondary language, so it won't display the translated post in the second language. This is because you are passing the static slug in the query and do not want WPML to interfere with this.
For queries in different languages, adjust the
and
parameters to the translated versions of the parent and child pages, respectively.
We have escalated the case, but there is no clear ETA for it to be added in a near future release. You can use the above-mentioned workaround for the time being.
We also advise checking the WPML Hooks documentation for further customization.
If this solution is irrelevant to your case, either because it's outdated or not applicable, 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 the issue persists, please open a new support ticket.
