[Barry]

I’d probably start by looking at what happens without your heavily-edited version of the theme – does it work then? If so, start reintroducing your edits and see if you can pinpoint things that way.

I’m afraid there may not be too much we can offer up here since it relates to some fairly bespoke custom theme work (by the sounds of it).

[Barry]

Sorry for the delay Ben, I’m afraid we can’t commit to a timeline on this one – at least not in the immediate future.

Would it be possible for you to simply press ahead by using 2 queries, one for non-tribe events, one for tribe events, and then merge the results, sorting them however you need to meet your requirements here?

[Barry]

Hi Seth,

It looks like you are using a minifier which has also concatenated all of the scripts into a single file – can you try turning this off to see if the override then works successfully?

It’s possible the override is being included (by your minifier) before the main event stylesheets and then is overridden in turn – it’s also hard to pinpoint which rules you added (if you could summarize the CSS rules you added, perhaps by sharing the original code as a Pastebin or Gist snippet, that would be great).

It would also be preferred if you could create a new thread for your own question – if Debbie or Chris return to the conversation with further questions about their own specific problems for instance this could become very confusing indeed 🙂

Thanks!

[Barry]

Hi Cynthia – I visited http://events.stcwdc.org/event/gamification-and-the-new-rules-for-user-assistance-recorded-webinar/ and was able to progress to Google Calendar without any problems.

I’m not sure why this is sporadic in nature – but I can’t find a way to replicate this at all using a stock installation of WordPress/our plugins even with very long titles and descriptions. Did you find a solution in the interim/have you been able to isolate anything behind this?

Definitely a strange problem (and not in any way to diminish this, but not one we’ve seen widely reported with the current release).

[Barry]

This should now be resolved as of the latest release. “Unstickying” and closing since we should be good here. Thanks everyone for your patience and support while we worked through this one.

[Barry]

We’re definitely taking note of the interest – please don’t think otherwise – but it isn’t necessarily something that’s easy to implement in a way that will work well across the board for all of our customers.

Right now a decision still has to be reached on whether a future release will include this or how exactly it will function: WooCommerce Tickets in its current form is – and we’ve always tried to emphasize and be open about this – a simple ticketing solution rather than a full featured event management tool per se.

Again, just to emphasize, it is something that’s under consideration and we’ll do our best to inform you as things progress 🙂

[Barry]

Try replacing it with:

echo tribe_get_unslashed_event_link()

I don’t think you should need to pass in the $post variable in these circumstances, but let me know if that doesn’t work for you.

[Barry]

So it looks like this may unfortunately have been overlooked – but we’ve logged it afresh and will start progressing it. Potentially this will make the next maintenance release or the subsequent one – thanks for your patience and support as always 🙂

[Barry]

Sure, I can understand that. Let me check in with the team – the first piece of work (preventing empty month views from returning a 404 status) has already been completed but I’ll need to see what’s planned/scheduled for empty day views.

[Barry]

It would be very much preferred if you could 🙂

It makes it easier for us on a few levels and allows us to reply more quickly – and please don’t hesitate even to add multiple new threads if needed (for instance if in future you have a range of distinct problems that you need help on) – as multiple team members can help simultaneously.

(I’ll close this one in anticipation of a new thread.)

[Barry]

Hi Noel,

The process is going to be different with different themes, but let’s look at an example using the default Twenty Twelve theme and let’s assume we are using the Default Page Template for events.

We could then edit/override the theme’s page.php template and change:

<?php get_sidebar(); ?>

To:

<?php if ( ! tribe_is_event_query() || ( tribe_is_event_query() && is_singular() ) ) get_sidebar(); ?>

Which is basically telling WordPress to show the sidebar:

* If the page/request is nothing to do with events
* Or show it if it is for events but just a single item, such an individual event or venue

The only problem then is that when you view month view, for instance, the sidebar has gone but the calendar will not occupy the full space. You could counter this by adding a snippet like this one to your theme’s functions.php file.

So that should give an overview of how you might get around this. Again, each theme is different and this may not apply exactly as described to other themes (very likely it will not) but it hopefully it gives you some ideas. Also note that you may prefer to place your customizations in a child theme, again I’ll leave it to you to dig into that 🙂

[Barry]

Apologies for the delay – the team’s been overwhelmed with support requests over the last couple of weeks, but we will get there and creating a new thread as you have done is the right way to go 🙂

[Barry]

Yeah there’s definitely a problem and it seems to boil down to their code changing one of the queries issues by WooCommerce Tickets.

Our dev team is looking into it and if it’s something we can/should solve within our code we’ll certainly do so – and I’ll dfefinitely update this thread to let you know the outcome.

[Barry]

Great tip, thanks mindfeck 🙂

[Barry]

Great, thanks for the feedback all – since it’s looking like we’re all sorted here I’ll close this thread. Of course if you continue to experience problems (or hit any other obstacles) please don’t hesitate to create new threads as needed.

[Author]

Posts