[Josh]

Hey!

Thanks for reaching out!

It’s best to open a new ticket even if the issues are similar. This allows us to ensure we’re able to answer your question as quickly as possible as well as ensure we’re able to answer you fully without having to answer multiple conversations within a single thread.

If you would, can you open a new ticket and include the list of Facebook pages that you’re importing from? Additionally, within that new thread, also add a private reply which has the system information found within the Events Settings -> Help tab of your WordPress dashboard. We’ve been unable to replicate this issue and we’re looking to find a root cause using settings and pages of those experiencing this issue.

Beyond that, the rest of our support that we’re able to give will be very similar to the original response to this thread.

danielp,

It’s been a while since we’ve heard from you. I’ll go ahead and close this ticket for now. If you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey

Thanks for following up!

I definitely understand the annoyance of the gist embedding issue on our forums right now. That should be getting cleared up shortly as we iterate on this new site.

I’m glad you were able to get the issue resolved! For the notifications, can you check to see if the notifications were filtered through your spam folder?

Thanks!

[Josh]

Hey,

Sorry again for the delay.

We went back and reviewed the original snippet to see if there was a clean way to modify it to fit what you’re needing so it’s not a continual attempt to work around the limitations of these other solutions. Here is the modified version (you’ll need to add the appropriate slug and operator for your specific scenario):

add_action( ‘pre_get_posts’, ‘exclude_events_category’ );
function exclude_events_category( $query ) {

if ( $query->query_vars[‘eventDisplay’] == ‘upcoming’ || $query->query_vars[‘eventDisplay’] == ‘past’ || $query->query_vars[‘eventDisplay’] == ‘month’ && $query->query_vars[‘post_type’] == TribeEvents::POSTTYPE && !is_tax(TribeEvents::TAXONOMY) && empty( $query->query_vars[‘suppress_filters’] ) ) {
$query->set( ‘tax_query’, array(
array(
‘taxonomy’ => TribeEvents::TAXONOMY,
‘field’ => ‘slug’,
‘terms’ => array(‘presentations’),
‘operator’ => ‘IN’
)
)
);
}

return $query;

}
We’ve added an additional check to see if we’re on the main query and running if we are. There are some occasional issues with this that we’ve seen in the past where the check has gone outside the scope of the main query. Let me know if this works with your scenario.

Thanks!

• This reply was modified 11 years, 3 months ago by Josh.

[Josh]

Hey,

Sorry for the delay!

You can remove the ticket notification from that email by adding additional line to the previous snippet. The updated snippet would look like:

<pre>add_action( 'init', 'wootickets_stop_sending_email', 99 );
function wootickets_stop_sending_email() {
$woo = TribeWooTickets::get_instance();
remove_filter( 'woocommerce_email_classes', array( $woo, 'add_email_class_to_woocommerce' ) );
remove_action( 'woocommerce_email_after_order_table',  array( $this, 'add_tickets_msg_to_email' ), 10, 2  );
}</pre>

Let me know if this helps.

Thanks!

[Josh]

Hey Ty,

Thanks for following up.

Definitely a very strange issue. Would you mind going the the Event Settings -> Help tab and copying the system information from the bottom of that page and sending it to us as a private message?

Thanks!

[Josh]

Hey!

We’ve reached out to the developers of the Download Manager plugin in attempts to work through the incompatibility. We’re currently waiting on their response and we’ll notify you here when we hear back and get a game plan together to work through this issue.

I’ll go ahead and close this ticket for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Lucas,

Thanks for following up! We’ll notify you within this ticket to the status of the compatibility as we proceed with the next release.

I’ll go ahead and close this ticket for now, if you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey,

Thanks for following up! This definitely sounds like a strange issue. Would you mind sending us login credentials as a private response so we can take a closer look at the issue?

Thanks!

[Josh]

Hey,

Thanks for following up with us!

Traditionally, theme settings are stored in a way that they’ll be kept for that theme even when switching. To be certain though, you can verify with your theme developer to ensure this is the case with your specific theme.

I hope this helps. Let me know if you have any further questions.

Thanks!

[Josh]

Hey,

Awesome! I’m glad we were able to get this cleared up.

I’ll go ahead and close this ticket, if you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Bennie,

I’m sorry for the delayed response. For some reason your post didn’t show up when I originally clicked through to respond to the other posters response.

You should be able to include the snippet just inside the opening “<?php” tag at the top of the file or at the bottom ensuring that you’re not including it within the brackets of an existing function. So you should be able to add it after the last “}” within the code pasted above.

Let me know if this helps.

Thanks!

[Josh]

Hey Larry,

Thanks for reaching out to us!

All of our views are created using PHP however the majority of the content is delivered using ajax. However, this is extensible and can be modified within your theme in the same way that PHP templates can be overwritten and modified.

Let me know if this helps. If you have any further questions when considering our plugin please don’t hesitate to ask.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

It’s possible that the custom meta may be causing a conflict. Do the fields display on the front-end with that code deactivated?

If so, would you mind pasting the code you used to create the meta box via a gist or pastebin here so we can take a quick look at it to see if there is anything that stands out as a potential conflict?

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

I apologize for the inconvenience but unfortunately there are several known issues with the WPML plugin. It is a strong desire of ours to get our plugin compatible with WPML this year. We do have it tentatively set for our next release to allow our developers time to actively dig into the issues and determine what it will take to get the plugins compatible.

So, if everything goes as plan and no delays are encountered in development, we should see compatibility with WPML by the next update to our plugin.

I apologize again for this inconvenience.

Thanks!

[Josh]

Hey Donald,

Thanks for reaching out to us!

You can remove that feature by adding the following snippet to your theme’s stylesheet:

.tribe-mini-calendar-event .list-date {
display:none!important;
}

Let me know if this helps.

Thanks!

[Author]

Posts