[Barry]

When you refer to reverting admin.css, do you mean a file from WooCommerce or from The Events Calendar or something else, such as from the WooTickets plugin directory?

[Barry]

Hi Mickey,

This is a facet of the manual ordering process in WooCommerce – it’s apparently a design feature and isn’t I’m afraid something that is in our realm of influence, as it were.

You could definitely approach the WooThemes support crew (since WooCommerce itself is their product rather than ours) and they might be able to fix you up with a workaround of some kind?

[Barry]

Hi burnhamrichards,

Just for future reference you’re more than welcome to post questions like this across in the Events Calendar PRO forum (even if you’ve only purchased WooCommerce tickets) and that’s probably a better home for this since it doesn’t sound like it’s too specific to WooCommerce Tickets itself.

Have you checked out our docs? We’ve got a list of functions – many of which could be helpful here, such as tribe_is_day() and tribe_is_month(), etc:

http://docs.tri.be/Events-Calendar/

Does that help any here?

[Barry]

OK, well in that case I will go ahead and close this thread – if you need any help in the future though definitely feel free to go ahead and create a new thread 🙂

[Barry]

Hi platinumblondes: can you confirm how you placed the test order?

If you did it through the WooCommerce orders screen (ie, in the admin environment) then this would be expected behaviour and nothing to worry about, at least not on a technical level: obviously however you might need to work around it somehow if it’s problematic for you.

If you placed the order as an ordinary customer would, be placing it in the cart and proceeding through checkout however, then that definitely wouldn’t be desirable. If that’s the case, can you confirm if this also affects ordinary WooCommerce products (if so, are you using any add-ons such as additional payment gateways – and are they impacting)?

[Barry]

Yes, it would relate to/affect all event-related custom post types. Glad it helped!

[Barry]

Hi minemindmedia, what versions of our plugins are you using here?

[Barry]

Hi granatdesign, would a snippet like this one help here? You could drop it into your theme’s functions.php or some other suitable place and modify it to suit, so that singular event posts are served by one template and all others by a different one.

[Barry]

Hi Kevin, I see no reason why you couldn’t. Something like this ought to swing it:

add_filter('tribe_events_register_event_type_args', 'change_event_type_args');

function change_event_type_args(array $args) {
$args['property'] = 'custom value';
return $args;
}

[Barry]

Hi everyone!

What I’d like to suggest is that we concentrate on mavellino18’s issue in this thread. Of course everyone’s welcome to monitor progress but if it turns out that there are multiple different causes of this then it could become very confusing indeed if we have to manage different troubleshooting processes all at different stages 🙂

Naturally, you are welcome to create your own thread and receive one-on-one help with this from a team member specific to your own installation and situation.

@marvellino18: I definitely appreciate you carrying out some troubleshooting already. What I’m not clear on and want to make sure wasn’t missed in the process was that, at the same time as switching to a default and unmodified theme such as Twenty Eleven, you also deactivated all other non-Modern Tribe plugins.

Can you confirm that you have tried that and what the outcome was / if it enabled you to zero in on any other plugins that were causing problems here?

[Barry]

Hi everyone, thanks for your patience so far. I just wanted to update you all and let you know this is still in progress and, realistically, the fix will probably arrive in the next, next release.

I can’t actually replicate this with my current setup, but I wanted to float the following idea as a possible interim workaround.

First, set up an override for tribe-events/single-event.php (if you are unsure how please see our Themer’s Guide for the lowdown on this). Then, locate the following lines of code:

<!– Notices –>
<?php tribe_events_the_notices() ?>

Try changing it to the following:

<!– Notices –>
<?php if (date(‘Y-m-d’) > tribe_get_start_date(get_the_ID(), false, ‘Y-m-d’)) tribe_events_the_notices() ?>

I can’t be certain it will help (since I’m not currently able to replicate) but it’s possible it may at the very least be a starting point for a solution. Nor is it perfect as it doesn’t test to see what notices it might be hiding, but again it could be embellished to cover various more complicated scenarios.

[Barry]

OK, so take a look at functions/custom.php around lines 58-60: you should see this code which seems to be causing the problem. Also, as you can see from the author’s comments, you should be able to modify that and add exceptions for custom post types such as events.

I can’t actually make that work the way the author seems to have intended – the problem is that it seems to be assuming only one query will be used to build up the page (which would be quite unusual) and only the first query is tested to see which post type it relates to – whereas actually many queries will run and this affects all of them. Hopefully that makes some kind of sense 😉

What you could try though is finding this line from the same file:

function query_post_type($query) {

Just after it, insert this line:

if (isset($query->tribe_is_event_query) && $query->tribe_is_event_query) return $query;

That should hopefully fix this 🙂

[Barry]

No problem, glad that’s working for you – and of course it should hopefully be fixed anyway as soon as the next maintenance release arrives 🙂

For the time being since I think we’re all happy here I will close this thread.

[Barry]

Hi mindfeck – the upcoming events widget does seem to work in some places and not others. For instance, if I am using the default page template (from Events > Settings > Display) and add the Event List widget to the default sidebar it is correctly populated when I view the main calendar page or indeed any other regular page.

For some reason though it doesn’t work on the front page. At this stage can I check if that is consistent with your experience and if you have noticed any other similar patterns you think I need to be aware of?

[Barry]

OK – good to hear – but if the problem does come back and cause new problems please don’t hesitate to open a new thread and reference this one.

Thanks!

[Author]

Posts