|
RCAhostmaster
|
January 27, 2017 at 9:52 pm
After upgrading to EE 4.9.28.p, our entire site crashes and will not respond. The only thing that brings the website backup is when I SSH into our directory and rename the EE folder, forcing it to de-activate.
I’ve disabled all of the other plugins, hoping it was a conflict with another plugin, but that did not work. No error code or message is listed after turning EE back on.
I’d like to download a previous version, but there isn’t anything listed on the portal for previous versions. I do know version 4.9.26.p was working fine on our site.
Site specs:
WordPress version 4.2.12
CentOS 6.7
PHP 5.6.19
MySQL 5.5.47
|
|
Tony
|
January 30, 2017 at 4:30 am
Hi there,
When the site isn’t responding what happens? Is it just a whitescreen or does it time out?
Have you check the servers error logs to see if there are any errors being thrown with EE activated?
You could enable WP_DEBUG and then re-enable EE, with WP_DEBUG enabled any errors should be displayed on the page.
Can I also ask why you are using WP 4.2.12 rather than 4.7+? WP backport security fixes but staying on older versions you miss out on any new features.
|
|
Tony
|
January 30, 2017 at 4:56 am
I tested 4.2.28 on the same version of WP you are using and did find a problem on activation which I’ve created a ticket for our developers to fix. Although its likely to be the same error, I can’t be 100% sure if it’s the same issue on your site without seeing what error is being thrown on your site so I would recommend following the above steps and posting the error here.
To get your site back up and running you can download a version of 4.9.26 HERE (you you’ll need to rename the directory to event-espresso-core-reg when installed)
|
|
RCAhostmaster
|
January 30, 2017 at 6:41 am
Thanks for the link. Yes, it is just a white screen. Once I have this operational, I will clone the main site and enable WP_DEBUG on one of our dev servers to see what exactly is shown. It may be of help to you all.
The reason we are running such an old version of WordPress is because our custom theme needs a complete recode to support the newer versions. Until that is done, we are stuck with 4.2.12.
I only manage the server side and backend for them (I.T.). The web development is done by someone else. Finding a web developer that actually knows what the hell they are doing is hard these days.
|
|
Josh
|
January 30, 2017 at 8:30 am
You’ll probably need to stay on the older version of EE (4.9.26) until your WordPress version updated to at least WordPress 4.4.
|
