Forum Replies Created
-
Posts
-
My tickets are html based and I have been sending them in HTML. That was the issue because there are no pdf tickets.
OK – well in that case I’m not too sure how readily this can be done – but we have put in a request to make it easier to resend tickets (in 3.0) and that is currently under consideration.
Also, refunded tickets or deleted orders don’t decrease the qty_sold or increase the total sales meta value.
No, but my understanding is that this is simply how WooCommerce works. If you manually create or adjust orders you need to manually control stock.
Hi ddfaktde,
Looks like you have hit on a bug: I’ll report this to the developers and hopefully we’ll be able to get a fix out sometime soon 🙂
Thanks for your patience!
Hi jpfaraco,
Here’s a snippet that adds the ticket form to other views such as the list view. Of course, that isn’t quite what you want to do – but it shows how the form can be attached to an action and indeed you could potentially extract and use directly the very same callback:
TribeWooTickets::get_instance()->front_end_tickets_form()
Does that help at all here?
Default themes including Twenty Twelve should work perfectly and can quickly be customized without touching any code – beyond that I’m afraid we have no recommendations to offer as each theme is different and has its own quirks – but we can certainly leave this open and see if other members of the community have recommendations to make 🙂
Hi everyone. It is indeed a typo and one we apologize for – we don’t make a habit of hardcoding table prefixes and this slipped through the net, however we’re quite literally taking corrective action as I type and a fix will be released for this as quickly as possible.
We definitely appreciate that this will have caused unnecessary disruption and, again, we can only apologize – and appreciate your patience while we get on top of this one.
Secondly, if my attendees want to change ticket types e.g. from Basic to Premier, how can i go about doing so?
You can modify orders, or else delete the original and generate a new one, via WooCommerce. Again this won’t be as gracefully handled in WooTickets 1.x as it is in WooTickets 3.0.
Hi buooy,
Since you are using WooTickets 1.0.1 you should be able to observe the generated PDF tickets within your media directory (often wp-content/uploads/(YEAR)/(MONTH) – but the actual location can of course vary according to your local configuration).
So you could definitely resend them without having to actually regenerate them: recording which ticket belongs to which order would be a little more involved and you would probably need to set up a couple of listeners, one to catch new orders and one to look for attachments – then piece the information together that way.
That may sound a little hacky however it would take some slight coding gymnastics to bring about what you want here 🙂
Thirdly, when we trigger a paypal refund in wootickets, the number of tickets sold does not decrease! how can this be rectified?
There is no easy way to workaround this except having a manual process to catch this and optionally making changes directly to your database (or setting up some custom code to facilitate this).
WooTickets 3.0, I would add, handles refunded and cancelled orders with far more grace – a good reason to update!
Definitely.
As you note this is working just fine on a different installation, so perhaps there is a conflict with either a theme or plugin or even an environmental issue (if for instance it is hosted by a different service or in a different configuration). So … can you:
* Deactivate everything except The Events Calendar, WooTickets and WooCommerce
* Switch to a default, unmodified theme such as Twenty Twelve
* Test if the problem remains
* Assuming the problem has gone, reactivate everything one-at-a-time until the problem returns (it may not)
* At the point where the problem comes back, take note of whichever component – be it your theme or a plugin – you last activatedIf we can isolate the cause of the problem we can then consider our options 🙂
Well, WooTickets integrates with WooCommerce and it is WooCommerce which imposes various requirements making up the checkout process.
It may well be possible to short circuit things and remove WooCommerce’s requirements for other data to be obtained during checkout – however I’m afraid that is beyond what we can help with here: first and foremost you would probably need a good working knowledge of developing against WooCommerce to accomplish your goals, or else create a custom solution from scratch.
OK, that’s a bit puzzling. If possible, let’s run through our basic troubleshooting steps:
* Please deactivate all plugins except for The Events Calendar, WooTickets, WooCommerce and Events Calendar PRO
* Please switch to a default, unmodified theme such as Twenty Twelve
* Now test to see if the problems remain
* If the problem is resolved, reactivate each component one-at-a-time, testing at each stage to see if they have returnedIf the problem does come back, take note of whichever component – be it your theme or a plugin – was last activated: there is likely to be a conflict with this item and if we can identify it then we can look at further options.
Hi Hamish,
What I’d actually recommend here, if everything is working nicely on the test site, is adding all the same plugins and then the same theme as on your production site – adding only one component at a time, testing at each stage to see if the problem has returned.
If it does return (though it may not) you should take note of whichever component, be it a plugin or your theme, triggered the behaviour.
Would that be possible here, or have you already re-established all of the same plugins and theme?
Looks like it affects dates with less than 4 events, too. Before we do anything else can I ask you to login, visit Settings > Permalinks (no need to actually adjust or save anything, though – just visiting this page causes a flush of permalinks) then try visiting those links again?
How strange.
Do you have any custom code inside that theme (perhaps added to functions.php) that localizes strings?
If your theme doesn’t explicitly “declare” support for WooCommerce then yes you will see a warning notice to that effect, generated by WooCommerce. Often it can simply be ignored, however.
You seem to be using quite an old version of WordPress – can you also confirm which versions of our plugins – for both The Events Calendar and WooTickets – you are using (just visit the plugin admin screen to determine this)?
Thanks!
