[Barry]

Please note this thread will no longer be monitored – if we can help with anything else, please do create new threads as needed 🙂

[Barry]

Please note this thread will no lnoger be monitored. If we can help with anything else, feel free to open new threads as needed – thanks!

[Barry]

How many do you have to update? Would it be viable to update each of them, or are there too many for that to be practical?

[Barry]

Awesome, thanks for bearing with us 🙂

[Barry]

WordPress has a post_class filter you can leverage for this sort of purpose:

http://codex.wordpress.org/Function_Reference/post_class

So that’s one avenue, or you could modify the relevant template and code it in there.

I hope that helps 🙂

[Barry]

Hi Mike,

While typically we don’t take on tasks like that we’re certainly happy to point folks in the right direction wherever we can if we see requests for help on our forums and, for things like this, could certainly furnish you wish a list of folks – independent devs and freelancers – who may be able to assist further (as it is admittedly sounding a tad outside the scope of regular support).

So, if you go ahead and make the purchase, we’d be delighted to do what we can 🙂

[Barry]

Hi!

I do see what you are trying to do and it’s definitely possible but, I’m afraid, it is just a bit beyond what we can help you with here on this forum.

It sounds like you don’t want to show any recurring events in list view. That being the case, you may wish to investigate using WP_Query and hooks like parse_query (which relate to WordPress itself rather than our plugin specifically) in order to do this cleanly and still have functional pagination on list view.

Showcasing recurring events separately would mean potentially also be possible, either with WP_Query or tribe_get_events() – which is effectively a convenient wrapper function around WP_Query – but again we’d really need to leave you to dive into this sort of customization.

Thanks!

[Barry]

Sure – try something like:

.single-tribe_events #tribe-events-content form.cart { background: transparent }

I hope that helps!

[Barry]

Awesome – glad it helped 🙂

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

[Barry]

Awesome 🙂

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

[Barry]

Hi!

I was asking about uninstalling/re-installing, not deactivating, and reactivating. I imagine that changes things?

No, not really – right now though we do have a few deactivation hooks none exist to remove data (and WordPress will not automatically purge things either).

Thanks also for confirming the problem – I can see that now, though I’m afraid it’s not something I can replicate locally:

I’m hesitant to de-activate the theme to activate another one because I don’t want to lose any of the customizations set up so far.

I completely understand, but perhaps you could use a testing environment (this could be as simple as installing a fresh copy of WordPress in a subdirectory) in order to run through our standard troubleshooting steps?

If you did this, you could effectively troubleshoot backwards – start with nothing but our plugins and a default theme, then start building up until you have an approximation of your live site – and try to detect if one of the other plugins/your theme is triggering this.

Let me know how you get on 🙂

[Barry]

I’ll go ahead and close this thread – if we can help with anything else please do create a new thread. Thanks!

[Barry]

Please note this thread will no longer be monitored – if you have any further questions please feel free to create new threads as needed. Thanks!

[Barry]

Apologies for not seeing your last post, justeverything – however as before it is often best to create new threads of your own: if someone other than the original poster replies it isn’t always flagged up as in need of further attention by staff.

We are definitely going to look into this further following our own testing with a WP Engine account (which led to us identifying a number of possible problems).

Please note this work may span more than one release cycle – but as querying is of course crucial to the plugin’s operation it is not something we wish to rush.

Thanks for your patience in the meantime – I’ll go ahead and close this thread as there isn’t too much more we can do in the short term, but if anyone does have further questions certainly feel free to post them in new threads.

Thanks again.

[Barry]

Thanks for your patience here 🙂

We were able to run some tests within a WP Engine hosting account and could certainly see some warnings – long query warnings in particular – being generated. Though performance was snappy this was admittedly not on a live site, under load from real traffic.

As a number of you seem to be hitting very real problems here we are of course going to do what we can to try and make some improvements with regards to query performance and will quite likely start with an attempt at minimizing the number of long queries that take place.

Realistically this work may span more than one release cycle: querying is central to the plugin and we need to take the time to get it right – but do bear with us and we’ll do what we can here 🙂

Thanks!

[Author]

Posts