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
Attendee Listing Shortcode Fatal Error | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Attendee Listing Shortcode Fatal Error

Attendee Listing Shortcode Fatal Error

Posted: August 15, 2013 at 6:37 pm

Viewing 2 reply threads


Meng

August 15, 2013 at 6:37 pm

Hi Team,

I’ve been attempting to show attendees from a single event (with their gravatars) on my website page using this shortcode: [LISTATTENDEES event_identifier=”your_event_identifier” show_gravatar=”true” show_expired=”true”] and this following message keeps occuring:

“Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 40961 bytes) in /home/floatpro/public_html/float2nature.com/wordpress/wp-content/plugins/event-espresso/includes/shortcodes.php on line 215”.

Please, help.


Josh

August 15, 2013 at 8:12 pm

Hi there,

You can try increasing the amount of memory that can be consumed:

http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Please note, this setting may not work if your host does not allow for increasing the PHP memory limit–in that event, contact your host to increase the PHP memory limit. Also, note that many hosts set the PHP limit at 8MB.


Meng

August 20, 2013 at 9:14 am

Ah,of, course. I feel so stupid. I never thought of that. Thank you so much, Josh.

Viewing 2 reply threads

The support post ‘Attendee Listing Shortcode Fatal 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.

Event Espresso - Staging Server