Upgrade to 5.6.1.1 broke site... need help figuring out what's broken....

Permalink
A couple of weeks ago I upgraded to 5.6.1.1 and it immediately broke my site where I couldn't even get into the dashboard.

At the time, I played around with some of the edits listed in the forums, but now I'm trying to remember what I did.

I had made a backup of the DB and here's the version information:

,('SITE_APP_VERSION','2012-10-03 01:09:34','5.6.0.2',0,0)
,('SITE_INSTALLED_APP_VERSION','2012-09-14 03:23:01','5.6.0.1',0,0)
,('APP_VERSION_LATEST','2013-03-20 19:00:01','5.6.1.1',0,0)

I've fixed it to the point of being able to access the dashboard, but my pages are still blank. Here's what I did to fix it...
* Loaded the backup into the database.
* Removed the concrete version in the upgrade directory and deleted the corresponding entry in /config/site.php.
* Uploaded 5.6.1.2 into the /concrete directory.
* Ran the upgrade script to bring the database up to 5.6.1.2.

When I try to load the home page, I get the following php error in the host logs. (The page is blank.)
PHP Fatal error: Call to a member function getCustomAreaStyles() on a non-object in /home3/huddleus/public_html/wps/concrete/core/models/collection.php on line 490

The page source ends suddenly, like this:

<style type="text/css">
#wrapshad{
background: #;
background: -webkit-gradient(linear, 0 0, 0 bottom, from(#), to(#));
...
-pie-background: linear-gradient(#, #);
behavior: url(/packages/jb_floating_back/themes/jb_floating_back/js/PIE.htc);
}

#wrap0 {
background: url("missing data


I thought it might be a problem with the floating back theme, so I went into Themes and did a preview of one of the other themes. I get this error in the preview:

Fatal error: Call to a member function getCustomAreaStyles() on a non-object in /home3/huddleus/public_html/wps/concrete/core/models/collection.php on line 490


Does anyone have any idea how I can fix my site?

Hork
 
Hork replied on at Permalink Reply
Hork
Anyone? Any ideas? How do I go about troubleshooting this?
Hork replied on at Permalink Reply
Hork
Would it work to try to replace the /concrete directory with 5.6.02 and edit the /config/site.php file accordingly? And restore the database from the backup again?
Hork replied on at Permalink Reply
Hork
I did this and it worked, but then I updated to 5.6.1.2 with the automatic updater and I got the same error as described above. How can I troubleshoot what is causing the error?