Include events in main blog loop : Confusing, Almost unusable…

[Chris]

When I tick “Include events in main blog loop” (aka “Show events with the site’s other posts. When this box is checked, events will also continue to appear on the default events page.” )

If I want to use normal blog posts and events, this feature is broken. It assumes (like the woocommerce integration) that you’re only using this wordpress install for one purpose: events. Not many people are going to do that from what I can see.

I naturally assumed that would drop the start date into the ‘publish date’ field so that without modification of other themes and plugins it should ‘just work’. This would add MASSIVE value to your plugins for the lay person, and people like myself who spent hours plowing through debug variables and code to work out how to do this without modifying the plugins (which is what I’ve had to do)

You need a developer to seriously use this set of plugins for a professional site. You CANT do it any other way. There’s too many gaping holes. – like free events having to be RSVP otherwise ticket fees are charged. What if I just want FREE with a cart checkout! (I know another plugin)… I’d fill your user voice with 50 requests if I wrote them, but even that doesn’t guarantee you’ll fix anything. (like putting the event name and ticket name on the woocommerce description – a natural default for any cart)… so many unconventional defaults… so frustrating. I want to shake somebody in your office!! To be honest, I’m debating writing my own plugins for your base events plugins… I’d make tonnes of money just implementing your user voice requests and forum requests (many of which never make it to user voice – why doesn’t your head of support put common issues from here on there, then remove ones that are done!! come on… you’re sooooo close to being a ‘great’ ticketing solution… and don’t start me on mobile apps and your implementation… #ohboy #dealbreaker for many… had to write our own!).

This seems to be repetitively asked for in this forum (and ignored consistently) and is a GAPING hole in this check boxes feature, in fact it’s a BUG, a massive bug.

Can you add secondary options to choose the behaviour of this setting:

1. choice of either start date or publish date

if publish date is selected, choice to append start date and end date to posts query

I’m not going to add this to the user voice page, as that list is badly maintained and a waste of time. There are many items there that are complete and not marked, and features asked for that are badly needed and ignored on your ER/Bug list.

[Chris]

sorry, was a bit tired and grumpy when I wrote that…

Here’s a grain of salt …

[Hunter]

Hey Chris,

Thank you for taking the time to post your thoughts. Even if it’s not all rosy and cheerful, it is still valuable feedback which we cherish dearly. Rest assured, we have a lot of hard working members on our team with the sole purpose of putting out the best plugins and support possible.

With that said, try the following snippet. I believe it should work for what you’re hoping to achieve. Let me know how it goes and we’ll go from there. I’ve also brought this thread to the attention of other support team members so we can further discuss your feedback.

add_action( 'pre_get_posts', 'tribe_post_date_ordering', 51 );
function tribe_post_date_ordering( $query ) {
if ( $query->tribe_is_multi_posttype) {
remove_filter( 'posts_fields', array( 'TribeEventsQuery', 'multi_type_posts_fields' ) );
$query->set( 'order', 'DESC' );
}
}

As tedious and useless as our UserVoice Feature Ideas might look and feel, we are doing everything in our power to improve how we listen to our users, and more importantly, how to incorporate that feedback into upcoming releases.

Thanks again and please keep me updated. Have a great Monday and take care.

[Chris]

add_action( 'pre_get_posts', 'tribe_post_date_ordering', 51 );
function tribe_post_date_ordering( $query ) {
    if ( $query->tribe_is_multi_posttype) {
        remove_filter( 'posts_fields', array( 'TribeEventsQuery', 'multi_type_posts_fields' ) );
        $query->set( 'order', 'ASC' );
    }
}

Needed “ASC” otherwise events way in the last list first. I need the next event to list first, so just reversed the order.

Used this, but also need to make sure events disappear when their ‘end-date’ has been reached… the query needs the ‘end-date’ column added to the query to do this, or a subquery condition… where is the best hook to do that?

• This reply was modified 9 years, 5 months ago by Chris.

[Hunter]

Chris,

Try adding the following line beneath the line containing ‘ASC’ and it should hide events from the main blog loop after their end date has been reached.

$query->set( 'start_date', date( 'Y-m-d H:i:s' ) );

I also recommend changing:

remove_filter( 'posts_fields', array( 'TribeEventsQuery', 'multi_type_posts_fields' ) );

to:

remove_filter( 'posts_fields', array( 'Tribe__Events__Query', 'multi_type_posts_fields' ) );

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts