Do not hard code a value in the search field. You will get a lot of nonsense searches because people do not expect that they have to clean up the field before they can actually type something into it. They will just type and hit enter. Alternatives: Use the placeholder attribute. You can style it … Read more
I think, I found a solution by gmazapp. At least, it worked for me. It’s a little hacky-ish, but does the job pretty good, so I’m sharing it, if someone will be looking for the same thing in the future.
Somebody shoot me please… Since this is the first theme I developed I didn’t know that I needed a search.php for my form to work! Anyway I created search.php and inserted The Loop, after I did that I’ve copied that file inside my theme and my search form worked like a charm!! Hope this will … Read more
You’ll have to write a custom WP_Query in search.php. Also since you want to search in post_title + categories, you might have to run 2 separate queries and merge results of them into 1. Something like: $q1 = get_posts(array( ‘post_type’ => ‘post’, ‘post_status’ => ‘publish’, ‘posts_per_page’ => ‘-1’, ‘s’ => get_search_query() )); $q2 = get_posts(array( … Read more
I’m afraid there is no function in WP core that will get number of unique categories based on given list of posts… So let’s take a look at your code first… There are some problems in it… There is no need to use typical loop in here – it causes many operations in background (setting … Read more
You can see product categories on the right sidebar below Update / Publish section. If you cant see the categories go to the top of the page on the right find & click Screen Options and check Product Categories
Right after posting, I learned a couple things, most importantly, that url encoding is done differently for paths and queries and one of our search sources treats the search query as a path, so I had to use rawurlencode for the path; and urlencode for the others. This is why I was receiving inconsistent results … Read more
You are looking for pre_get_posts. This action is run between the composition of a (search) query and the actual query, to allow you to change the query. So, it would allow you to intercept banned keywords like this: add_action( ‘pre_get_posts’, ‘wpse338558_intercept_banned_keywords’ ); function wpse338558_intercept_banned_keywords ($query) { $banned = array (‘word1′,’word2′,’word3’); if (in_array ($query->query_vars[‘s’], $banned)) $query->s=””; … Read more
I would recommend using content-{posttype}.php method, where you only have HTML markup, template tags for posts or custom post types and leave loops outside of those files. See Twenty Eleven for more detailed example. After this change you can easily modify search.php and include specific content markup based on post type. if ( have_posts() ) … Read more
The problem in this case is the name of the post type, action. WordPress core uses the query var action for its own purposes, so this has created a conflict somewhere within the code. The solution is to rename the post type to something unique to remove the conflict.