[George]

Hey @Karly!

The related posts are retrieved using a very simple set of parameters: tags and Event Categories.

You can explore the complete set of code by heading to this file in Events Calendar Pro:

/events-calendar-pro/src/functions/template-tags/general.php

In there you’ll find the tribe_get_related_posts() function, which is as follows:


function tribe_get_related_posts( $count = 3, $post = false ) {
$post_id = Tribe__Events__Main::postIdHelper( $post );
$tags = wp_get_post_tags( $post_id, array( 'fields' => 'ids' ) );
$categories = wp_get_object_terms( $post_id, Tribe__Events__Main::TAXONOMY, array( 'fields' => 'ids' ) );
if ( ! $tags && ! $categories ) {
return;
}
$args = array(
'posts_per_page' => $count,
'post__not_in' => array( $post_id ),
'eventDisplay' => 'list',
'tax_query' => array( 'relation' => 'OR' ),
'orderby' => 'rand',
);
if ( $tags ) {
$args['tax_query'][] = array( 'taxonomy' => 'post_tag', 'field' => 'id', 'terms' => $tags );
}
if ( $categories ) {
$args['tax_query'][] = array(
'taxonomy' => Tribe__Events__Main::TAXONOMY,
'field' => 'id',
'terms' => $categories,
);
}

$args = apply_filters( 'tribe_related_posts_args', $args );

if ( $args ) {
$posts = Tribe__Events__Query::getEvents( $args );
} else {
$posts = array();
}

return apply_filters( 'tribe_get_related_posts', $posts );
}


When it comes to changing the parameters used for finding “related” events, you can use the tribe_related_posts_args filter seen in the code above. This filter lets you filter the query arguments used in that eventual Tribe__Events__Query::getEvents( $args ) call in the function above.

☝️ I hope this information helps!

Sincerely,
George

[George]

Hey Lee,

Sorry for the delayed response here!

This is not something “stupid” on your end!

In fact, it looks like a JavaScript conflict emerging from either your theme or another plugin on your site.

I would recommend doing each of the steps recommended in this article → https://theeventscalendar.com/knowledgebase/testing-for-conflicts/

After EACH STEP in that process, take another look at what happens when you hover over those events…do the tooltips show correctly, or continue to be broken?

Let us know what you find!

Thank you,
George

[George]

Hey Sean,

Sorry for the delayed response here! It is unfortunately not possible to add timezones there. 🙁

Well, it is technically possible, but would take a large amount of custom coding and delicate implementation of custom timezones.

Our plugins use the timezones provided by PHP and WordPress itself. If you head to Settings → General in your wp-admin, you’ll notice that the timezone options there are the same ones that end up in the various timezone pickers in our plugins. The “colloquial” / common named timeones like “EST”, “Central”, “Mountain” etc. are unfortunately not available at this time.

I hate to bear that news! Please let me know if there’s anything else I can try to help with.

Sincerely,
George

[George]

Hey Shaun,

Thanks for reaching out.

The situation you describe is by design:

seems like the only way to have a username and password is to be the person that actually paid for the plugin.

The only way for you to post here would be for the client to share their login credentials with you, and for you to then log in and post from that account.

We do not store any payment information, like credit cards or anything, so if you gain access to the account you will not see any payment credentials like card numbers, etc…just wanted to mention this as it’s the main thing folks are often concerned about when it comes to sharing their login credentials.

If this is not a sufficient solution, then please contact us over email with a link back to this thread for context.

The email address is support at theeventscalendar.com

I will close this thread to facilitate emailing us if need be; over email we can discuss things like account credentials and access in privacy.

Please follow up over email only on this topic if need be—or, if you don’t need to follow-up, login with your client’s credentials and post away in the premium forums! 😀

Cheers,
George

[George]

Hey Michael,

Apologies for the delayed response. Doing this is only possible with custom coding. We do not technically offer support for custom coding, but I was writing up a code snippet for you and did not reply to let you know.

