Support

August 27, 2018 at 2:47 am

Hi there,

Yes, the solution is to change the ‘Default Registration Status’ on the event to ‘Approved’. That way, any registrations that complete all of the steps will be approved and apply to the sold values, this is the option you need to change: http://take.ms/UGECC

You’ll then be able to tell if a registration has actually paid by the ‘Transaction status’, when you apply the bank payment in the admin it will update the transaction status to Complete, unpaid will remain ‘Incomplete’.

August 27, 2018 at 3:13 am

Currently setting the Default Registration status to Approved is the only way you can tell EE to count those offline registrations in the sold values automatically.

– We don’t want to send venue and other details to unconfirmed registrants that did not pay yet.
– We want to check registrants prerequisites before approving.
– Not Approved default registration status would be useless then.

You didn’t mention any of those requirements in your first post, so if you can’t use a Default Registration Status of ‘Approved’ we don’t currently have any other method that will work for your requirements. The only registration status EE will use to compare with the sold values is Approved.

August 28, 2018 at 11:35 am

Thank you for the feedback, I’ll pass this along to our developers to discuss further, however even if a change is due there is no other quick fix for this.

So right know using bank draft type of payment either risk of overbooking event or to keep track of paid registrations outside EE.

Currently, the only way to prevent that is to use a Default Registration Status of Approved.

And is the Not Approved default registration status useful for anything if it ruins EE ability to track numbers and allows overbooking?

It is unlikely that ‘Not Approved’ registrations would count towards the sold values in EE, the Not Approved status is intended to be used as an interim status that allows the user to register, the admin to check for X requirements and then set the registration to the status they prefer from there (usually Pending Payment or Approved).

It was never intended to apply to the events sold values, the registrations are not approved so as far as EE is concerned that status will never apply to ‘sold’.

Is not there workaround such as https://eventespresso.com/topic/pending-payment-registration-counted-for-a-spot/?

I’m not sure how that applies? That thread is asking how to change the session lifespan for ‘reserved’ tickets, they want to make the length of time a ticket is reserved shorter. If you are asking if you could use something similar to extend the session to days I wouldn’t recommend doing so.

With how EE works, there is no workaround that can reserve a ticket indefinitely that is not attached to a registration with a status of Approved, that’s core functionality that we can’t just work around.

This is really crucial for offline payments.

We can’t change how offline payment methods work without significant changes to core and also need to consider how that will affect other users that do also use online payment methods. We would need either another registration status that did apply to sold values and all of the logic that follows with that, or some other method of tracking a registration made with an offline payment method and monitor that. It’s likely an additional status would be the way forward, but again, there’s a lot of moving parts to consider for this so its not something we can provide a workaround for, or a snippet to help with.

To use an offline payment method and reserve a ticket/registration with EE currently, you will need to use a Default Registration status of Approved.

August 30, 2018 at 1:11 pm

Hmm, without exporting them to CSV first I can’t think of way to filter these easily.

To confirm I’m on the same track as you, you want to filter registrations based on both Reg Status and Txn Status? So both of these – http://take.ms/0BitE

Meaning you could filter for ‘Approved’ registrations with a TXN Status of ‘Incomplete’?

August 31, 2018 at 4:20 am

Ok, so try this:

https://gist.github.com/Pebblo/22995de5472c46a361ecc206bc8e9f9b

Add that to a custom functions plugin on your site:

https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/

That adds an additional filter to the Event Espresso -> Registrations list table that allows you to select the TXN status – http://take.ms/GEzGI

Setting that allows you to set a specific transaction status to filtr for, it also works with the other filters, so setting a Reg Status of Approved and TXN status of Incomplete works as one would expect – http://take.ms/idhVn

Note that whilst I’ve tested this myself and it seems to work fine, it’s not officially supported or tested by EE, I didn’t find any issues with it but there may well be some I haven’t found, just something to keep in mind (it doesn’t update anything in the DB so wont have any permanent issues that will need fixing if its removed).

September 3, 2018 at 3:40 am

You’re most welcome.