Warnings and a fatal error after installing version 5.5.1
Permalink
This afternoon I updated my concrete5 site I'm building to Version 5.5.1 using the dashboard. Now when I try to access the site I get all sorts of warnings and one fatal error:
Warning: set_exception_handler() expects the argument (View::defaultExceptionHandler) to be a valid callback in /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/dispatcher.php on line 46
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/dispatcher.php:46) in /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/startup/session.php on line 22
Warning: Cannot modify header information - headers already sent by (output started at /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/dispatcher.php:46) in /home/daveb209/public_html/staging/concrete5.4.0.5/libraries/view.php on line 721
Fatal error: Call to undefined method View::addFooterItem() in /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/elements/page_controls_header.php on line 27
Clearly I'm missing something that will help make this work. I'd appreciate any insight as soon as possible.
Warning: set_exception_handler() expects the argument (View::defaultExceptionHandler) to be a valid callback in /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/dispatcher.php on line 46
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/dispatcher.php:46) in /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/startup/session.php on line 22
Warning: Cannot modify header information - headers already sent by (output started at /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/dispatcher.php:46) in /home/daveb209/public_html/staging/concrete5.4.0.5/libraries/view.php on line 721
Fatal error: Call to undefined method View::addFooterItem() in /home/daveb209/public_html/staging/concrete5.4.0.5/updates/concrete5.5.1/concrete/elements/page_controls_header.php on line 27
Clearly I'm missing something that will help make this work. I'd appreciate any insight as soon as possible.
Yes, that's true. The upgrade feature in the Dashboard requires you to upgrade once to 5.4.2.2 before upgrading to 5.5.1. So I did both based on what the Dashboard required and now the site doesn't work.
I just got this message upgrading from a 4.2.2 site did you manage to rectify it?
Though only the following single error
Warning: set_exception_handler() expects the argument (View::defaultExceptionHandler) to be a valid callback in /updates/concrete5.5.2.1/concrete/dispatcher.php on line 52
Though only the following single error
Warning: set_exception_handler() expects the argument (View::defaultExceptionHandler) to be a valid callback in /updates/concrete5.5.2.1/concrete/dispatcher.php on line 52
solution, for my issue can be found here.
http://www.concrete5.org/community/forums/installation/upgrade-erro...
It was to do with an extension to the core files.
http://www.concrete5.org/community/forums/installation/upgrade-erro...
It was to do with an extension to the core files.
From the look of the error message it looks like 5.4.0.5??
If you checkout
http://www.concrete5.org/developers/downloads/...
You'll see
===>Upgrading note: You need to be running version 5.4.2.2 to upgrade to 5.5.0.
So if you were upgrading an older version, then you're probably in deep trouble unless you have a backup. If you've got a backup, restore it, and then upgrade to the 5.4.1, then 5.4.1.1 etc until you get to 5.5.0. Then upgrade to 5.5.1