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
Espresso log file issue | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Espresso log file issue

Espresso log file issue

Posted: January 30, 2013 at 2:12 am

Viewing 1 reply thread


Jacopo Lualdi

January 30, 2013 at 2:12 am

Hi everybody,
During the last days my website incurred in the 500 Internal Server Error and my hosting provider noticed that the wp-content/uploads/espresso/logs/espresso_log.txt reached more than 2gb size, which caused the website’s crash. Obviously the espresso_log.txt file records ANY action done by EE on my website, so I’d like to ask you if there is a way to avoid this, or to let it record just few actions in order to prevent this issue in the future.
Thanks


Dean

  • Support Staff

    •

January 30, 2013 at 2:54 am

Hey Jacopo,

The log file should only be turned on when trying to troubleshoot errors. You can turn it on/off in the General Settings by turning the option “Use full logging?” to NO.
Viewing 1 reply thread

The support post ‘Espresso log file issue’ 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.

The original Forum description...

Status: closed

Updated by Dean 12 years ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server