Forum Replies Created
-
Posts
-
Our beta testing period has officially completed.
Even so, we can probably send you the last build that we sent out for beta testers to use, however please be aware that we will not provide any support for this on the forum as 3.0 still has not been officially released and the last beta build will likely contain bugs that have since been fixed in our development code.
If that’s not a problem, please do email Rob at pro (at) tri (dot) be with your request (and, ideally, link back to this thread) and he’ll take things from there. Thanks!
Hi Somatic,
There are a few points you bring up and they are neatly encapsulated by this paragraph:
So you guys are somehow adding the ticket to the cart, but completely bypassing all the functionality of woocommerce_add_to_cart_action(). I’m not sure that’s well-advised, as there’s a bunch of product->cart validation that goes on in there, and of course, the desired redirect filter.
No redirect is taking place in this scenario – the WooTicket ticket form simply submits directly to the cart page – so to skip straight to your final question you could change this either by overriding the tickets.php and specifying an action URL of your choosing or else you could set up a filter on woocommerce_get_cart_url (which might even serve to catch not only scenarios like this but redirects to the cart page, too).
I’m not too concerned about the fact that woocommerce_add_to_cart_action()‘s magic isn’t running as a result of this – a series of checks will anyway take place within the cart object’s check_cart_items() method – but if you can describe a case that is going to be missed we’re definitely open to feedback.
Does that help/clarify things?
It would be a touch more involved than adding a custom field – you would need to look at how the PDF is generated and attached and potentially unhook that and hook up your own implementation in its place (which might essentially be a slightly modified version of the original code).
Unfortunately it’s beyond the scope of support to guide you through this one – do know however that the ticketing system is going to change in WooTickets 2.0 and will potentially be easier to amend.
Not at all, happy you’re on track – let me know if there’s anything else on this front or create new tickets as needed 🙂
Just a sidenote that I spoke with the dev team this morning and they agree this is an area where all use cases weren’t fully considered – so a change is being implemented as I speak. I don’t think it will make the very next release – as that is subject to a feature freeze so we can get it out of the door as quickly as possible – but it should be available in the subsequent minor update.
Hi dgusty – you can add anything you want pretty much, but please be aware that customizing the PDF currently requires solid development skills. You could of course customize the HTML portion of the email being sent out or send an additional PDF – again that sort of customization would require a reasonable amount of PHP and WordPress know-how.
Hi Paul, no problem, it would be something like this – of course you would need to change that filepath to match your customized template’s location.
Hi Paul,
So within the event editor to re-enable the cost field you would need to basically do a template override of the meta box template. Essentially:
– You should copy the-events-calendar/admin-views/events-meta-box.php and place your copy somewhere appropriate
– Change your custom copy – remove the if condition surrounding the cost fields (around lines 107-122 in the default version of the template)
– Add a filter to make sure your customized template is used. That would look something like:
add_filter('tribe_events_meta_box_template', 'change_event_mb_tpl');You would then need to define change_event_mb_tpl() – this should accept the default template filepath which it can then return unmodified or, if it relates to events-meta-box.php change it to the filepath of your custom copy.
So this is definitely something that requires some PHP/WordPress know-how and I appreciate that isn’t for everyone. What I definitely will do however is log this as something that needs attention in a future version.
Yep the idea of changing the status to virtual and downloadable is just to force sales to be marked as completed earlier than they would otherwise, in the case of most payment gateways. It’s not ideal and is nothing more than a quick workaround.
In the next version of WooTickets all ticket products will be virtual by default as we feel that is the best model for what is actually being purchased – the issue of making the order immediately complete however is something that really needs to be solved at WooCommerce/payment gateway level.
Hi James,
You can certainly request a refund: they are assessed on a case by case basis so if you’d like to contact my colleague Leah please use the email address below and just provide a brief summary of the problem and also link back to this thread.
Thanks!
I’m not aware of any general problems in this area; certainly if it works for one it should work for another – though of course we can’t really guarantee what Google or other services will actually do with the data.
We can leave this open and if you detect any errors that do indeed result from our code, or if others have the same problem, we will definitely be happy to look into this in more detail.
Thanks!
Hi James!
It seems that using recurring events applies ticket purchases to all of those events. Is there a way around this?
Right, so WooTickets does not currently support recurring events. So the simplest way (but perhaps most time consuming, on an administrative level) would be to create individual events and allocate tickets for each day.
To make WooTickets work with recurring events without that kind of step would, currently, require some amount of customization and some solid WordPress development skills.
I wanted to set up varying prices for each day, so there could be a child and adult price, for example. This doesn’t appear to be supported either.
You can set up multiple tickets – so you can have an adult ticket with one price and a child ticket with a different price, for example.
What you can’t accomplish with that sort of set up is a collective or ‘pooled’ inventory, however, and again that is an existing limitation.
Does that help, at least as far as giving you a better idea of what WooTickets can and should currently do?
