Upgrade to 5.6.0.2 error
PermalinkMy setup is almost a plain vanilla default concrete5 site.
Should I worry ?
Apparently the upgrade did go through, but maybe the above error happened somewhere halfway the upgrade ?
Thanks ChrisH for posting your experience here. I encountered the same and ended up deleting all blocks where I only had override custom templates and then copying them back post update.
I went ahead and opened a bug report on this issue:
http://www.concrete5.org/index.php?cID=427279...
Please confirm the bug to keep the momentum going
http://www.concrete5.org/index.php?cID=427279...
Please confirm the bug to keep the momentum going
I got the same error message during upgrade. Inspired by this thread this was my trick to success (so far):
1) Rename /blocks/ to /tmp_blocks/ or something.
2) Run the upgrade. Use the force. It should be succesful.
3) Rename /tmp_blocks/ back to /blocks/
I'm not 100% sure if there are side effects in your case. I suppose it depends what is inside your blocks overrides.
1) Rename /blocks/ to /tmp_blocks/ or something.
mv blocks/ tmp_blocks/
2) Run the upgrade. Use the force. It should be succesful.
/index.php/tools/upgrade/?force=1
3) Rename /tmp_blocks/ back to /blocks/
mv tmp_blocks/ blocks/
I'm not 100% sure if there are side effects in your case. I suppose it depends what is inside your blocks overrides.
Apparently what was happening was the upgrade routine was looking at the root block/autonav overrides directory and expecting all the files required for the block (db.xml, etc.) rather than just custom templates.