Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Available Spaces Not Correct, non-paying attendees entered into event report | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Available Spaces Not Correct, non-paying attendees entered into event report

Available Spaces Not Correct, non-paying attendees entered into event report

Posted: July 8, 2013 at 4:58 pm

Viewing 4 reply threads


evan hatch

July 8, 2013 at 4:58 pm

Hello,

Hoping you can direct me on how to fix this issue, there are two.

The number of available spaces is not showing correct. Here is what is happening, I am testing out events I am creating because I just bought this product. I create a registration but before I confirm payment (which comes after submitting Reg details) I Navigate away to another section of my site. (Problem 1) Even though I have not completed the transaction (paid) the person is still registered as attending and the available seat count decreases by one.

It seems your system is registering people that fill out the form but do not actually pay, this is an issue.

(Problem 2) When I look at the Attendee report all the tests I have done are there as registered, which decreases the number of available seats, and thus is putting useless data into my database of sales.

Is there a fix for this? I don’t want people as “attending” until payment is actually received.


Dean

  • Support Staff

    •

July 9, 2013 at 2:08 am

Hi,

By default the attendee status for registered but not paid is Incomplete. An incomplete attendee is registered but does not count towards the attendee count (available spaces).

If the status is set to Pending, then they havent paid BUT they still count towards the count.

This status can be changed in the event itself (Default Payment Status for Event:) or in the General Settings (Default Payment Status (this value will be automatically filled in for each person’s payment status, until payment is made, for each event):) will set it for every event unless over ridden in the event itself.

So I would double check what your settings are.


evan hatch

July 9, 2013 at 9:37 am

Excellent, this is great news. I sent mine to pending as it sounded more user friendly but didn’t realize there would be an impact to registrations. I will reset to Incomplete. thanks.


evan hatch

July 9, 2013 at 2:28 pm

Is it possible to set EE to purge any incomplete transactions after a period of time? The counting towards tickets available issue was cured by the fix above but I am still seeing “cancelled” and abandoned transactions appear as attendees.


Josh

July 9, 2013 at 2:48 pm

There isn’t a feature that automatically deletes incomplete registrations. These need to be done by someone with admin access. You can delete them in bulk by going to the attendee overview, filter the list to only show the incomplete status, then select all by checking the box at the top of the table, then delete.
Viewing 4 reply threads

The support post ‘Available Spaces Not Correct, non-paying attendees entered into event report’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Josh 11 years, 6 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server