Support

April 5, 2016 at 9:48 am

Hi Nancy,

You are correct, it looks like there is a fatal error being thrown during the ajax request.

Can you enable WP_DEBUG so we can run a registration and see if we can catch the error please?

April 5, 2016 at 10:22 am

Unfortunately your theme is throwing notices that are breaking the ajax request (separate issue from the error 500)

Can you swap out the WP_Debug code you have now, for this:

define( 'WP_DEBUG', true ); // Or false
if ( WP_DEBUG ) {
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
}

Which basically enables WP_Debug, but stops it printing errors to the screen and adds them to a debug.log file within /wp-content/

This is the notice being thrown:

Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0!

Its usually within the theme and just means a widget need to be updates to follow the latest coding standard. I’d recommend you issue a ticket with your theme developers to get that fixed.

April 5, 2016 at 2:20 pm

Hmm, there’s nothing being logged in the debug log when the ajax error is thrown.

Have you modified the default message templates within Event Espresso at all?

I’m wondering if this is an issue with triggering messages (although it would be strange as the payment message seems to work fine).

Can you enable the Invoice payment method so I can finalize a registration without having to pay and confirm that works.

April 5, 2016 at 2:59 pm

Ok, I think I’ve found it.

With the invoice payment method there’s a fatal error shown within debug.log:

[05-Apr-2016 20:54:26 UTC] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 80 bytes) in /wp-includes/wp-db.php on line 2350

That’s about 40MB which is rather low when using Event Espresso. I’d recommend updating to at least 96MB, you usually can do that by adding:

define( 'WP_MEMORY_LIMIT', '96M' );

to the wp-config.php file, anywhere above the line /* That's all, stop editing! Happy blogging. */

I normally add it just above where I add WP_Debug.

More info:

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

If that then works you can de-activate the Invoice payment method, set WP_Debug to FALSE and also delete the debug.log file from within /wp-content/

April 6, 2016 at 7:34 am

You’re most welcome.

Remember to disable the error logging and remove the debug log (unless you want to start the rrors) as that file is publicly accessible.