[Barry]

Thanks Ken!

[Barry]

Not at all, thanks for posting back with the solution – it’s often really helpful for others.

[Barry]

Great, yep that should do the trick, I don’t see anything wrong with that at all. If you wanted it to take up a little less space, just to make it easier when you next open up and work with that file, you might change it to:

<div id="<?php echo tribe_is_month() ? 'content-full' : 'content' ?>">

But that’s essentially the same thing, just “re-worded” – functionally they should be identical.

[Barry]

I’m sorry Ken, you’re absolutely right and I misread your initial post. Additional fields will not work with venues. It would however make a great feature request (someone may even already have suggested it).

I suspect it would also be possible to activate WordPress’s native custom fields in respect of venues, which could be a different avenue worth exploring.

[Barry]

OK, so every theme is different but if you’re comfortable editing its templates (follow your theme vendor’s advice here, such as doing this from within a child theme or whatever approach will make the changes “update resistant”) and you can locate a piece of code like this in the page.php template:

get_sidebar();

We should be able to do something like this to hide it:

if (!tribe_is_month()) get_sidebar();

Which will stop it from displaying on the month/grid view.

[Barry]

Also – if that seems like a working solution, please check out Rob’s post in this thread which demonstrates how you can make it an actual hyperlink.

There is another thread somewhere where I showed a means of converting them to hyperlinks automatically, without wrapping them in HTML, but unfortunately I can’t locate it right now – however that is also definitely possible.

[Barry]

Would Additional Fields help here? You can basically create as many custom fields as you’d like.

[Barry]

No problem at all – just to highlight we don’t typically work on weekends (unless you get lucky!) so it might be Monday before we get back to you, assuming you post for more help today.

Either way, hopefully it all works out 🙂

[Barry]

This reply is private.

[Barry]

Hi David – thanks for the feedback. I’ll relay this to Rob, in future though could I ask you to report any issues with the 3.0 beta directly to him by email?

Thanks!

[Barry]

There are various ways you can go about this.

For instance, to have the ticket price (or range of prices) display for each relevant entry on the upcoming events list you might customize both your list.php template and also your tickets.php template.

You could adapt this approach to show different information on other templates, too, or if you’re feeling adventurous you could create some custom functions to query if an event contains tickets and obtain/generate pricing data or the add to cart button that way.

There are many ways to skin a cat 🙂

[Barry]

This reply is private.

[Barry]

Sure go ahead. Details below.

[Barry]

Hi Mike,

Thanks for reporting that: a fairly straightforward solution is to find the code at the start of the tickets.php template:

<?php global $woocommerce; ?>

And change it to:

<?php
global $woocommerce;
if (post_password_required()) return;
?>

Remember that this would ideally be handled within a template override (a copy of tickets.php contained within an events directory inside your theme) – you can read more on that in our themer’s guide and we have a specific tutorial covering template overrides.

So hopefully that offers you an interim solution, meanwhile I’ll talk to the team and see what we can do here.

[Barry]

OK, let’s take this one issue at a time. Bearing in mind I don’t have a copy of Canvas it’s quite possible I’ve missed something, however changing ecp-single-template.php to look like this might solve issue (2).

Can you test that out? If you haven’t done so already please familiarize yourself with our Themer’s Guide and our tutorial on template overrides.

Thanks!

[Author]

Posts