[Michael]

I’d love to update to 3.3, but

1. my events listings in the backend straight up disappeared.

2. the appeal of an events plugin that uses wordpress’ custom post types were that you could query them like any other post type. However this simple and completely valid query now fails:

$the_query = new WP_Query(
array(
‘post_type’ => array(
‘post’,
‘page’,
‘tribe_events’
),
‘meta_query’ => array(
array(
‘key’ => ‘_feature’,
‘value’ => ‘on’
)
),
)
);

I’ve seen this type of thing being reported elsewhere and in every scenario the ticket is shrugged off as being an issue with the customers code.

For the interest of this plugins future, I highly recommend this bug be identified and patched.

Until that time, I simply must urge my client to stick with the old versions.

-M

[Michael]

Nevermind, I’ve rolled back the plugin to v3.0.3 and it’s working perfectly now.

[Michael]

Can you point me to the file that alters the WP_Query call? Or where it is that the plugin modifies the resulting SQL query?

[Michael]

@Marty: Brilliant, thank you!

[Michael]

Hey Paul,

Confirming that its the latter case: “the problem that it is showing every instance of recurring events, when you want it only to show one instance”.

[Michael]

Thanks Joey, That does help.

You guys have an awesome product. Looking forward to seeing it grow as wordpress matures as a cms.

[Michael]

Okay. I’ve completely botched this – Is there a way I can share a line of PHP code on the forum?

Also, anyway to delete my own botched comments :\

[Michael]

All my < ? php lines were stripped from the comment above. Should read:

I get the /1970-01-01 suffix when calling

Right now my hack is

[Michael]

I am currently using 2.0.4 and I get the /1970-01-01 suffix when calling

Right now my hack is

Any word on why this is occuring/when it will be fixed?

Thanks for the hard work!

[Author]

Posts