Complete vs. Processing

[Tony Alexander]

Running ECP 3.0.1, EC 3.0 and WooTickets 3.0 and tickets are still being marked processing by default as opposed to complete. Reading similar threads on the topic I saw this was supposed to be addressed in the most recent update. I don’t see a setting for this? Is the plugin still passing tickets to WooCommerce as “processing”?

[Leah]

Hey Tony,

Thanks for your note. And thank you for noting that you are using all updated plugins, that’s great.

Part of the issue with the earlier WooTickets build was that the ticket product type needed to be manually changed from shipped to virtual (and downloadable) for the order to come through as complete. In Tickets: WooCommerce 3.0, the ticket products are virtual by default. Is it possible that the ticket that you’re seeing the problem with was created before you updated, and is still marked as a shipped product? You can check that in the WooCommerce –> Orders dash.

If you could check that and let me know, we’ll go from there. If you’re still having this trouble with new tickets, we’ll definitely need to check that out.

Thank you,
Leah

[Barry]

Hi Tony! Just to chip in here: that is expected in most cases – tickets use a virtual product type by default now since that is the closest and best model to what’s actually happening, however this in itself will not necessarily mean that orders are moved immediately to a status of complete (nor should it). The ordering process still follows the normal pattern of all WooCommerce orders.

In addition to Leah’s advice you could consider trying out/adapting one of the various workarounds in the forum for this or else contact the WooThemes support crew for a definitive “fix” – based on what you are saying, however, I wouldn’t say this is a bug so much as just normal operating behaviour for WooCommerce (which, since that’s a pretty flexible plugin, you can change – but we are not the best support channel to guide you through that).

[Tony Alexander]

Thanks Leah, Barry –
I waited to implement ECP and WooTickets until the update, so all of these ticketed events were created using the update. I checked before posting and tickets are being created in WooCommerce as simple, virtual products but downloadable is not selected by default. I suspect this is a bug?

[Barry]

No – it’s not a bug, that’s exactly as it should be.

Tickets are now created as virtual products – that is the best fit since tickets are neither downloadable products nor (in a WooTickets context) are they normally physically shipped to the recipient.

[Tony Alexander]

You are quick Barry!

I guess I am confused, both by related threads on this topic and the not by Leah above where he said tickets needed to be manually changed, in the earlier version, from shipped to virtual and downloadable for the order to come through as complete. After reading that I assumed the update marked tickets as “virtual and downloadable” by default. It makes sense the latter would not be true as the tickets are not downloaded, rather, emailed.

I will check with the WooNinjas, though I suspect they are going to say they don’t provide support for third party plugin developers.

I appreciate the help and swift response. Kudos

Tony

[Barry]

Yeah I mean what I’d say (about Woo Ninjas not supporting third party plugins – which is fair enough) is to remember that a ticket is, after all, a simple and virtual product.

So while there’s no harm in giving them the context (that you are using WooTickets) really this could be a quite general, non-WooTickets specific question: “I want my virtual products to be immediately marked as complete. How do I do this?”

[Tony Alexander]

This reply is private.

[Barry]

Yep, in fact that was shared in a thread not long ago and it’s fine by us to drop useful links into these threads:

http://www.skyverge.com/blog/how-to-set-woocommerce-virtual-order-status-to-complete-after-payment/

And it’s definitely worth trying – anecdotally it seems results have been mixed but mostly positive. We don’t however have an “official” solution of our own since this is something that would correctly be solved at WooCommerce level (whether natively or by a customization like in in that thread) rather than WooTickets level.

Glad you got a solution 🙂

[Author]

Posts