So I upgraded Concrete to 5.6.0.2 and it ruined my site
Permalink
Not completely, and I've been franticly working on a fix but I could use some help since I know very little about Concrete.
Anyways I deleted the last line of site.com/config/site.php so it wouldn't use the site.com/update/concrete5.blah.blah folder so I could manually replace and edit the site.com/concrete folder and see the changes.
So here's as far as I got. I've been replacing the site.com/concrete folder with 2 of the updates, 5.4.2.2 & 5.6.0.2
With the 5.4.2.2 the entire site works except for viewing your shopping cart in the shop.
And the dashboard, I can't add products or do anything ecommerce related.
With the 5.6.0.2 the entire site is broken, only shows a menu, but in the shop the cart works.
As for the dashboard, everything works perfectly.
I'm not really sure where to go from here. I've been mixing 5.4.2.2's files and 5.6.0.2's files to try to get a good match where the cart link would work and I can add products.
Anyways I deleted the last line of site.com/config/site.php so it wouldn't use the site.com/update/concrete5.blah.blah folder so I could manually replace and edit the site.com/concrete folder and see the changes.
So here's as far as I got. I've been replacing the site.com/concrete folder with 2 of the updates, 5.4.2.2 & 5.6.0.2
With the 5.4.2.2 the entire site works except for viewing your shopping cart in the shop.
And the dashboard, I can't add products or do anything ecommerce related.
With the 5.6.0.2 the entire site is broken, only shows a menu, but in the shop the cart works.
As for the dashboard, everything works perfectly.
I'm not really sure where to go from here. I've been mixing 5.4.2.2's files and 5.6.0.2's files to try to get a good match where the cart link would work and I can add products.
Upgrading note: You need to be running version 5.4.2.2 to upgrade to 5.5.0.
Upgrading note: You need to be running version 5.5.2.1 to upgrade to 5.6.0.
For more information on how concrete5 version numbers work and what they denote, please read our Version Numbering Guide.
http://www.concrete5.org/documentation/general-topics/version-numbe...
Upgrading note: You need to be running version 5.5.2.1 to upgrade to 5.6.0.
For more information on how concrete5 version numbers work and what they denote, please read our Version Numbering Guide.
http://www.concrete5.org/documentation/general-topics/version-numbe...
Hmm, good catch.. I missed that :) I always upgrade via the C5 interface myself.
Yeah I've got no backup to go to. So that sucks. Lol. So is there anyways to downgrade then update the right way?
If you replaced files I guess you could try placing back the files for the old version you had used. :) But.. make a backup first either way!
So I replaced my old 5.4.0.5, which is my current version, then I upgraded to 5.6.0.2 which didn't work and everything got messed up. So when I go to my website it shows me
Fatal error: Call to undefined method ProductBlockController::addFooterItem() in /home/ifccgkmh/public_html/packages/core_commerce/blocks/product/controller.php on line 51
and to my shop it shows me
Fatal error: Call to undefined method ProductListBlockController::addFooterItem() in /home/ifccgkmh/public_html/packages/core_commerce/blocks/product_list/controller.php on line 22
I don't know if when I upgraded it changed those controller.php files.
Fatal error: Call to undefined method ProductBlockController::addFooterItem() in /home/ifccgkmh/public_html/packages/core_commerce/blocks/product/controller.php on line 51
and to my shop it shows me
Fatal error: Call to undefined method ProductListBlockController::addFooterItem() in /home/ifccgkmh/public_html/packages/core_commerce/blocks/product_list/controller.php on line 22
I don't know if when I upgraded it changed those controller.php files.
Not sure what to tell you, I would have made a backup myself.. Because I know if I am not the one to mess up, the software will. :)
How did you upgrade?
Do you use the right update procedure?
Do you use the right update procedure?
I used the online update, the one that when you log into your dashboard it tells you to upgrade. Everything seemed to go fine, then I viewed the website and it gave me the JSON.php error which I fixed by moving the json.php file to the models directory. Then it gave me the controller.php error I listed above. That's pretty much the only thing wrong with the site, when I remove that file (controller.php) the site works perfectly, it just wont list any of my products for sale.
Hey idk if this will work, but can some of you send me your versions of your controller.php files?
public_html/packages/core_commerce/blocks/product/controller.php
&&
public_html/packages/core_commerce/blocks/product_list/controller.php
public_html/packages/core_commerce/blocks/product/controller.php
&&
public_html/packages/core_commerce/blocks/product_list/controller.php
I was also wondering if I could just reinstall concrete and just keep my site data?
No, a reinstall requires an empty database.
What if I were to move all my data off the servers then reinstall concrete, would I be able to plug my website back in
There are 2 ways you could do that:
1. Take a database and /files folder backup, then import both to the new c5 install. This requires a functioning site to make the backup format the same version. It may well backup your problems and re-import them to the new site.
2. Create a starting point xml from the old site and import it to the new site. This also obviously requires a functioning site to start from, but may not be as picky about versions and may loose some auxiliary information.
So performing either requires a working site to make a backup or export a starting point from! And some expertise.
A third manual method also requires a working site (at least partially, but you may also be able to get some of it from one of the web archive/history servers or even from Google as an html impression).
3. Start a new site, and copy/paste content from the existing site.
1. Take a database and /files folder backup, then import both to the new c5 install. This requires a functioning site to make the backup format the same version. It may well backup your problems and re-import them to the new site.
2. Create a starting point xml from the old site and import it to the new site. This also obviously requires a functioning site to start from, but may not be as picky about versions and may loose some auxiliary information.
So performing either requires a working site to make a backup or export a starting point from! And some expertise.
A third manual method also requires a working site (at least partially, but you may also be able to get some of it from one of the web archive/history servers or even from Google as an html impression).
3. Start a new site, and copy/paste content from the existing site.
I think I might just go with the 3rd option, I can't get into my dashboard settings but I can get into the file manager for my images, and edit pages to rebuild.
So basically (correct me if I'm wrong) I'm going to need to backup the entire site to a place that isn't public_html, then make a new database (keeping the old one intact) install concrete5, take the backed up website and put it into a folder like site.com/oldsitebackup/ and access it using index.php. Then cross reference it to build the new site.
So basically (correct me if I'm wrong) I'm going to need to backup the entire site to a place that isn't public_html, then make a new database (keeping the old one intact) install concrete5, take the backed up website and put it into a folder like site.com/oldsitebackup/ and access it using index.php. Then cross reference it to build the new site.
So making the backup folder isn't working, is it possible to install concrete to a specific folder like site.com/newsite to build and test it in? With separate databases and all that. Then after it's complete would I be able to move it to the regular .com (public_html) directory and have it take over?
For method 3, no, what you are doing there is to hope that third party web archive locations have a copy of your site or at least many of the pages before it went bad and that you can cut and paste from those pages. Method 3 really is a last resort. If you can revert your site to something that sort of works, anything between 1 & 2 is better.
But at any rate you want to make a backup before doing so.
Have you got one you can go back to for now?
Or is the live site now broken?
I think the best way to debug is by starting to post a screenshot of what you're seeing so we can give some pointers.
Cheers,
Phantium