Forum Replies Created
-
Posts
-
You could try adding this to your theme’s functions.php file: that means the fields will still be visible to those users you designate but not to others.
Do note however that I have not tested this using the plugins you mentioned, only on a default installation.
Why would it ask each user for this? There should be just one for the whole site, yes?
It allows for scenarios where different admins can work with and pull events in from different Eventbrite accounts that they might be managing. The alternative for sites that need to work with multiple Eventbrite accounts would be to make the keys universal and have the admin select which key he or she wants to work with on every single operation.
It’s not perfect and may be revised in the future – but I understand that to be the basic reasoning.
There are a number of complications and challenges that mean this is not currently on any roadmap. That doesn’t mean there’s no chance of it happening, but we’d probably need to see much more demand for it that we have so far.
Unfortunately it’s not currently possible – at least not without some customization which would require relatively advanced development skills and a good working knowledge of both WordPress and The Events Calendar internals.
OK, so that’s a quite separate problem (from hiding the updated/scheduled fields) – can I ask you to create a new thread for this? Otherwise it will become quite confusing here.
Thanks! (I’ll now close this thread.)
OK. I think the rationale for this is that, if the ticket were physically shipped, you would still need to mark the order complete manually.
With that in mind (as discussed here and elsewhere) you could also try editing the product (in the WooCommerce product editor) and marking it as virtual and downloadable.
It then ought to automatically complete.
Hi Ricard – we haven’t forgotten about you – I’m just waiting for a response from one of the developers to see if we’ve got time to create a temporary workaround (possibly we may not).
Joseph: yep I’ve got that logged, it would seem to me to be a sensible way forward and once the team are ready to work on the next iteration of WooTickets this is something they can consider.
Thanks for your feedback – we’ve had a lot of great ideas being posted and it is all really great stuff 🙂
If you edit the ticket in the WooCommerce product editor, you can change the Catalog Visibility setting from Hidden to Catalog – it should then become visible within the storefront.
So one possible solution could be to leverage a meta query (you will probably be interested in testing against the _EventRecurrence meta key if so) or, alternatively and perhaps less efficiently, you could iterate through your result set and determine which events are recurring from there.
Hi Aaron, yep this is (currently) a little counter-intuitive. What are you setting the eventDisplay parameter to?
OK, just moving this across to our WooTickets forum and I’ll take a look at this.
Hi Matthew!
The first thing to do is read up on (and setup your theme for) template overrides (you may also want to read up on our themer’s guide).
Then, open up your custom events-list-load-widget-display.php template and find this code – simply remove it or comment it out.
Does that help here?
