Forums

Site hosed due to Apache update

Permalink
Hey all,

I manage most the websites for the college I work for which are all run on WordPress. One of the sites for the college uses C5 (version 5.4.2.2 as of now) as its CMS and the people in charge of that site were maintaining it themselves (or apparently not maintaining it). Yesterday, one of the other web techs reconfigured Apache on our web server yesterday and that C5 site is now hosed. We've rolled back the Apache changes (I don't know what he changed), but the entire is so full of errors its unreadable:

http://belmontshowcaseseries.com...

We've tried to find where to turn off the error reporting to try to salvage the site, but we're not able to get into the Dashboard to administrate the site. We know we need to upgrade C5 to the most current version, but all our attempts to update the site yield a blank white page. We've also tried creating a new installation and importing the old site's database into the new site's database, but we're getting SQL import errors.

Can someone help us figure this out? Is there a way to recover the old site so we can get in and upgrade it?
 
mlocati replied on at Permalink Reply
mlocati
You can try modifying the /config/site.php file.
Add the following lines just after the line define('PASSWORD_SALT', ...

if(defined('E_DEPRECATED')) {
   error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED);
} else {
   error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT);
}
slushman replied on at Permalink Reply
Thanks for the help mlocati! Unfortunately, that didn't resolve it. All the errors are still there. We've actually turned off the PHP error reporting on the server, but it seems like C5 actually turns it all back on.

Even if I just put:
error_reporting(0);
ini_set('display_errors', '0');

In the site.php file, the errors still show up. I'm getting pages of these kinds of errors:

Strict Standards: Non-static method Cache::get() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/models/package.php on line 78

Strict Standards: Non-static method Cache::key() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/libraries/cache.php on line 117

Strict Standards: Non-static method Cache::getLibrary() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/libraries/cache.php on line 121

Strict Standards: Non-static method Cache::key() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/libraries/cache.php on line 137

Strict Standards: Non-static method Loader::package() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/startup/packages.php on line 8

Strict Standards: Non-static method Object::camelcase() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/libraries/loader.php on line 299

Strict Standards: Non-static method Loader::package() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/startup/packages.php on line 8

Strict Standards: Non-static method Object::camelcase() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/libraries/loader.php on line 299

Strict Standards: Non-static method Loader::package() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/startup/packages.php on line 8

Strict Standards: Non-static method Object::camelcase() should not be called statically in /home/showcase/public_html/updates/concrete5.4.2.2/concrete/libraries/loader.php on line 299
mlocati replied on at Permalink Reply
mlocati
Maybe debug logging is enabled in concrete5.
You can hack the file /concrete/startup/debug_logging.php.

Replace this line
$debug_level = Config::get('SITE_DEBUG_LEVEL');

with this line
$debug_level = 0;
slushman replied on at Permalink Reply
OK, I figured out what was happening. The version being used on the site was in the updates folder, so all the changes I was making in the config folder weren't actually doing anything. When i turned off debugging error messages in the updates/5.4.2.2/concrete/config/base.php file, the error messages disappeared and I was able to log into the dashboard. The site is now up to the current version and back online. Thanks for your help mlocati!