Upgrade from 5.7.9 -> 5.7.13 has just killed my site.
Permalink
I just tried upgrading to 13 as suggested from the control panel. Boy do I wish I didn't.
I've now lost my site completely. Its just a white page with nothing on it.
index.php has
and I'm stuck. I tried looking at the concrete5.7.5.13_remote_updater directory, but the index.html file seems to be empty.
I'm on shared hosting so no shell, what do I do to get it back??
I've now lost my site completely. Its just a white page with nothing on it.
index.php has
and I'm stuck. I tried looking at the concrete5.7.5.13_remote_updater directory, but the index.html file seems to be empty.
I'm on shared hosting so no shell, what do I do to get it back??
I've also just found this in the error log. Not sure what this means...
Every time I try and got to either the site itself or the ccm link I get this in the logs
Does that help? This is with the new concrete directory in place
Every time I try and got to either the site itself or the ccm link I get this in the logs
[13-Feb-2017 03:23:18 UTC] PHP Fatal error: require(): Failed opening required '/home/gpsit/public_html/updates/concrete5.7.5.13_remote_updater/concrete/dispatcher.php' (include_path='.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php') in /home/gpsit/public_html/concrete/bootstrap/configure.php on line 52 [13-Feb-2017 03:30:45 UTC] PHP Warning: require(/home/gpsit/public_html/updates/concrete5.7.5.13_remote_updater/concrete/dispatcher.php): failed to open stream: No such file or directory in /home/gpsit/public_html/concrete/bootstrap/configure.php on line 52 [13-Feb-2017 03:30:45 UTC] PHP Fatal error: require(): Failed opening required '/home/gpsit/public_html/updates/concrete5.7.5.13_remote_updater/concrete/dispatcher.php' (include_path='.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php') in /home/gpsit/public_html/concrete/bootstrap/configure.php on line 52 [13-Feb-2017 03:32:01 UTC] PHP Warning: require(/home/gpsit/public_html/updates/concrete5.7.5.13_remote_updater/concrete/dispatcher.php): failed to open stream: No such file or directory in /home/gpsit/public_html/concrete/bootstrap/configure.php on line 52 [13-Feb-2017 03:32:01 UTC] PHP Fatal error: require(): Failed opening required '/home/gpsit/public_html/updates/concrete5.7.5.13_remote_updater/concrete/dispatcher.php' (include_path='.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php') in /home/gpsit/public_html/concrete/bootstrap/configure.php on line 52
Does that help? This is with the new concrete directory in place
Incase this helps...
http://www.goldenplainsit.com.au/concrete/index.php/install... gets me to the installation page.
Peter.
http://www.goldenplainsit.com.au/concrete/index.php/install... gets me to the installation page.
Peter.
From the error message it looks like it is looking in the updates folder for the concrete folder?
Try adding the complete Concrete 5.7.5.13 folder in the updates folder and see if this helps..
Try adding the complete Concrete 5.7.5.13 folder in the updates folder and see if this helps..
Thanks for the input Weyboat. I've moved the unpacked concrete5.7.5.13 folder into public_html/updates and still get not found error when I try and go to the ccm folder.
If I now go towww.www.website.com.au/updates/concrete3.7.5.13... I get the installer.
I'm really not sure where this updated directory should go and what should go there.
The website root seems to be public_html on this install. It has the application, concrete and there directories there. My reading of the instructions is to call the concrete folder concrete.old and put the concrete3.5.7.5.13 folder in its place (under public_html) and rename it concrete.
The odd thing is that there is a concrete folder in this 3.5.7.13 one so that gives me public_html/concrete/concrete. I tried just putting the second level concrete folder in place of the concrete.old but still can't find anything.
Where exactly should this source tree go for the upgrade?
If I now go towww.www.website.com.au/updates/concrete3.7.5.13... I get the installer.
I'm really not sure where this updated directory should go and what should go there.
The website root seems to be public_html on this install. It has the application, concrete and there directories there. My reading of the instructions is to call the concrete folder concrete.old and put the concrete3.5.7.5.13 folder in its place (under public_html) and rename it concrete.
The odd thing is that there is a concrete folder in this 3.5.7.13 one so that gives me public_html/concrete/concrete. I tried just putting the second level concrete folder in place of the concrete.old but still can't find anything.
Where exactly should this source tree go for the upgrade?
See my latest message
Just so I understand the layout..
You have the existing concrete folder renamed to concrete.old?
You have placed the concrete5.7.5.13 in the root and renamed it concrete?
You have the existing concrete folder renamed to concrete.old?
You have placed the concrete5.7.5.13 in the root and renamed it concrete?
Getting no response from you now?
Sorry, was away from the computer. Yes that's correct. I've tried putting it in the root, I've tried putting just the concrete folder from within the concrete5.7.5.13 folder in the root, I've tried now putting concrete5.7.5.13 into the updates folder under root.
So it basically has at the moment.
I've tried putting the concrete from within concrete5.8.5.13 in place of concrete directly under public_html but no change.
So it basically has at the moment.
public_html
concrete.old
concrete <-- was named concrete5.8.5.13
concrete
updates
concrete5.8.5.13I've tried putting the concrete from within concrete5.8.5.13 in place of concrete directly under public_html but no change.
Lets see if we can get back to square one..
Remove the folders from the root/updates folder.
Delete any new concrete folders from the root.
Rename your concrete.old folder back to concrete.
See what that does
Remove the folders from the root/updates folder.
Delete any new concrete folders from the root.
Rename your concrete.old folder back to concrete.
See what that does
That just gives me a white page, which I think is from the failed web update.
Do you have backups?
Your folder structure should be
public_html application concrete packages updates
That's what I have. I'm just not sure where and what I should unpack from the zip file. The instructions on the web page seem to be pretty straight forward, but I'm now really not sure what should go where.
The zip, when unpacked has
or should the whole concrete5.7.9.13 replace concrete old (this is how I read the instructions on the update page)?
I've tried both, neither work though. sigh.
The zip, when unpacked has
concrete5.7.9.13 concrete <-- is this the one that should replace concrete.old? application updates ... ...
or should the whole concrete5.7.9.13 replace concrete old (this is how I read the instructions on the update page)?
I've tried both, neither work though. sigh.
If you private message me with login details to the server, I will take a look for you.
Done, thanks so much.
There you go..
I am just doing a little spring cleaning on the server, so give me 15 minutes..
Ok, you are amazing.. how the hell did you get that going so quickly??
Experience!
Do you still want to upgrade to 5.7.5.13?
Do you still want to upgrade to 5.7.5.13?
Yes, actually to 5.8 I guess if the server would handle it.. but certainly to 13
I would not do 8.1 if I was you.
Best wait a while for the bugs to get squashed..
I will get 5.7.5.13 ready for updating, standby..
Best wait a while for the bugs to get squashed..
I will get 5.7.5.13 ready for updating, standby..
Okay, thats updated to 5.7.5.13 for you.
Just change your passwords now on the server and your site login (to be on the safe side) and your good to go.
Weyboat
Just change your passwords now on the server and your site login (to be on the safe side) and your good to go.
Weyboat
Thankyou SO VERY MUCH. You are fantastic. Hopefully one day I'll understand what happened.
Your method of updating was wrong
The best way is to download the update and extract it into your updates folder and then run the update from the dashboard.
What you did (I think) was to extract the download into the root and rename it to concrete, when you navigated to that folder in your browser, you were effectively trying to install a new instance of concrete, from there it all went downhill as you know.
The best way is to download the update and extract it into your updates folder and then run the update from the dashboard.
What you did (I think) was to extract the download into the root and rename it to concrete, when you navigated to that folder in your browser, you were effectively trying to install a new instance of concrete, from there it all went downhill as you know.
What broke it originally was trying to run the update automatically from the updates menu in the dashboard. For some reason that just hung.
Anyway, thanks so very very much your a champ.
Anyway, thanks so very very much your a champ.
In the directory structure I can't see any ccm directory anywhere.