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 Internal Server Error | Event Espresso - Staging Server
I have a new install of ES (version 4.2.1.reg) and the latest version of WP. I had the events working, then I added a second event and it seems to be coming up with a 500 error.
The error log is giving the following:
Out of memory (allocated 170131456) (tried to allocate 101457921 bytes) in /home/USERNAMEREMOVED/public_html/wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/templates/ticket_selector_chart.template.php on line 131
I’ve allocated 128M in the wp-config.php file as well (which should be more then enough… )
I also have the following addons installed:
ES Calendar
ES Members Addon
ES Multi-Event Registration
ES Social Media
If you are using Event Espresso 4 you should disable the Members, Multi-Event and Social Media add-ons because they are not compatible with EE4. There is an EE4 calendar add-on available if you’ve purchased it separately so if the calendar you have is designed for EE3 then you should also disable that add-on.
Please disable the add-ons that are not compatible with EE4 and let us know if that helps.
The support post ‘500 Internal Server Error’ 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.