[Geoff]

Awesome, I’m glad that helped! Thanks for following up and confirming. 🙂

I’ll go ahead and close this thread, but please feel free to start a new one of anything else comes up and we’d be happy to help.

Cheers!
Geoff

[Geoff]

Hey there, Marcus! I saw that my previous answer was marked as correct, so I’m going to go ahead and close this thread. Please feel free to start a new thread of any other questions pop up and we’d be happy to help. 🙂

Cheers,
Geoff

[Geoff]

Hey there, Anders–nice to see you again!

You’re spot on and there appears to be a z-index conflict.

I was able to remedy it in DevTools with the following CSS:

.genesis-nav-menu .menu-item:hover>.sub-menu {
z-index: 999;
}

Give that a shot and let me know if it helps clean things up. 🙂

Cheers!
Geoff

[Geoff]

Hi Robert, thanks for getting in touch!

Good question. It really depends on the filing status and type of organization. If you go ahead and fill out the application, we’ll review it and hit you back up with a reply whether you qualify.

Does this help answer your question? Please let me know. 🙂

Cheers!
Geoff

[Geoff]

Hi there, James! Thanks for getting in touch and sorry about the issue. I can help you figure out what’s happening here.

By chance, are you using WooTickets 3.9? We released a new version (3.9.1) just yesterday that addresses an issue that sounds very similar to the one you’re describing.

Give the update a try, or let me know if you are already running 3.9.1.

Cheers!
Geoff

[Geoff]

Hi there Rober! Sorry about the issue. I can help you get back on track.

If you were using this snippet to move the location of the ticket form, you can prevent the issue from happening again by wrapping it in the following:

if(class_exists('TribeWooTickets')) {
// rest of the snippet
}

That should clean things up a bit so the error doesn’t happen again. 🙂

Does this help answer your question? Please let me know.

Cheers!
Geoff

[Geoff]

Thanks everyone for following up! Definitely some great discussion in here and I’m glad we all settled in a nice spot.

I’ll go ahead and close this thread for now, but do please feel free to start a new one if any additional questions or issues pop up and we’d definitely be happy to help.

Cheers!
Geoff

[Geoff]

Awesome–nice work and thanks for both following up and sharing the way you went about it. 🙂

Geoff

[Geoff]

Hey Joshua, just checking in to see if there’s been any update or if you have any follow-up questions–please let me know!

Geoff

[Geoff]

Hey there! Thread’s been pretty quiet for a couple of weeks, so I’m going to go ahead and close it. Please start a new thread if you have additional questions and we’d be happy to help you there.

Cheers!
Geoff

[Geoff]

Hey there, Wayne! This thread’s been quiet for a couple of weeks, so I’m going to go ahead and close it. Please start a new thread if you have additional questions and we’d be happy to help you there.

Cheers!
Geoff

[Geoff]

Hey there, Nick! Thread’s been quiet for a couple of weeks, so I’m going to go ahead and close it. Please start a new thread if you have additional questions and we’d be happy to help you there.

Cheers!
Geoff

[Geoff]

Hi Morte, thanks for getting in touch!

Good question–you’re correct: showing ticket amounts on the front end is not currently right out of the box. It’s something we’re definitely looking at, but haven’t added to the roadmap just yet.

In the meantime, you could fetch the number of total tickets available and echo it where needed using the tribe_events_count_available_tickets() function:

<?php echo tribe_events_count_available_tickets() ?>

That will display the number of available tickets for a particular event.

Cheers!
Geoff

[Geoff]

Hello Karen, thanks for getting in touch!

Yeah, we noticed the same thing when we updated to the latest version of WooCommerce ourselves.

Our WooTickets plugin inherits the styling used by WooCommerce. In other words, we don’t force any specific style but rather inherit the styles implemented by WooCommerce. We tested this on other non-ticket products and the issue applies there as well. That means it’s something that is universally affected by WooCommerce rather than the WooTickets plugin.

You can try to style the controls using custom CSS, but your best bet is to let the WooCommerce team know about the change and request that the styling be added back in.

As an alternative, you could revert to the previous version of WooCommerce you were using and the styles should reappear.

Sorry I don’t have a concrete solution for you here, but I hope this helps shed light on the issue.

Cheers!
Geoff

[Geoff]

Hi there, Sandra! Thanks for getting in touch and for checking out The Events Calendar and the PRO. 🙂

I do want to note that we typically reserve the Pre-Sales forum for questions about The Events Calendar PRO and plugin features and other questions about our premium plugins rather than troubleshooting issues.

That said, I’m happy to provide you some resources to help troubleshoot your issue:

• New User Primer – This gives an excellent overview of how to install and configure The Events Calendar, including links to additional tutorials that provide deeper details. It’s an excellent place to get started if you’re new to the plugin.
• Testing for Conflicts Guide – Many issues can be identified and resolved simply by following the steps outlined in this guide. Often, issues are related to conflicts with themes or other installed plugins and this guide provides the steps to identify them.
• Support Forum – This is the support forum for the free plugin. It’s an extremely active community and members from our team check it each Wednesday to contribute answers as well.

I hope this helps! Let me know if you have any additional questions about the plugin features and I’d be happy to help. 🙂

Cheers!
Geoff

[Author]

Posts