Many, Many, Many Errors!
Permalink
I upgraded to C5 8.2.1 and my site no longer worked. I upgraded to PHP 7.0 (options are 5.6, 7.0, or 7.1) and got errors about finfo. Edited phprc and the finfo error went away but a whole bunch of new errors cropped up. Half of the plugins don't work. If I try to edit a page all the menu controls disappear. I am at a loss. I have never been able to do anything with Concrete5 because there is always something wrong.
Currently I have the site set to show full debugging details.
Can someone take a look and help me out?
Go here:
http://cassiecarter.com/Concrete5/index.php...
Then click on "Artwork" in the main menu.
There are all sorts of other errors on other pages, but they require login. It would be swell if I could find a way to change permissions on individual pages but I am just about done trying to figure this mess out!
Thanks,
Cassie
Currently I have the site set to show full debugging details.
Can someone take a look and help me out?
Go here:
http://cassiecarter.com/Concrete5/index.php...
Then click on "Artwork" in the main menu.
There are all sorts of other errors on other pages, but they require login. It would be swell if I could find a way to change permissions on individual pages but I am just about done trying to figure this mess out!
Thanks,
Cassie
What version did you upgrade from? It looks like the database migrations didn't get done. I would suggest you login then go tohttp://cassiecarter.com/Concrete5/index.php/ccm/system/upgrade... and click "Click here if you would like to re-run this script."
Thanks for your reply! I did what you suggested and there's no change. Still getting the same errors.
I upgraded C5 7.5.13 in March of this year, then upgraded to 8.2.1 yesterday.
What method did you use to upgrade? Did you replace your /concrete directory in place, or did you do it through the dashboard? When you re-ran that script did the whole thing finish or were there errors?
Hmmm . . . let me see if I can remember.
First I ran the update from the dashboard. From there it showed me there were two add-ons that needed to be updated, so I ran the update and it seemed like it didn't work. Also I started to see errors. So . . .
I downloaded the update, unzipped it, and replaced the old "concrete" directory with the new one via FTP. Then I went back and successfully ran the add-on updates in the dashboard.
After that I started getting finfo errors, so I went to my ISP and upgraded PHP. I still had errors so I modified phprc, which fixed the finfo errors but then I had a whole bunch of OTHER, new errors.
Does that help? Unfortunately the "reply" overlay covers your response so I can't check to see if I answered all your questions . . .
UPDATE: when I reran the script, it completed with no errors.
First I ran the update from the dashboard. From there it showed me there were two add-ons that needed to be updated, so I ran the update and it seemed like it didn't work. Also I started to see errors. So . . .
I downloaded the update, unzipped it, and replaced the old "concrete" directory with the new one via FTP. Then I went back and successfully ran the add-on updates in the dashboard.
After that I started getting finfo errors, so I went to my ISP and upgraded PHP. I still had errors so I modified phprc, which fixed the finfo errors but then I had a whole bunch of OTHER, new errors.
Does that help? Unfortunately the "reply" overlay covers your response so I can't check to see if I answered all your questions . . .
UPDATE: when I reran the script, it completed with no errors.
Hmm.. When you went to that link what version did it say was current on the website? I feel like your site might be running on a different version than we think. If you had tried to do the upgrade through the dashboard it might be looking in the updates directory instead of the root concrete directory. What happens if you change your updates directory to updates_backup and then add a new (empty) updates directory? This might break your site even more - just to warn you.
It says 8.2.1.
I'll try what you suggested and report back.
I'll try what you suggested and report back.
OK, I renamed updates to updates BACKUP then created an empty updates directory.
I went back and reran the script. I got this error:
Invalid "update.core" defined. Please remove it from /home/cassiecarter/cassiecarter.com/Current/Concrete5/application/config/update.php.
Putting back the old updates folder ...
I went back and reran the script. I got this error:
Invalid "update.core" defined. Please remove it from /home/cassiecarter/cassiecarter.com/Current/Concrete5/application/config/update.php.
Putting back the old updates folder ...
Now it doesn't work at all . . .
For some reason everything disappeared out of the original updates folder ...
For some reason everything disappeared out of the original updates folder ...
Does the site come back up if you remove the /application/config/update.php? Just rename it - don't delete it. Then once you've done that try running that script again.
I removed the content of application/config/update.php and got the site back.
When I went back to the "rerun script," I got an interesting result:
Upgrading from 8.2.1
Upgrading to 8.1.0
Your current website uses a version of concrete5 greater than this one. You cannot upgrade.
When I went back to the "rerun script," I got an interesting result:
Upgrading from 8.2.1
Upgrading to 8.1.0
Your current website uses a version of concrete5 greater than this one. You cannot upgrade.
Now I'm getting errors on the home page, too.
Now that makes sense! Try downloading the 8.2.1 zip file, then rename the current concrete directory to concrete_8.1.0 and put the unzipped one into the root as just concrete and run the upgrade script again.
If it works you can delete the 8.1.0 one off the server so it isn't there taking up space.
If it works you can delete the 8.1.0 one off the server so it isn't there taking up space.
OK, it's in progress. It will take a while to upload. Not sure why my FTP connection is so darned slow.
I feel like you need to change (or delete) the version_installed from the /application/config/generated_overrides/concrete.php too, but I'm not 100% on that, if the upgrade doesn't fix it try doing that, if you want to change it put it to 8.1.0.
OK I'm more or less back to where I was but errors are appearing only on some pages.
I am starting to think the problem is Easy Image Gallery.
Unfortunately, once a page has Easy Image Gallery on it, there is no way to edit it and therefore no way to remove Easy Image Gallery from the page.
I am starting to think the problem is Easy Image Gallery.
Unfortunately, once a page has Easy Image Gallery on it, there is no way to edit it and therefore no way to remove Easy Image Gallery from the page.
I believe to remember that I ran into a similar problem.
I had a site running using a free add-On (some gallery/slideshow thing) which was not v.8 ready and broke every page i had it on.
What I did was downgrading to a version before v8, removing the add-on and performing the upgrade to 8.2.1 and then I replaced the add-on with something else.
Some of the free Add-Ons are not v.8 ready yet.
I had a site running using a free add-On (some gallery/slideshow thing) which was not v.8 ready and broke every page i had it on.
What I did was downgrading to a version before v8, removing the add-on and performing the upgrade to 8.2.1 and then I replaced the add-on with something else.
Some of the free Add-Ons are not v.8 ready yet.
If you think it's that block, you can just comment out the stuff in the controller.php for the view function and see if the page comes up. If you want I could try to help you out with that but you would need to PM me FTP info
I discovered that if you go to the Dashboard (if you can get to it, which you can't in many cases with the errors I'm experiencing), then go to Extend Concrete5 then click on the Details button for the add-on that is causing problems, then under Block Types click on the link with the add-on's name, you eventually end up on a screen you might get to more easily by starting in Stacks & Blocks > Block Types. Anyway, THERE you can delete all instances of the problem add-on.
This solution seems to fix MOST of the problems I've been having.
This solution seems to fix MOST of the problems I've been having.
