|
frogbox
|
March 1, 2017 at 5:31 am
Hi,
I have recently been getting this error in registering for an event. Having looked at the forums I see similar problems, one relating to caching and the other relating to Memory. In my instance it I have no WP caching plugins activated and my php memory_limit is 128mb. I am using WP 4.7.2 and Event Espresso – 4.9.31.p Version 4.7.2.
Any ideas?
Thanks
Tim
|
|
Tony
|
March 1, 2017 at 6:56 am
Hi Tim,
There are lot of reasons that can happen.
If you check within the servers error logs do you see any errors from EE?
I ran a quick test registration on your event and didn’t run into any problems, is it happening on a specific event for you?
|
|
frogbox
|
March 1, 2017 at 7:06 am
Originally I saw a memory error
“[Wed Mar 01 10:00:00.617331 2017] [proxy_fcgi:error] [pid 46891:tid 139749744322304] [client 82.6.198.52:59386] AH01071: Got error ‘PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 49283045 bytes) in /var/www/vhosts/community-options.org.uk/httpdocs/wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/TicketSelectorRowStandard.php on line 450\n'”
My memory_limit is currently set to 192mb so can’t see this being the issue?
Thanks.
|
|
Tony
|
March 1, 2017 at 7:37 am
That’s a PHP fatal error stating your site is running out of memory, why would that not be the issue?
The amount of memory used depends on many factors but in short your site needs more memory, try increasing the memory limit to 256MB and see if you run into the same problems.
|
|
frogbox
|
March 1, 2017 at 7:41 am
I thought that wouldn’t be an issue as it’s asking for 49mb but there is 192mb available?
I have upped it to 256MB as requested. Is that value something you would expect to see needed?
Thanks
|
|
Tony
|
March 1, 2017 at 7:45 am
I thought that wouldn’t be an issue as it’s asking for 49mb but there is 192mb available?
Its trying to request an additional 49283045 bytes of memory rather than a total of 49MB.
I have upped it to 256MB as requested. Is that value something you would expect to see needed?
It depends, we have seen sites using that amount of memory.
If your using a visual editor the minimum amount of memory they recommend is 128MB, then any additional plugins, EE also uses memory so it all adds up.
|
|
frogbox
|
March 1, 2017 at 7:48 am
Aha, got you. Makes sense. Lets see how 256MB works then.
Thanks Tony.
|
|
Tony
|
March 1, 2017 at 7:56 am
You’re most welcome.
Please do let us know if you have further problems.
|
|
frogbox
|
March 1, 2017 at 8:44 am
Hi Tony. Seems that the increase in Memory doesn’t seem to have changed anything. This issue is happening on any event I choose.
Hmm, for some reason the booking page was being served over http and not https as it should be. I have reloaded it and have processed the page of https and it registers successfully. Are you being served https?
Thanks
|
|
Tony
|
March 1, 2017 at 9:48 am
I’m getting https.
How are you getting to the events? Using /courses/ or another url?
From /courses/ I’m having no problems.
Can you run through the steps you are taking to throw the error please?
|
|
Josh
|
March 1, 2017 at 9:54 am
Hi there,
Event Espresso doesn’t actually serve anything to your website, the registration processing is all happening on your web server. You can follow this guide to make sure the front end of your website is served over https:
https://eventespresso.com/wiki/espresso-sslhttps/
|
