Fatal error: Call to a member function getCustomAreaStyles() when Adding a Stack
Permalink
I have 2 new C5 sites (both using the newest stable C5 release - Version 5.6.1.2) and both are throwing an error when adding a stack to a page, but the stack is actually fine after publishing the pages.
Fatal error: Call to a member function getCustomAreaStyles() on a non-object in /home/Selinsgrove/www/www/concrete/core/models/collection.php on line 490.
Neither of these sites were upgrades. The first site didn't throw the error initially. The other did right out of the box.
Any ideas on what this message means and how to fix?
Thanks.
Fatal error: Call to a member function getCustomAreaStyles() on a non-object in /home/Selinsgrove/www/www/concrete/core/models/collection.php on line 490.
Neither of these sites were upgrades. The first site didn't throw the error initially. The other did right out of the box.
Any ideas on what this message means and how to fix?
Thanks.
No, this is fairly new for me with these 2 sites - I have seen others have this issue in the forums with different problems, like your home page. I tried one update and everything went wrong so I re-installed the former version from the server backups and haven't tried updating since. Waiting for things to settle down here and for stable to be stable.
I usually like to go for the newest up front, but have determined it's not in the best interest of my business or my client's.
I usually like to go for the newest up front, but have determined it's not in the best interest of my business or my client's.
Any news on this? It's really stopping my development efforts.
No, I guess I should post in the bugs area - Okay, posted as a bug for help. Crossing fingers!
See -http://www.concrete5.org/index.php?cID=491382...
See -http://www.concrete5.org/index.php?cID=491382...
Just wanted to let you know that this is a KNOWN bug recognized by the developers - I got a badge for posting it. But no answer yet, though I expect a fix soon.
I will keep you posted as I hear anything. :-)
I will keep you posted as I hear anything. :-)
anybody ever come up with a fix for this?? Same issue. add a stack, get the error. refresh, all seems fine!!
Nobody seems to be able to help me troubleshoot it.