• Resolved ajones98

    (@ajones98)


    Hi there,

    I seem to be getting an issue with the plugin where I am trying to do a very basic custom search query on the frontend of my site. Please see the code below.

    <?php $args = array('s' => get_search_query()); ?>	
    <?php $query = new WP_Query($args); ?>	
    <?php while ($query->have_posts()) : $query->the_post(); ?>
    <?php the_title(); ?>
    <?php endwhile; ?>

    When this plugin is activated the custom search query returns no results, however as soon as I disable CPT UI everything works as it should.

    I have tried changing themes, disabling all plugins except CPT UI and nothing seems to be work. Is this a known issue? I don’t think that this is theme or plugin conflict related due to the tests I have made. The only thing I am yet to test is moving the hosting, else this looks like it is a bug within the plugin files.

    I appreciate any help and support you can give on this.

    Cheers
    Aaron

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    shouldn’t need to be doing anything so drastic as moving hosting for a general common query in WordPress.

    Theme changing isn’t going to help either, as that just changes which file holds the code making the same query.

    That said, the only thing sort of standing out to me is the variable naming, I’m wondering if $query is used as some sort of global in this area of the loading, and you’re possibly overwriting it. My first thing to try would be renaming that to something else.

    That said, this query isn’t even making use of a post type, so how CPTUI would be interferring somehow, if it indeed is, is very baffling. When it comes to code that’s run on the frontend, the only code that we have execute is just simply the registration of the saved post types/taxonomies. We don’t do anything with queries for content.

    Thread Starter ajones98

    (@ajones98)

    Hi There,

    I have done some more testing on this and got to the bottom of the issue.

    The problem was I had registered a taxonomy called ‘search_terms’ which interrupted the WordPress core search. I have had to rename the taxonomy and all is working well now!

    Thank you for your response!

    Many thanks
    Aaron

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Awesome to hear you got things working again, and interesting that that was the source.

    I’m curious if this is a slug that should be blacklisted. I don’t see it shown at https://codex.www.ads-software.com/Function_Reference/register_taxonomy#Reserved_Terms but I do see “search” and “terms” separately.

    First time this has come up as well, so maybe just best left alone until it becomes somehow a bigger issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin breaking ALL frontend search queries’ is closed to new replies.