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
Removing unpaid registrations, found strange payment=Admin records | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Removing unpaid registrations, found strange payment=Admin records

Removing unpaid registrations, found strange payment=Admin records

Posted: December 5, 2012 at 1:43 am

Viewing 1 reply thread


Jeremy Dillworth

December 5, 2012 at 1:43 am

Because of the way Event Espresso works, it creates a database row for every registration before the user has paid. Some users change their mind and never pay, or may hit the back button several times to change things on the form. You end up with a number of stale, unpaid registrations.

To keep things tidy, I’ve setup a cron job on my server that looks for registrations “WHERE payment_status = ‘Incomplete'” from a week or more ago. Some of the rows returned by this query are very strange. Their payment column says “Admin”, so I asked the only other user that logs into WordPress if he manually entered any accounts. He did enter some, but a number of them had their names in all caps, which he would never do.

So, if I didn’t create them and he didn’t create them, how do these records exist with payment = ‘Admin’?

Thanks

Jeremy


Josh

December 5, 2012 at 7:47 am

One way that this could happen is the record was created on the front end, and updated later by an Admin.

Viewing 1 reply thread

The support post ‘Removing unpaid registrations, found strange payment=Admin records’ 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.

Event Espresso - Staging Server