|
Meng
|
June 21, 2014 at 12:05 pm
I once had this problem solved before but now it’s happening again. I’ve got Cocoa error 3840 after logging in on my iPhone app (EE HD ver 1.6.3). Also, from the event JSON feed, I’ve got this error message: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes) in /home/k2750393/public_html/float2nature.com/wordpress/wp-includes/shortcodes.php on line 227
How to fix this?
|
|
Lorenzo Orlando Caum
|
June 21, 2014 at 12:55 pm
Hello,
Please raise the memory that is available to PHP:
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
If you have already raised it, then please ask the host to raise it from their end.
—
Lorenzo
|
|
Meng
|
June 21, 2014 at 7:35 pm
Hi Lorenzo,
Thanks for your quick respond. I have asked the host to raise it. It’s now set to 128M. You can see it from the info.php screenshot. The error messages still appear both on event JSON feed and EE iPhone app. On my EE iPhone app, I can’t access my events (today/past/future).
|
|
Lorenzo Orlando Caum
|
June 21, 2014 at 11:54 pm
Hi Meng,
The site is still running out of memory. Here are some searches on the WordPress.org forums for the memory issue:
http://wordpress.org/search/Fatal+error%3A+Allowed+memory+size?forums=1
Since you have already raised it, I would check with the host about bumping up the limit to a higher level:
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
—
Lorenzo
|
|
Meng
|
June 22, 2014 at 10:41 pm
My host has confirmed that the memory limit has been set to higher level (256M) but the errors still occur. As I’ve mentioned earlier, I have once had this same problem solved before. This is so frustrating.
|
|
Dean
|
June 23, 2014 at 1:58 am
Hi,
The initial error you posted: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes)
This is already reaching 256mb in memory. This to me suggests that there is a memory leak somewhere on your site. It could be the theme it could be a plugin. Are you using a large number of plugins?
|
|
Meng
|
June 24, 2014 at 8:10 pm
Hi Dean!
As I’ve mentioned earlier, I had this similar problem once before and it was solved. Here’s the link of the topic: https://eventespresso.com/topic/fatal-error-message-in-json-api-test/. I have tried to deactivate some plugins, also changed the theme, but it didn’t work.
Here’s the list of installed plugins on our site:
Event Espresso version 3.1.36.5.P
WordPress version WP 3.9.1
Installed plugins
Akismet by Automattic version 3.0.0,
AutoChimp by Wanderer LLC Dev Team version 2.15,
Contact Form 7 by Takayuki Miyoshi version 3.8.1,
Event Espresso – Social Coupons by Seth Shoultes version 1.5.4.p,
Event Espresso – MailChimp Integration by version 1.2,
Event Espresso – Permissions by Event Espresso version 1.5.5.p,
Event Espresso – Social Media by Event Espresso version 1.1.7.p,
Event Espresso – Ticketing by Event Espresso version 2.1.p,
Event Espresso by Event Espresso version 3.1.36.5.P,
Flickr Photostream by Miro Mannino version 3.1.2,
Jetpack by WordPress.com by Automattic version 3.0.2,
Send From by Benjamin Buddle version 2.0,
WooDojo by WooThemes version 1.5.4,
WooThemes Helper by WooThemes version 1.2.4,
Countdown Widget by Matt Say version 2.5.4,
WordPress Importer by wordpressdotorg version 0.6.1,
WP Image Size Limit by Sean Butze version 1.0.4,
WP-reCAPTCHA by Jorge Peña version 3.2
|
|
Lorenzo Orlando Caum
|
June 24, 2014 at 9:56 pm
Hi, could you run some testing with only Event Espresso running and let us know if the issue continues?
Temporarily deactivate all plugins. Then reactivate Event Espresso and addons and test out the iphone app.
Does it still report memory issues?
Be sure to restore your other plugins after running the test above.
—
Lorenzo
|
|
Meng
|
June 24, 2014 at 10:26 pm
I’ve just tried that once again. The issues still persist.
|
|
Tony
|
June 25, 2014 at 10:45 am
Hi Meng,
Could you remove the [LISTATTENDEES] shortcode from your events and retry please?
This is to help narrow down the issue.
|
|
Meng
|
June 26, 2014 at 1:22 am
Hi Tony,
It’s working! Thank you!
|
|
Tony
|
June 26, 2014 at 4:01 am
Great! 🙂
To fix this if you open up wp-content/uploads/espresso/templates/attendee_list.php
Around line 50 you’ll find:
if (!$this_is_a_reg_page){
$event_desc = do_shortcode(stripslashes_deep($event->event_desc));
}
Either remove or comment out that code.
This has been fixed within EE previously, but it appears you copied that template over when using a version that did not have this fix applied.
|
|
Meng
|
June 29, 2014 at 3:55 am
Hi Tony,
Thank you for the info. I’ve tried to fix it but the error message reappeared. Fortunately, we don’t need the ‘feature’ that allows us to display our attendee list with their gravatar. It’ll be cool, though. I really hope this would be fixed in the future.
|
|
Lorenzo Orlando Caum
|
June 29, 2014 at 2:12 pm
Hi,
We’ll have this fixed for the next release of Event Espresso 3.
—
Lorenzo
|
