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 500 server error on payment settings page | Event Espresso - Staging Server
I’ve looked at previous posts regarding 500 server errors and I’ve done everything – changed to default template, deactivated all plugins, updated all current plugins, etc, etc. I still get a 500 server error when trying to access the payment settings page. I need any suggestions you have on how to fix this.
Thanks!
I updated my license so it would show up correctly. For some reason it was still showing up as localhost. I’ve updated my account and license on the website. The one I added was GM. Let me know if you have any idea why I’m still getting the 500 server error. I can’t figure it out. Thanks!
I looked into this and it turns out that your server apparently has the fopen function locked down. Event Espresso does a check on the payment gateways settings page to see whether your site can load up as https in order to present the correct gateway options. I’ve disabled this check for now in the paypal gateway’s settings.php file so you can load up the payment settings page now.
It may be possible to check with your host to see if they’ll configure the server to allow fopen. There are other functions that will use that as well (one I can think of off the top of my head is the invoice generator).
Viewing 5 reply threads
The support post ‘500 server error on payment settings page’ 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.