Upgrade woes
Permalink
Wow, I am really starting to rethink my decision to build sites with C5. I recently attempted to upgrade one site to the latest version and it totally exploded. Then I reverted to the previous backup, and now I get this message at the bottom of every page :
"Fatal error: Call to undefined method Controller::outputFooterItems() in /home7/firstci7/public_html/concrete/elements/footer_required.php on line 8"
There is no support except for this forum (which is awesome by the way), and I am twisting in the wind...
"Fatal error: Call to undefined method Controller::outputFooterItems() in /home7/firstci7/public_html/concrete/elements/footer_required.php on line 8"
There is no support except for this forum (which is awesome by the way), and I am twisting in the wind...
While you have reverted the database, have you removed the upgrade line from the end on config/site.php?
Thank you for your reply John.
When I look at config/site.php I do not see anything that has to do with the upgrade, only the serve, username, password, database,base url, dir_rel, and "passeord_salt".
However in the file concrete/config/version.php it syas app_version 5.4.05, which is the version I am running.
Ultimately, I'd like to run the latest version, but I can't seem to figure out how to do that without completely breaking the site. This seems kind of goofy to me :-).
When I look at config/site.php I do not see anything that has to do with the upgrade, only the serve, username, password, database,base url, dir_rel, and "passeord_salt".
However in the file concrete/config/version.php it syas app_version 5.4.05, which is the version I am running.
Ultimately, I'd like to run the latest version, but I can't seem to figure out how to do that without completely breaking the site. This seems kind of goofy to me :-).
If the 5.5.1 upgrade had completed, the last line of /config/site.php would end with:
Upgrades leave the old version in /concrete and place the upgrade version in /updates/concrete5.5.1/concrete. C5 then redirects anything to do with the C5 core to the version according to the code above.
To revert, as well as restoring the database, you would need to delete this.
<?php define('DIRNAME_APP_UPDATED', 'concrete5.5.1');?>
Upgrades leave the old version in /concrete and place the upgrade version in /updates/concrete5.5.1/concrete. C5 then redirects anything to do with the C5 core to the version according to the code above.
To revert, as well as restoring the database, you would need to delete this.
I am not finding that line in the /config/site.php. nbor am I finding anything at all int upgrades folder.
OK. I think we can rule out the upgrades ddefinition.
Seeing you were upgrading from 5.4.05, Were you following the procedure inhttp://www.concrete5.org/documentation/how-tos/developers/update-ve... ?
Upgrades used to overwrite the /concrete/ folder (rather than just make pointers to the relevant /upgrades/x.x.x/concrete/ folder), so if your database is 5.4.05, to revert you may have to replace/revert files in the /concrete/ folder. (with an old version download of C5)
Another problem may be that some older themes may not have the footer_required code. It is usually safest to swap to the default theme when making any version upgrade, so that you can at least see your site if the custom them is not compatible with the new C5 version, then swap the theme back after a successful upgrade process.
Seeing you were upgrading from 5.4.05, Were you following the procedure inhttp://www.concrete5.org/documentation/how-tos/developers/update-ve... ?
Upgrades used to overwrite the /concrete/ folder (rather than just make pointers to the relevant /upgrades/x.x.x/concrete/ folder), so if your database is 5.4.05, to revert you may have to replace/revert files in the /concrete/ folder. (with an old version download of C5)
Another problem may be that some older themes may not have the footer_required code. It is usually safest to swap to the default theme when making any version upgrade, so that you can at least see your site if the custom them is not compatible with the new C5 version, then swap the theme back after a successful upgrade process.
