Updating bricked my site

Permalink 2 users found helpful
I just tried to update my concrete site with the update process through the settings menu and now this is all I get:

Warning: require_once(/home/p2ranger/cotting.us/updates/concrete5.6.1.2_updater/concrete/models/config.php) [function.require-once]: failed to open stream: No such file or directory in /home/p2ranger/cotting.us/updates/concrete5.6.1.2_updater/concrete/startup/required.php on line 15

Fatal error: require_once() [function.require]: Failed opening required '/home/p2ranger/cotting.us/updates/concrete5.6.1.2_updater/concrete/models/config.php' (include_path='/home/p2ranger/cotting.us/libraries/3rdparty:/home/p2ranger/cotting.us/updates/concrete5.6.1.2_updater/concrete/libraries/3rdparty:.:/usr/local/lib/php:/usr/local/php5/lib/pear') in /home/p2ranger/cotting.us/updates/concrete5.6.1.2_updater/concrete/startup/required.php on line 15

I'm using a theme that came with it and no 3rd party add ons

Don't know where to start. Thanks

Jason

 
mkly replied on at Permalink Reply
mkly
Hello,
If you go to
/home/p2ranger/cotting.us/updates/concrete5.6.1.2_updater/concrete/models/config.php

is that file there?

Best Wishes,
Mike
p2ranger replied on at Permalink Reply
No, that file is not there. If I were to get a copy of that file and put it in there, would that do the trick? If so how do I get that file?

Thanks

Jason
mkly replied on at Permalink Reply
mkly
Yes, this would correct the issue. I wonder if you had a corrupted download. You should go to downloads page
http://www.concrete5.org/developers/downloads/...
And replace the concrete5.6.1.2_updater with the folder in the zip file. Rename that folder from concrete5.6.1.2 to concrete5.6.1.2_updater

This should get you up and running.
@dmen, this should also resolve the issue for you as well.

Best Wishes,
Mike
p2ranger replied on at Permalink Reply
Thanks for the tip. That got me one step further along. Now it gives me a mysql error:

mysql error: [1054: Unknown column 'Blocks.btCachedBlockRecord' in 'field list'] in EXECUTE("select CollectionVersionBlocks.isOriginal, Blocks.btCachedBlockRecord, BlockTypes.pkgID, CollectionVersionBlocks.cbOverrideAreaPermissions, CollectionVersionBlocks.cbDisplayOrder, Blocks.bIsActive, Blocks.bID, Blocks.btID, bName, bDateAdded, bDateModified, bFilename, btHandle, Blocks.uID from CollectionVersionBlocks inner join Blocks on (CollectionVersionBlocks.bID = Blocks.bID) inner join BlockTypes on (Blocks.btID = BlockTypes.btID) where CollectionVersionBlocks.arHandle = 'Header' and CollectionVersionBlocks.cID = '1' and (CollectionVersionBlocks.cvID = '13' or CollectionVersionBlocks.cbIncludeAll=1) and CollectionVersionBlocks.bID = '24'")

What can I try now?

Thanks

Jason
p2ranger replied on at Permalink Best Answer Reply
Found a solution. In the INSTALL file that was on my site I found where it said to use this URL when upgrading.

http://yoursite.com/index.php/tools/required/upgrade...

I was able to get this page to pull up that then finished the upgrade process.

This is after I took mkly's advice:
* I downloaded the concrete zip installation file to my computer.
* I then changed the name of the folder that the zip file creates, concrete5.6.1.2, so that it says concrete5.6.1.2_updater
* I uploaded this folder to /my_server's_location_of_concrete_install/updates to replace the one that is already there
* I visitedhttp://yoursite.com/index.php/tools/required/upgrade... to complete the upgrade process

Thanks for helping me get my site fixed. I hope no one else runs into this, but if they do I hope this helps

Jason
fmatlock replied on at Permalink Reply
fmatlock
Thank you for posting this. This was exactly the problem I had and this solved it right away!

Was the site you were upgrading on GoDaddy by chance? Mine was and the really odd thing is that I had just upgraded two other sites on GoDaddy without problems and then this one exploded. Just a mystery probably but I was curious.

Thanks,
Frank
dmen replied on at Permalink Reply 1 Attachment
Hi, was going to start a new thread, but this is almost identical to what happened to us last night. Did the update through the settings menu and the site bricked. Nearly the same error too - failed to open stream, but in line 18 of dispatcher.php. GIF image attached for the specifics.
I managed to get the site back up by deleting server side files and reuploading them from our local version. But I lost a good three hours last night doing that.
mhawke replied on at Permalink Reply
mhawke
After upgrading, it's always good to clear your cache before trying to diagnose problems.

Can you clear your cache by going directly to the "Clear Cache" page using this url?

www.www.yourdomain.com/index.php?cID=68...
p2ranger replied on at Permalink Reply
No, it still gives me the same error messages when I use that URL modified for my domain.

Jason