Error: "concrete/libraries/block_view_template.php on line 41" after deleting theme
Permalink
http://www.concrete5.org/community/forums/usage/error-concretelibrariesblock_view_template.php-on-line-41-after-/
I am in a world of hell right now. I designed a site (emphasis on design... I am NOT a developer) for a client,http://www.tomasos.com and was working on it earlier tonight. Something was really wonky with my connection and things were not uploading etc. So, I thought it had something to do with the theme and I "decided" to delete the dot_awesome warm theme from inside dashboard/themes and right after that, it gave me this exact error and I can't login or bypass login and get to the dashboard.
Fatal error: Call to a member function getBlockTypeHandle() on a non-object in /home6/barking8/public_html/tomasos/concrete/libraries/block_view_template.php on line 41
I also had a bunch of stuff in the clipboard and that might be a contributing factor. I had recently installed the Scribd Addon, TnSpacer, and had created 4-5 individual dot-awesome buttons on the index page in a layout cell. I am willing to pay someone to get into the database for me and find the offenders. I have to have this site up by morning.
It just seems to me that it has something to do with one of the custom blocks with the dot_awesome warm theme. Everything was fine until I removed the theme, which had been installed as a package, not a simple theme because it has custom blocks.
If anyone is awake at this hour and wants to tackle this, PM me and I will call you back.
I am in a world of hell right now. I designed a site (emphasis on design... I am NOT a developer) for a client,http://www.tomasos.com and was working on it earlier tonight. Something was really wonky with my connection and things were not uploading etc. So, I thought it had something to do with the theme and I "decided" to delete the dot_awesome warm theme from inside dashboard/themes and right after that, it gave me this exact error and I can't login or bypass login and get to the dashboard.
Fatal error: Call to a member function getBlockTypeHandle() on a non-object in /home6/barking8/public_html/tomasos/concrete/libraries/block_view_template.php on line 41
I also had a bunch of stuff in the clipboard and that might be a contributing factor. I had recently installed the Scribd Addon, TnSpacer, and had created 4-5 individual dot-awesome buttons on the index page in a layout cell. I am willing to pay someone to get into the database for me and find the offenders. I have to have this site up by morning.
It just seems to me that it has something to do with one of the custom blocks with the dot_awesome warm theme. Everything was fine until I removed the theme, which had been installed as a package, not a simple theme because it has custom blocks.
If anyone is awake at this hour and wants to tackle this, PM me and I will call you back.
Actually, I did uninstall it from within the dashboard but did NOT remove the package.
If I go to tomasos.com/index.php/dashboard I get the sign in page, but then it throws the error after trying to sign in as well so I can't bypass login and access the dashboard.
Come to thin of it... I deleted the theme from the themes page and DID NOT delete/remove the package.
Hope the below post will help you.
http://www.concrete5.org/developers/bugs/5-5-2-1/fatal-error-call-t...
Rony
http://www.concrete5.org/developers/bugs/5-5-2-1/fatal-error-call-t...
Rony
I know nothing about the database side of Concrete5. I wish it did, but it does nothing but frustrate me more. Thanks though.
That is why I posted this in Jobs... I want to hire someone before the tomorrow morning to help me figure this out.
I really want to help you to solve this error. But I don't have time due to a tight schedule. Hopefully someone else in C5 marketplace may help you.
Rony
Rony
Hi
Can't help as I also have a full schedule, but could you look at reverting to any backups?
Maybe rebuilding your content would be quicker and cheaper than paying a developer?
Remember to back up your database in its current state.
Just a thought.
Can't help as I also have a full schedule, but could you look at reverting to any backups?
Maybe rebuilding your content would be quicker and cheaper than paying a developer?
Remember to back up your database in its current state.
Just a thought.
Did you solve your problem? If not I might be able to help.
Thanks... but I got it solved by reverting to a backup. I stressed all night about it but had it resolved in under 5 minutes with Bluehost. They had multiple backups of their own, one that was better than what I had, and they took care of it. Kudos to Bluehost!!! Thanks for everyone's responses too.
Congratulations :)
Rony