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
My site crashed… | Event Espresso - Staging Server

Support

Home Forums Event Espresso Lite My site crashed…

My site crashed…

Posted: August 22, 2013 at 3:10 am

Viewing 2 reply threads


Renoir Nusse

August 22, 2013 at 3:10 am

I installed the lite version and my site showed this message:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 491520 bytes) in /home/kwon/public_html/dev/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/admin/manage-images.php on line 499
How can I disable nextgen without access?

  • This topic was modified 11 years, 5 months ago by Dean.
  • This topic was modified 11 years, 5 months ago by Dean. Reason: moved from translations
  • This topic was modified 11 years, 5 months ago by Dean.


Dean

  • Support Staff

August 22, 2013 at 3:53 am

Hi,

So you installed the Lite version of Event Espresso? If so I would suggest trying to increase the memory allocation, see this article – http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

You will need FTP or control panel access to your site to do this.


Josh

August 22, 2013 at 8:05 am

Also, with FTP access you can force Nextgen to be disabled by renaming the plugin folder.

http://www.wpbeginner.com/plugins/how-to-deactivate-all-plugins-when-not-able-to-access-wp-admin/

Viewing 2 reply threads

The support post ‘My site crashed…’ 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