Upgrade to 5.6. Has Killed My Website: Fatal error: Exception thrown without a stack frame in Unknown on line 0 - SOLVED
Permalink 1 user found helpful
I just did the update install to 5.6, which distorted and damaged my website. Then I tried to restore a backup that I made before the update within Concrete 5, and now when I try to access or login to my website, all I get is a white screen with the error message:
Fatal error: Exception thrown without a stack frame in Unknown on line 0
Please help me to restore my website:http://www.philipacampbell.ca
Any and all assistance will be much appreciated. Have a great day.
Regards,
-Phil
Fatal error: Exception thrown without a stack frame in Unknown on line 0
Please help me to restore my website:http://www.philipacampbell.ca
Any and all assistance will be much appreciated. Have a great day.
Regards,
-Phil
Did you manually update, or did you do it via the Dashboard?
If you did it via the dashboard, often times you can at least get your old site mostly function by removing/changing one line from your config/site.php file back to 5.5.2.1. The line reads like this:
If this is your first time upgrading via the dashboard, simply remove it. If this is your second or third time, then change it to:
But I'm not sure how you "attempted" to restore your backup.
You may also want to contact your webhost... Sometimes they have backups of your database or filesystem that can be easily restored to roll back to.
If you did it via the dashboard, often times you can at least get your old site mostly function by removing/changing one line from your config/site.php file back to 5.5.2.1. The line reads like this:
define('DIRNAME_APP_UPDATED', 'concrete5.6.0.1');
If this is your first time upgrading via the dashboard, simply remove it. If this is your second or third time, then change it to:
define('DIRNAME_APP_UPDATED', 'concrete5.5.2.1');
But I'm not sure how you "attempted" to restore your backup.
You may also want to contact your webhost... Sometimes they have backups of your database or filesystem that can be easily restored to roll back to.
You are a genius. This worked for me.
Thanks
Thanks
You should be able to restore that backup by importing it with phpMyAdmin. You may also need to hack the version definition in config/site.php as above.
Try it now..
Please accept my SINCERE THANKS, all of you, for your very valuable advice.
I did hack the site.php file, as suggested, to change it back to Concrete 5.5.2.1 and my site has now been fully restored to its previous look and functionality.
I did attempt the restore from the dashboard, but that didn't help whereas the hacking the site.php file did the trick.
A huge THANK YOU to all of you. I had many hours invested in building the website and was not keen to start all over. I will henceforth check these forums for bug reports before ever initiating any more Concrete5 "upgrades." It goes without saying that updates/upgrades should not be issued if they have not been fully tested and found to be stable. My website is a pretty simple one and I was not happy to be so seriously sideswiped by an update.
Lesson learned. Thank you again.
Regards,
-Phil
I did hack the site.php file, as suggested, to change it back to Concrete 5.5.2.1 and my site has now been fully restored to its previous look and functionality.
I did attempt the restore from the dashboard, but that didn't help whereas the hacking the site.php file did the trick.
A huge THANK YOU to all of you. I had many hours invested in building the website and was not keen to start all over. I will henceforth check these forums for bug reports before ever initiating any more Concrete5 "upgrades." It goes without saying that updates/upgrades should not be issued if they have not been fully tested and found to be stable. My website is a pretty simple one and I was not happy to be so seriously sideswiped by an update.
Lesson learned. Thank you again.
Regards,
-Phil
I have these update errors with almost every update/upgrade, at least at some web hosters. I read and wrote several forum posts, but there does not seem to be a solution except reverting to your old version. I can’t understand why, since 5.4.x, the development team has not solved this yet, as it seems to happen to a lot of users.
Back up all of your files
Export all of your tables for this site from your database.
In the event of an issue it is easy to restore. I usually import all of the tables into my database (after deleting them all) first - that usually works.
Unfortunately this advice comes a little to late for you, but a good note for future upgrades.