Forum Replies Created
-
Posts
-
To request a refund please email my colleague Leah (pro at tri dot be) with a link to this thread and a quick summary of the problem/reason behind your request.
Refund requests are assessed on a case-by-case basis but if you contact Leah in the first instance she will take things from there.
Thanks!
OK, yeah I can replicate the very same thing. Luckily though this is resolved in 3.0 (which should be available soon). When this happens are you able to restore the previous widget now that the site isn’t dieing?
(To clarify, that first function I referenced should go in your theme’s functions.php file or another suitable location.)
Hi Mamalm,
You would need to do a little customization here, so if you haven’t already done so please read up on our Themer’s Guide and this tutorial on safely overriding templates as they will give you the background knowledge you need to do this.
You then need a means of accessing ticket information from those new locations. This function returns an array of ticket objects for the current post (or you can specify a specific post ID for the relevant event).
You could then iterate through that array – here is an example that retrieves and displays the price to give you an example of the basic process – except you would be interested here in information about stock levels so you would probably prefer to use $ticket->get_stock_quantity() (as opposed to $ticket->get_price_html() ).
Whether you want to expose the actual stock level or display an out-of-stock message (and or a combination of those, if for instance you have multiple tickets per event) is something I’ll leave to you 🙂
Overriding the ticket.php template is definitely related and that would be the best approach to solving this – so simply copy the original, place it in the {YOUR_THEME}/events/ directory and customize away!
Does that help?
Hi Phil,
The add_to_cart_wootickets_btn() would indeed need to be in your functions.php file – or some other suitable location – before you can use it.
Please note that however that it will not generate the same WooTickets form as you would normally see when viewing a single event page – it simply creates an add to cart link and so is generally redundant in the context of the events/single.php template (as, if tickets are available, they will be listed in the normal ticket form).
Great!
Regarding the additional language tacked on by WooCommerce you may be able to dispose of that by customizing/overriding the relevant template.
Mike: does the approach outlined by Paul (in the skyverge.com link) work for you?
It’s design simply assumes “pretty” permalinks – which have in a sense become the de facto standard for permalinks – and some of the libraries used under the hood to help with permalink-related logic just don’t play nicely with default permalinks, unfortunately.
It should indeed be released shortly so if you want to hold on that may be the best course of action 🙂
As I don’t feel there’s too much more we can do for you here I’ll go ahead and close this thread (unless I hear back from you in the next few days).
Thanks!
It should be released in step with The Events Calendar 3.0 – which is expected soon 🙂
I can’t provide a firm date at this point, unfortunately, but we are in the final steps of preparing for release.
How strange. The (WP) calendar widget definitely shouldn’t be removed. Are you running any other plugins and have you tried deactivating them and reverting to a default, unmodified theme such as Twenty Twelve?
(Please use a service such as Pastebin instead of posting code directly in the forum.)
So to bring this back to the error you originally reported:
Fatal error: Call to undefined function add_to_cart_wooticket_btns()
All I can really tell you is that that is not a function provided by the current version of WooTickets or WooCommerce, so essentially you would need to strip that code out or replace it with something that does work.
