• I’ve come across a bug.

    A client’s site uses a few custom post types, with a custom taxonomy associated with one of those post types. Basically, imagine you have a taxonomy called ‘custom-tax’, which is associated with a custom post type called ‘custom-post-type’. Without The Events Calendar activated, the following type of URL is returning the correct results (where custom-tax is the name of the taxonomy and taxterm is the term queried):

    http://example.com?custom-tax=taxterm

    With the plugin activated, it’s returning no results. The reason is that the Events Calendar is changing the post types that the query uses.

    Without the plugin activated, the post_type bit of the WHERE clause is as follows:

    AND wp_posts.post_type = 'custom-post-type'

    With the plugin activated:

    AND wp_posts.post_type IN ('post', 'tribe_events')

    Let me know if you need any more information.

    Cheers,
    Eric

    http://wordpress.org/plugins/the-events-calendar/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thanks for reporting Eric, I’ll pass that on to the team to evaluate.

    Hi Eric: we can’t replicate this in an otherwise “plain vanilla” installation, after registering a new post type and taxonomy for the purpose.

    Is it possible something else is at work in the background here? Could there be any further query manipulation or other changes to the way WordPress queries for posts in place by whatever code is managing the particular custom post types/taxonomies you are using?

    Thread Starter Eric Daams

    (@ericdaams)

    Not that I’m aware of, though there may be some other factor I haven’t thought of. This happening on the same site with two separate themes, so likely not theme related. Possibly something plugin related, but without digging further I can’t really say.

    It’s interesting though that the same thing happened with bbPress, and was also reported in this other thread: http://wordpress.org/support/topic/the-events-calendar-messes-with-bbpress?replies=3

    Yeah I mean you could have a valid point – when we tried to replicate this problem where accessing the other custom taxonomy resulted in null results we actually found it worked as expected.

    Right at this time I’m not sure we’ve got a good case to change things, on the basis of our own test, but if you come across any other issues in this vein do let us know and we’ll take another look.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Plugin interfering with custom post type query’ is closed to new replies.