|
Florent Jonery
|
May 27, 2015 at 6:52 am
hello!
The problem suddently apprears a few days ago.
the site became very very slow and buggy (error 500 / pages loads in more than 1 minutes).
Before that, the site was relatively fast with page loading around 4 secs.
The problem dissapears with event expresso plugin desactivation.
the impact is important because we cannnot registrer anymore to events on the site.
The site is configured to autoupdate wordpress and modules.
we use event expresso 4.6.28.p
and WordPress 4.2.2
actives modules :
Akismet Version 3.1.1
Black Studio TinyMCE Widget Version 2.2.4
Book Review Library Version 1.4.12
CAS Maestro Version 1.1.3
easyReservations Version 3.5
Kadence Slider Version 1.4
Limiter les tentatives de connexion Version 1.7.1
Redirect to login if not logged in Version 1.6.3
Flo Jo
|
|
Lorenzo Orlando Caum
|
May 27, 2015 at 9:38 am
Hi Florent, you mentioned that you are seeing 500 errors on your site. Those may be fatal errors. Could you temporarily enable WP debugging on your site by adding this macro towards the middle of your wp-config.php file?
https://gist.github.com/lorenzocaum/848801a1173be464fbe7#file-gistfile1-php
Then try a registration or two to trigger the error. From here, go to this location using an SFTP or FTP client like Cyberduck or FileZilla:
/wp-content/debug.log
Copy and paste any errors shown there into a reply.
Then turn WordPress debugging back off:
https://gist.github.com/lorenzocaum/848801a1173be464fbe7#comment-1239850
—
Lorenzo
|
|
Florent Jonery
|
May 29, 2015 at 4:48 am
Hi Lorenzo,
We can’t find any errors in the logs files. Memory, CPU all seems normals. The WP memory is set to 128Mo.
We’d like to rollback the Event Expresso plugin to an older version.
Could you tell me how I can do that? Where could I find the 4.6.27.p version?
Thanks !
|
|
Florent Jonery
|
May 29, 2015 at 7:30 am
Hi!
We found the cause of this issue :
The “Use full logging” option was enabled in the General Settings. And the file became too big to be used normaly by eventespresso.
|
|
Josh
|
May 29, 2015 at 9:26 am
Yeah we definitely do not recommend leaving the full logging feature turned on. It should only be activated while doing troubleshooting if need be, then deactivated when troubleshooting is done.
|
