[Barry]

Hi – sorry to hear you are hitting difficulties.

That’s certainly something that’s cropped up occasionally due to conflicts with other plugins. I see you tried some of our troubleshooting steps already, which is fantastic, but can I ask you to try (or confirm you have already tried) the following steps in full?

• Please deactivate all other plugins
• Switch to a default, unmodified theme such as Twenty Twelve
• Now test to see if you can update recurring events
• If you can, begin reactivating everything
• Test at each stage to see if the problem has returned

Let us know how you get on – thanks!

[Barry]

Hi!

Currently there is no such feature – but you could certainly export/email yourself the attendee list and then extract the email addresses that way. Would that be workable?

If not, we’d certainly be open to any feature requests you might post along these lines – but I tend to think this might be the domain of an extension/add-on or customization rather than something we’d build in to the ticketing plugin itself (though if there was sufficient demand it would certainly be given serious consideration).

Thanks!

[Barry]

Hi!

Can you clarify your question a little – do you mean that you wish to add this information within a regular WooCommerce storefront view for a given category? Or are you wanting to add this information to the upcoming events list, or something like that?

Thanks!

[Barry]

Hi – great questions!

Just as with WordPress, some template tags do indeed assume they will be used in relation to the global $wp_query object – and that is the case here.

So, in a situation like this one, you would either need to devise a workaround with regards to the $wp_query global (proceed with caution if so!) or else build an alternative template tag that functions in the circumstances you are trying to use it.

I hope that helps 🙂

[Barry]

Hi Bob,

It certainly looks like something is going wrong there. Rather than being an issue with stylesheets I think the image being pulled in from Facebook is simply of rather strange dimensions. Do you find this only happens with the theme you mentioned (ie are images imported as expected when you use a different theme)?

If you haven’t tried that out already could I ask that you do so (and, ideally, also deactivate all other plugins except for those by Modern Tribe) and check if Facebook event images import in the expected dimensions?

A workaround until our next release – which should be available soon and includes reworked code for pulling in images from Facebook – would be to manually remove or replace the featured images. I do realize that’s not ideal if you have lots of imported events to deal with, but it could tide you over until the next release arrives.

Let us know!

[Barry]

Hi Kristin – great questions!

For your first question, that’s fundamentally more a matter of customizing WooCommerce than it is WooCommerce Tickets, though there’s definitely some crossover between the two. I’d recommend investigating adding custom checkout fields as a pure WooCommerce customization in the first instance – and then looking at how you might further integrate this with WooCommerce Tickets (if that’s even necessary) as a further enhancement. After all, a ticket is, essentially, just a product like any other.

Similarly, your second question really is one that relates to WooCommerce itself. Our plugin has no bearing or influence over the checkout process – so taking these questions across to the team at Woo if you need further insight is probably a good way to proceed.

Hope that helps 🙂

[Barry]

Hi – great question!

It’s not something that is directly supported by the plugin at this time. We’d certainly be open to considering any feature requests you might post along these lines, but right at this time you’d either need to leverage another suitable plugin (there might be some likely contenders that exist as general purpose WooCommerce extensions) and/or do some customization work to make this happen.

Does that help/clarify things?

[Barry]

Hi!

Sorry to hear you’ve hit difficulties.

The TribeWooTickets class is still a part of the WooCommerce Tickets plugin – so long as it is indeed active you shouldn’t have any problems. However, if for any reason the custom code in your template runs and WooCommerce Tickets is not active, then you could indeed see this sort of problem.

One workaround is to test for the presence of the TribeWooTickets class before running those pieces of code, something like this:

if ( class_exists( 'TribeWooTickets' ) ) {
    /* Add your remove/add action calls in here */
}

That should effectively insulate them from changes in the outside environment (such as WooCommerce Tickets being deactivated).

Does that help at all?

[Barry]

Yes, exactly so.

[Barry]

Thanks for sharing that information.

329 [/nas/wp/www/cluster-2051/baynature2/wp-content/themes/bay-nature/options/theme-widgets.php:481]
44 [/nas/wp/www/cluster-2051/baynature2/wp-content/plugins/events-calendar-pro/lib/tribe-geoloc.class.php:754]
13 [/nas/wp/www/cluster-2051/baynature2/wp-content/plugins/baynature/lib/post-count-correction.php:31]
7 [/nas/wp/www/cluster-2051/sffilmschool/wp-content/plugins/404-redirected/includes/functions.php:444]
1 [/nas/wp/www/cluster-2051/baynature2/wp-content/plugins/the-events-calendar/lib/tribe-event-query.class.php:856]

So not all of those relate to our plugin, but we are certainly aware for instance that the geolocation query (the second item on that list) needs some attention and that we could improve things overall. I’m afraid there’s no short term solution we can provide there – besides suggesting you work with your host to enable query caching if that’s not already in place – but I’d like to think you will see things improve in this regard over time as we turn out future releases.

PHP Fatal error: Call to undefined function tribe_is_community_my_events_page() in /nas/wp/www/cluster-2051/baynature2/wp-content/themes/bay-nature/page.php

I think this is really a separate issue and I’d recommend creating a new thread for it. If you hvae customized your theme’s page.php template at all please do provide details in the new thread.

Thanks!

[Barry]

So what you’d need to do – if you were hiding them via CSS is customize the relevant views and add those classes to the elements, then setup your own CSS rules to accommodate this.

Our Themer’s Guide (link over on the right) is a great starting point for this kind of work 🙂

[Barry]

Sounds like you’re making progress 🙂

You could use the tribe_get_venue() function to just retrieve the venue name (rather than a fully formed link) and/or wrap that within the same link as the event title.

Hope that helps – and I’ll go ahead and close this thread (feel free to open new ones as required for assistance with other issues).

[Barry]

Thanks – that’s the correct course of action and we’ll certainly consider it for a future release.

I’ll go ahead and close this thread, but of course if we can help with anything else please don’t hesitate to create new threads as needed. Thanks again!

[Barry]

OK: I’m afraid that, right now, there’s not much else we can do here in the short term.

It’s a shame you can’t set up caching for the generated HTML output, but certainly if it was causing problems I can imagine it would be preferable to live without it. We are continually changing and improving the codebase so I’d like to think you will see things improve as new versions arrive – but speeding things up further at this moment in time is something you’re realistically going to have to drive forward yourself with regards to your own site.

Sorry we can’t offer more on this occasion.

[Barry]

This definitely looks like a bug – we’ll fix it as quickly as we can. Apologies for any inconvenience in the meantime.

[Author]

Posts