After further testing, the problem was found to be caused by another filter, posts_where, which was registered to support searching also in custom fields, and that’s why only searching is affected. Originally it generates something like this, so if the OR statement returns true (when one of the custom fields includes foo), that post will … Read more
OK, After a lot of trial and error and asking around I managed to finally get a working solution. Thought I would post it here for those that are trying to fix a similar problem in the future. Filter 1: posts_join creates a left join on all queries to link up the postmeta table. Its … Read more
It will be good to know how you implement your code in header.php. You can try to move some condition to not affect all query? function my_pre_get_posts( $query ) { if ( is_admin() || ! $query->is_main_query() ) return; if ( is_post_type_archive( ‘propiedad’ ) ) { Becomes function my_pre_get_posts( $query ) { if(!is_admin()){ if ( is_post_type_archive( … Read more
Have a look at the WordPress Documentation available here, you’ll be able to do what you want to do by using two hooks: https://codex.wordpress.org/Making_Custom_Queries_using_Offset_and_Pagination Unfortunately, many developers find out that hard way that setting an offset value in their custom WordPress queries has the nasty and potentially serious side-effect of breaking pagination. There is a … Read more
You can add a custom tax_query to your filter, and pass the search query to it: function searchfilter($query) { if ($query->is_search && !is_admin() ) { $s = $query->get( ‘s’ ); $query->set(‘post_type’, [ ‘lesson’, ‘series’ ] ); $query->set( ‘tax_query’, [ [ ‘taxonomy’ => ‘your-taxonomy’, ‘field’ => ‘name’, ‘terms’ => $s , ] ] ); } return … Read more
i had a similar issue, where i wanted to show different subcartegories inside a main category shoes men shoes men women shoes women so inside shoes i wanted to show both men and women shoes whilst non of these items should be required to be in category shoes.. your tax_query might be correct but you … Read more
You are stepping on a query mine. It is easy to assume that: You can change query. Parameters are well defined. So by changing of parameters you can achieve desired results. In reality there are plenty of query parameters, touching which leads into horrible dead ends. WordPress is engineered to query and show posts which … Read more
Use the widget_posts_args filter add_filter(‘widget_posts_args’, ‘wpsites_modify_recent_posts_widget’); function wpsites_modify_recent_posts_widget($params) { $params[‘post_type’] = array(‘post’, ‘$post_type’); return $params; } Source
So, it turns out my hunch was correct and the solution is to add some rewrite rules. Here’s what I added: function owr_blog_rewrite( $rules ) { return [ ‘notes/topic/([^/]+)/?$’ => ‘topic=$matches[1]’, ‘notes/topic/([^/]+)/page/([0-9]+)/?$’ => ‘topic=$matches[1]&paged=$matches[2]’, ] + $rules; } add_filter( ‘rewrite_rules_array’, ‘owr_blog_rewrite’ ); Everything works as expected now
Not sure exactly why, but by adding another filter using the meta_query it all started working. I now only get posts in my custom post type archive that do not have the project_update field set and are ordered by project_status. This is what I was after. $meta_query = array( array( ‘key’=>’project_update’, ‘value’=>’1’, ‘compare’=>’!=’, ) ); … Read more