jserrao/custom-search-acf-wordpress.php

I'm having an issue adding this to my functions.php file. I've copied and pasted it, entered my custom taxonomy = 'doctor' *line 97; and entered the custom search fields *line 17-23.

$list_searcheable_acf = array(
"last_name",
"first_name",
"title",
"specialties",
"city",
"state",

);

I would appreciate any help. Entering these kills the search function all together.

@willgeekforyou - can you post the code you used? I'll take a look.

How would this work with repeater fields?

@swade-fah: just add the slug of the field names into Step 1. The individual repeater components will be part of that field slug at the DB level.

@jserrao: Thank you for this, seriously! I had a plugin conflict with 'searchwp' and using your code instead worked perfectly (I credited you in the theme). All the best!

Thanks so much!

I made a small change to accommodate custom table prefixes.

Added $table_prefix = $wpdb->prefix; and then changed all the instances of wp_ to ".$table_prefix."

I'm a bit green to GIT and not sure how to properly share the change, but here it is:

function advanced_custom_search( $search, &$wp_query ) {
     global $wpdb;

     if ( empty( $search )) {
  return $search;
     }

     // 1- get search expression
     $terms_raw = $wp_query->query_vars[ 's' ];

     // 2- check search term for XSS attacks
     $terms_xss_cleared = strip_tags($terms_raw);

     // 3- do another check for SQL injection, use WP esc_sql
     $terms = esc_sql($terms_xss_cleared);

     // 4- explode search expression to get search terms
     $exploded = explode( ' ', $terms );
     if( $exploded === FALSE || count( $exploded ) == 0 ) {
  $exploded = array( 0 => $terms );
     }

     // 5- setup search variable as a string
     $search = '';

     // 6- get searcheable_acf, a list of advanced custom fields you want to search content in
     $list_searcheable_acf = list_searcheable_acf();

     $table_prefix = $wpdb->prefix;

     // 7- search through tags, inject each into SQL query
     foreach( $exploded as $tag ) {
         $search .= "
           AND (
             (".$table_prefix."posts.post_title LIKE '%$tag%')
             OR (".$table_prefix."posts.post_content LIKE '%$tag%')
             OR EXISTS (
               SELECT * FROM ".$table_prefix."postmeta
                WHERE post_id = ".$table_prefix."posts.ID
                  AND (";
   // 7b - add each custom post-type into SQL query
         foreach ($list_searcheable_acf as $searcheable_acf) {
           if ($searcheable_acf == $list_searcheable_acf[0]) {
             $search .= " (meta_key LIKE '%" . $searcheable_acf . "%' AND meta_value LIKE '%$tag%') ";
           } else {
             $search .= " OR (meta_key LIKE '%" . $searcheable_acf . "%' AND meta_value LIKE '%$tag%') ";
           }
         }
  // 8- Add to search string info from comments and custom taxonomies
  // You would need to customize the taxonomies below to match your site
          $search .= ")
             )
             OR EXISTS (
               SELECT * FROM ".$table_prefix."comments
               WHERE comment_post_ID = ".$table_prefix."posts.ID
                 AND comment_content LIKE '%$tag%'
             )
             OR EXISTS (
               SELECT * FROM ".$table_prefix."terms
               INNER JOIN ".$table_prefix."term_taxonomy
                 ON ".$table_prefix."term_taxonomy.term_id = ".$table_prefix."terms.term_id
               INNER JOIN ".$table_prefix."term_relationships
                 ON ".$table_prefix."term_relationships.term_taxonomy_id = ".$table_prefix."term_taxonomy.term_taxonomy_id
               WHERE (
              taxonomy = 'your'
      OR taxonomy = 'custom'
      OR taxonomy = 'taxonomies'
      OR taxonomy = 'here'
            )
                AND object_id = ".$table_prefix."posts.ID
                AND ".$table_prefix."terms.name LIKE '%$tag%'
             )
         )";
     }
     return $search;
 }

@bmdinteractive, thanks for the update. In git parlance, you are issuing a pull request. Gists are a bit weird in how you iterate on them relative to git/github proper. You can't really do pull requests in gists so I just updated my code block to include your work and referenced your contribution in heading block.

@MelanieMenard - thanks.

This works like a charm, awesome job jserrao!
I have a few suggestions to update your comments though (I suspect these are still from earlier iterations of the gist).

• On line 13 it says to define a list of ACF Fields in list_searcheable_acf(), but inside the function you ask for custom post types instead.
• Line 14 refrences to step 8 to include taxonomies, but this happens in step 10

@Sjouw - thanks, I updated those commenting errors, fixed whitespace issues and republished.

Current version returns SQL statement including the php comments ("// 9- Adds to $search DB data from custom post types" for example).

Also, whenever $search is used in a comment it is substituted with the value of $search (since it's inside a string).
Because of this, // 10- Adds to $search DB data from comments
generates // 10- Adds to AND ( (wp_posts.post_title LIKE '%search%') OR (wp_posts.post_content LIKE '%search%') // 9- Adds to DB data from custom post types OR EXISTS ( SELECT * FROM wp_postmeta WHERE post_id = wp_posts.ID AND ( (meta_key LIKE '%field%' AND meta_value LIKE '%search%') DB data from comments

When removing the comments this gist works as expected, many thanks!

Also, this gist removes searching in wp_posts.post_excerpt, the default $search coming into the filter is
AND (((wp_posts.post_title LIKE '%search%') OR (wp_posts.post_excerpt LIKE '%search%') OR (wp_posts.post_content LIKE '%search%')))
which gets overwritten by
AND ( (wp_posts.post_title LIKE '%search%') OR (wp_posts.post_content LIKE '%search%')

I've made the above changes in this fork: https://gist.github.com/fiskhandlarn/f6f86c99e59f62d72ac2ce10be12dc1a
(together with some speed enhancements for non-repeater fields)