Support

September 26, 2016 at 12:22 pm

Hi there,

Does your site receive a relatively small amount of hits?

EE changed up how it generated the messages a little while ago and uses WP Cron, the needs page hits to trigger the event (it can be any hit at all, admin, use, bot, anything) which may be causing this.

If you don’t process large batches of registrations you can switch back to the previous method if you prefer.

Go to Event Espresso -> Messages -> Settings.

There you will find the option ‘Generate and send all messages’, set that to ‘On same request’ and save the settings.

Now run a test registration and confirm if you receive the emails instantly?

September 28, 2016 at 5:34 am

Thanks for posting, Steve.

Using a transactional email service will often be much quicker and more reliable as their business model depends more heavily on the emails (as opposed to most hosts who offer emails as a convenience/add-on).

We have some details on using these services and list some providers here:

https://eventespresso.com/wiki/postmark-app-mandrill-transactional-email-handling-services/

October 4, 2016 at 4:11 am

Hi Howard,

All of those 3 issues listed sounds connected:

1) At the payment step, it just spins and spins, even though Carmen’s payment went through successfully to AuthNet. The customer does not know that it went through, and sometimes will try again and double register unknowingly.

It sounds like there is an error being thrown that is breaking the ajax request which means EE does not know a payment has been made and sits waiting for a reposnse, which means….

2) The backend is showing that attempted registrations by customers are “pending payment”, and were abandoned. Payment for those did not succeed, and the customers may be lost.

If there is an error and EE doesn’t know there is a payment the registration will remain pending payment. Which also means:

3) A test registration went through and is listed in EE under that event as being registered, but on the Events summary list, it shows “0” as approved registrations. So employees who look at the list don’t see the real number of registered customers.

‘Pending payment’ registrations do not apply to the event, only ‘Approved’ registrations do. A registration would automatically be ‘Approved’ if the payment was recorded and shown as a full payment within the transaction.

Can you create a test event we can use to register onto please, you can set it to password protected and post the password here for us to view.

We will need a paid and free ticket on the event to test the registrations (we will not make like payments, but can test to see if any errors are being thrown up until making a payment).

You can use a regular event if you prefer, just not we may run multiple test registrations.

Also, if you look within the servers error logs do you see any errors around the same time these registrations were made?

October 4, 2016 at 9:53 am

I ran a test registration on that event and can see the issue you mention, but no errors are shown.

Can you enable WP_DEBUG on the site so I can retest then?

You can add this snippet to your wp-config.php file:

https://gist.github.com/Pebblo/8787f5530ea777c84aaf62f075e55b32

That tells WordPress to save the errors rather than displaying them which should then save the error to a debug.log file within /wp-content/

October 6, 2016 at 4:26 am

Where can i find the wp-config.php file?

wp-config.php is within the root directory of where you installed WordPress, the location can change depending on your setup but its often in the root directory for your site.

And do I add that snippet of code into the wp-config.php file?
Any special location?

Yes the above snippet should go within wp-config.php, it should be pleaced anywehere above the line that has /* That's all, stop editing! Happy blogging. */

Like this – http://take.ms/Cmkqa

If you are unsure we can add this snippet for you if you can provide FTP details, you can use this form to send them securely:

https://eventespresso.com/send-login-details/

October 7, 2016 at 7:06 am

Your site is currently throwing a syntax error when the code you have added above:

Parse error: syntax error, unexpected '<' in wp-config.php on line 85

A syntax error basically means something is there that should not be.

I’m guessing your have included this:

<?php //Do not include the opening PHP tag

If so please remove it.

October 7, 2016 at 10:01 am

That will cause problems because constants should only be defined once. You’ll need to remove one of those.

October 10, 2016 at 12:11 pm

Hi Howard,

In order for us to see the error notifications, you’ll need to send in FTP access, or you can check the error log that’s in the debug.log file in the wp-content folder of your website.

October 11, 2016 at 8:21 am

Here’s the error we’re seeing in the log after trying a test registration:

[11-Oct-2016 14:16:37 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) in

We’ll try bumping up the memory by making to the wp-config.php file. That may or may not help depending on your host. If that doesnt help, the way forward is you contact your host and request that the server’s memory limit be expanded to more than the current 64MB.