|
Christina Morris
|
March 22, 2018 at 9:30 am
I recently migrated the server and wonder if there is a setting that isn’t on. It was working fine before the migration. Can you let me know what might trigger this? I don’t see any error in the logs.
|
|
Josh
|
March 22, 2018 at 9:38 am
Hi Christina,
What usually triggers this is a server issue. Does the new server have similar software (e.g. PHP version) and resources (e.g RAM) as the old server? Does the new server have server-level caching enabled?
|
|
Christina Morris
|
March 22, 2018 at 9:41 am
It’s a higher PHP from: 5.6 to 7.2 with FPM enabled.
More RAM and I don’t think there is any server-level caching.
|
|
Josh
|
March 22, 2018 at 9:45 am
Does the new server have anything in place that restricts AJAX calls to the wp-admin from the front end of the site?
If you can post a link to the event page we can investigate further.
|
|
Christina Morris
|
March 22, 2018 at 9:46 am
I don’t think so RE Ajax calls, not sure where to check that…
https://bgcdallas.org/events/corporate-cup/
|
|
Josh
|
March 22, 2018 at 10:01 am
I’m not seeing any errors when I submit the registration form there.
One thing that may help narrow down the issue is you can turn on WP debug mode. There’s some information in the documentation that shows how:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
|
|
Christina Morris
|
March 22, 2018 at 10:02 am
IT’s not the registration, it’s the payment.
|
|
Josh
|
March 22, 2018 at 10:10 am
This is the error in the console:
https://slack-files.com/T02SY781D-F9TTUKSLR-6fdb75b75b
If I were to guess what’s causing the 500 error is the new serving is missing a PHP function, used by the Authnet gateway, that the old server had.
If you enable WP_DEBUG mode, then test, then check your site’s wp-content/debug.log file we’ll be able to find out which function is missing.
|
|
Christina Morris
|
March 22, 2018 at 10:13 am
I have this in my config
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
define( ‘WP_DEBUG_LOG’, true );
and it’s not writing a log!
|
|
Josh
|
March 22, 2018 at 10:25 am
That’s usually due to file permissions where the server will not allow WP to create a file. You can work around this by manually adding a blank file to the /wp-content/ directory, and name the file debug.log.
|
|
Christina Morris
|
March 22, 2018 at 10:53 am
Thank you for your help. It was a php.ini with a different PHP version than the one set in WHM. The version it was trying to use didn’t have the iconv() function operating!
Thanks again for your help. It takes a village…
|
