[Barry]

Hi Chris – can you link me to an example of this? I took a quick look at the URL you shared but couldn’t see the problem (quite possible that I missed it though).

Can you also confirm if you tried switching back to a default and unmodified theme at the same time as deactivating all non-Modern Tribe plugins?

Last but by no means least, you should be able to export events using the WP export tool – but if for some reason in your particular environment you cannot then yes, some other tool (such as phpMyAdmin, a dedicated backup plugin or even the mysqldump command line utility if you have that level of access and it is installed on your server) would be a good way to go.

Thanks!

[Barry]

Hi soesit:

Unless you are using PHP 5.5+ you will not be able to do that – empty() only works with variables, not with the direct result of function calls.

Try placing it in a variable first $ticket_link = tribe_get_custom_field(‘TicketLink’) and then test to see if $ticket_link is empty. Also note that tribe_custom_field() echoes the field (if it exists) by itself, so you don’t need that extra echo.

Does that help at all?

[Barry]

Hi braniganinteractive,

I’d need a little more context to answer that – there are no particular restrictions but just as with many WP functions they often have to be used at the right place and time.

Can you share any of your code and give me the background of how/where it is being used?

[Barry]

Hi Darryl,

This should only occur with empty week views and is something we hope to address in a forthcoming maintenance release.

In the meantime, following from this thread, you could basically tweak one of those snippets and transform it into something like this – if you drop that in your theme’s functions.php file you should see that empty week views no longer return a 404 status.

Does that help at all here?

[Barry]

Hi Darryl,

Great question! The best starting point for this sort of work is out Themer’s Guide – but essentially you would probably want to override and customize our default-template.php template (and also set Default Event Template as the template to use from within the Events > Settings > Display screen).

Does that help at all?

[Barry]

Hi Amanda, just to help me get up to speed on this one – can you you link to whatever thread/code you originally used to focus on a specific category?

Thanks!

[Barry]

Hi Dave,

If I’m understanding you correctly and you basically want to keep related events but remove the thumbnails, you could try adding this snippet to your theme’s functions.php file.

Does that help at all here?

[Barry]

Hi Richard: just to add, a short snippet like this will hide/remove the ticket form:

remove_action('tribe_events_single_event_after_the_meta', array(TribeWooTickets::get_instance(), 'front_end_tickets_form'));

So you could use that conditionally, given a piece of code that detects if the current user is indeed a certain category of member, ie:

if (false === is_customer_type('gold_customer')) {
remove_action('tribe_events_single_event_after_the_meta', array(TribeWooTickets::get_instance(), 'front_end_tickets_form'));
}

The opening line – the is_customer_type() function – is of course something I just made up, you’d need to devise your own equivalent (or work with the relevant plugin authors to build it) but hopefully it gives you a broad idea of how this might be done.

A more comprehensive solution might additionally include a check run when items are added to the cart to provide more complete protection – however that sort of customization really relates to WooCommerce and we’d have to leave it to you to develop a solution there, too, though perhaps the team over at WooThemes could help with that.

Hope that gives you some ideas 🙂

[Barry]

Hi akbradley57,

Sorry for the delay first of all. If I’m understanding you correctly I don’t think that thread is directly related … are you able to share the URL for one of your “all events”?

Thanks!

[Barry]

Hi quantafire,

I’m not absolutely clear as to the context, but if for instance categories are being viewed in list form then within (a custom copy of) list/content.php you should simply be able to use WordPress’s have_posts() function.

Does that help here?

[Barry]

Hi Skatch – I can’t see a custom events stylesheet or anywhere else containing that rule – can you confirm which place you added it to?

[Barry]

OK – in that case I’ll go ahead and close this thread. Of course if you do want to take this up again any time please feel free to create a new one. Thanks!

[Barry]

Great! And thanks for reporting back with those details, we’ll add that to our issue tracker 🙂

[Barry]

Right – but if I’m understanding you correctly what we want to do here is stop them from impacting in this way on event pages.

It’s quite likely they are adding those elements by using a hook and so we need to unhook their code only when a certain condition is met – such as the current request being for a single event – and possibly rehook it so it runs later on instead.

If you could touch base with the plugin authors and see if you can get some code to unhook their stuff then we can potentially combine that with the code I posted above and work toward a solution here 🙂

[Barry]

What theme are you using?

[Author]

Posts