If $input_terms is the input array of term slugs, then you should be able to use (if I understand the question correctly):
$property = [
'post_type' => 'properties',
'paged' => $paged,
'tax_query' => [
[
'taxonomy' => 'features',
...
Hmmm... maybe I didn't put enough into the question to make it understandable - I have added to the question now. All I want to do is $_GET the URL; check if there is features in the search query and if there is return result depending on that query. However if there are 2 terms in the query only return the Properties with both terms
As a debug step, just use $input_terms = [ 'term_one', 'term_two' ] and make sure the $property array here above returns correct query results. What happens then? @CoderSte
So I've done a var_dump to make sure the query works and it seems to be correct. As for adding in the terms manually to $input_terms I have done that and I still get the result I am getting now with no change
I just tested this and it seems to work as expected on my vanilla install. I only get posts that are assigned to all terms in our $input_terms array. What does your SQL query look like? @CoderSte
The SQL of the query that is fed with the $property arguments. From your dump it looks like your tax_query is not an array of arrays. Try to copy the array structure I adjusted in my answer. @CoderSte
Hmmm... Basically I am making a site for a client like a real estate so there's a lot of different queries for different things - I have a feeling that might be the problem. Question is can that cause problems?
I am using $wp_query = new WP_Query - I think that might be the problem
What you mean by that? I'm still pretty new to like Custom Post Type with queries. I used to just make standard custom themes for clients nothing this big at all
I finally got it working, but not with the code in my question. I totally scrapped that whole idea and restarted going in a new direction.
NOTE:
If anyone are ever able to sort out the issues in my question, feel free to post an answer. Also, if you have any other solution, also feel free to po...
I think it's this one ;-) It's an interesting puzzle there he was trying to solve, but I just wanted to mention this approach ;-)
but good luck with the probject
and this classic regarding pagination for sub-quries:
The Problem
By default, in any given context, WordPress uses the main query to determine pagination. The main query object is stored in the $wp_query global, which is also used to output the main query loop:
if ( have_posts() ) : while ( have_posts() ) : the_post();
When you use a custom quer...
(overrding the main query object reminds of how the problematic query_posts work, so you might be aware of that too)
The Problem
By default, in any given context, WordPress uses the main query to determine pagination. The main query object is stored in the $wp_query global, which is also used to output the main query loop:
if ( have_posts() ) : while ( have_posts() ) : the_post();
When you use a custom quer...
Discussion between birgire and CoderSte
Discussion between birgire and CoderSte