Sorry for dropping the ball there! However, I have put together a code snippet for you that should work well in regards to keeping the RSVP form open by default. Try adding the following code to your theme’s functions.php file:


add_action( 'wp_footer', 'tribe_force_rsvp_form_to_be_open' );

function tribe_force_rsvp_form_to_be_open() {
wp_enqueue_script( 'jquery' );

?>
<script>
jQuery(document).ready( function() {
if ( 0 < jQuery( '.tribe-events-tickets' ).length ) {
jQuery( '.tribe-events-tickets' ).addClass( 'tribe-events-tickets-has-rsvp' ).addClass( 'tribe-tickets-has-rsvp' );
}
});
</script>
<?php
}


I hope this helps! 😀

— George

[George]

This reply is private.

[George]

Thanks for the followup! There is nothing out of line in that system information, which is good—version numbers are all recent, etc.

How are things with these issues, then? What issues persist?

[George]

This reply is private.

[George]

Thanks for chiming in, Chris!

Greg, it is definitely worth finding out if the Preview button is being used by the folks administering your site.

1. Let us know if you find anything that confirms that many people are using the Preview Button.

2. Let us know if when you yourself use the preview button in the process of creating new events with new venues if that seems to lead to some duplication like you originally reported.

Cheers!
George

[George]

No problem Sébastien! Glad to hear you found the problem.

Definitely report this conflict to the UberMenu folks—their plugin should not be breaking other JavaScript from other plugins….

Best of luck with your site! Open a new thread any time if other questions or issues arise.

Sincerely,
George

[George]

No worries! 😀

Open a new thread any time if other issues or questions arise.

Cheers,
George

[George]

Glad to hear it, Alexander!

As for how the tags got there in the first place, I admit that I am not quite sure. This is often a problem if you copy-and-paste the shortcodes from a location, so that might be relevant to your issues.

In any case, I hope this tips helps with shortcodes going forward, and I wish you the best of luck with your project!

Open a new thread any time if other issues or questions arise.

Sincerely,
George

[George]

Hey Rob,

Thanks for clarifying this a bit.

It is tricky to target just events, especially a subset of events. However, you do have a few options here.

You can use robots.txt as you suggest; learn more about using that here → http://www.robotstxt.org

Another option is to add robots meta tags to the HTML head of any events document…the main /events/ page, single events, etc.

I wrote up a snippet for you that should do just that:


if ( class_exists( 'Tribe__Events__Main' ) ) {

function tribe_limit_search_indexing_of_events() {
if ( tribe_is_event() ) {
echo '<meta name="robots" content="noindex, nofollow">';
}
}

add_action( 'wp_head', 'tribe_limit_search_indexing_of_events' );
}


☝️ I tested this and it worked well for me on my local site—in terms of adding the proper meta tags, anyways.

Like with any limitation imposed on indexing—whether by robots.txt, or .htaccess, or meta tags, etc.—these limitations are requests. It is fundamentally up to the search engines to honor that request.

So, regardless of what method you choose it may take some time before you notice changes in effect.

Let me know if this information helps, and if there are any further questions I can try to help with!

Sincerely,
George

[George]

Hey Sebastien,

Thanks for your followup here.

I am sorry to hear that issues persist.

I cannot recreate the problems on my own site.

So to help find out what the problems are, I would recommend that you do the steps this article tells you to do: https://theeventscalendar.com/knowledgebase/testing-for-conflicts/

☝️ What do you find after doing these steps?

Thanks!
George

[George]

Hey Robert,

Thanks for your follow-up. There is unfortunately no date range feature in the works other than what you already find, for example, on the demo site. 🙁

Next, to ask:

And just to confirm, I can’t restrict access even at the one-to-one level (a user restricted to adding only their band)?

☝️ This is indeed not possible with our plugins out of the box. You could write extensive custom code to enable such limitations (or hire someone to write such code for you), but our plugins do not do this out of the box.

Sorry to disappoint here!

Please let me know what you think and if there are any other questions I can try to help with.

Sincerely,
George

[Author]

Posts