[Barry]

Can you list any other plugins that you have installed – particularly any event-related ones (besides ours, of course)?

[Barry]

Excellent – thanks for working through that with us and all the best with the project 😀

[Barry]

No problem, sorry we can’t do more here.

[Barry]

Excellent 😀

[Barry]

OK, turns out Community Events will use your page template in any case (normally page.php). Somewhere in there there is likely to be a call used to grab the sidebar, something like this:

get_sidebar();

You could try wrapping that in a conditional statement like so:

if (!tribe_is_community_my_events_page()) get_sidebar();

Does that help?

[Barry]

OK, so for the front page how about modifying the snippet slightly – try this slightly modified code instead – does that help at all?

[Barry]

Hi Tony,

I just want to ensure I’m picturing the problem correctly as there have been various posts about this (as you pointed out) but some subtle though important differences between them.

Can you direct me to a URL or URLs that illustrate the issue?

[Barry]

Do you mean the download Jonah provided in his tutorial? What I’d suggest is giving it a go and restoring the originals if it doesn’t work.

[Barry]

Jonah and I posted at the same time there Nitin – but I’d definitely recommend his approach if possible, it’s a touch simpler and the field already exists 🙂

[Barry]

You could definitely enable regular old post custom fields if you wanted to use those to record an email address on a per-post basis.

The first step would be to add a snippet to your theme’s functions.php file so that you can view the user interface for this.

You would also need to make sure that the custom fields checkbox is checked in the screen options pulldown.

Does that help at all?

[Barry]

Hi Paul,

Can you clarify if this relates to some custom code of your own or if you are seeing this in regular event pages generated by our plugin (if so, can you provide a URL so I can take a look)?

Thanks!

[Barry]

I’m afraid that isn’t possible without some extensive customization work.

When you have a recurring event you effectively are sharing the title, description, venue and organizer information between all instances – so a change either has to apply to all of them or else you need to break it down into multiple – but separate – chains of recurring events.

[Barry]

Hi Eddy: can you tell me what Events > Settings > Template > Events Template is set to?

[Barry]

Hi Philippe,

What I can say is that the exporter and print functionality have now been written and are looking good so far. Right now it’s going through the quality assurance process to iron out any bugs and other oversights.

For a number of reasons however it makes sense to release this in tandem with the next major release of The Events Calendar/Events Calendar PRO – and they too are undergoing the last stages of QA and development.

What that means is that how quickly we can get the next WooTickets release out of the door hinges to an extent on progress in the other projects – that makes it difficult for us to commit to a specific date. Right now we expect to get these new versions live somewhere in the next two months – but we can’t offer anything more specific, I’m afraid.

So while I completely appreciate your position there’s not too much more I can tell you.

[Barry]

Hi J-P, that’s great feedback – I tend to think it validates a lot of the work that has already gone into WooTickets and we’d agree that using a single e-commerce engine, WooCommerce in this instance, has a number of advantages for most vendors.

[Author]

Posts