5.7.11 to 8.0 - uncaught PDOException
Permalink 1 user found helpful
Hi C5,
I attempted the upgade from 5.7.11 to 8.0 as follows;
1) downloaded 8.0 archive
2) deleted all content from the archive except the Concrete directory
3) uploaded to public_html/upgrades directory of my site
4) extracted the archive
5) went back to my site dashboard, checked for upgrade, installed upgrade
6) here is the entire error message:
An unexpected error occurred.
Uncaught PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'arvcon1_conc970.UserSignups' doesn't exist in /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:91 Stack trace: #0 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(91): PDOStatement->execute(NULL) #1 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(828): Doctrine\DBAL\Driver\PDOStatement->execute() #2 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php(712): Doctrine\DBAL\Connection->executeQuery('SELECT t0.uID A...', Array, Array) #3 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php(196): Doctrine\ORM\Persisters\Entity\BasicEntityPersister->load(Array, NULL, NULL, Array,
What to do???
Please advise.
I attempted the upgade from 5.7.11 to 8.0 as follows;
1) downloaded 8.0 archive
2) deleted all content from the archive except the Concrete directory
3) uploaded to public_html/upgrades directory of my site
4) extracted the archive
5) went back to my site dashboard, checked for upgrade, installed upgrade
6) here is the entire error message:
An unexpected error occurred.
Uncaught PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'arvcon1_conc970.UserSignups' doesn't exist in /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:91 Stack trace: #0 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(91): PDOStatement->execute(NULL) #1 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(828): Doctrine\DBAL\Driver\PDOStatement->execute() #2 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php(712): Doctrine\DBAL\Connection->executeQuery('SELECT t0.uID A...', Array, Array) #3 /home/arvcon1/public_html/updates/concrete5-8.0.2/concrete/vendor/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php(196): Doctrine\ORM\Persisters\Entity\BasicEntityPersister->load(Array, NULL, NULL, Array,
What to do???
Please advise.
HI
Thanks for getting back- since the start post earlier, i went back to 7.5.11 by deleting the pubic_html/updates/concrete5-8.0.2 directory and application/config/updates.php and noticed that 7.5.12 had been released, thinking that the errors (plural as I have had other issues in trying to get 8 installed) I had been seeing had been fixed. But alas to my chagrin the same PDOException came up (I didn't compare the errors word for word but at a glance it was the exact same error message). I am pleased to say that rolling back to stable version is easy.
There is also a caution notice before installing saying that I have over 100 overrides and that sometimes overrides interfere with updates. I checked the contents of the override files and they all theme design options / customizations. I am thinking of moving them and trying to update again, logic being that I can just put them back after the update (hopefully) is successful but am afraid that I will break my site...even with a back up it's time I really don't feel like wasting...
Any other insights? Any light you can shed is appreciated.
Thanks again.
Thanks for getting back- since the start post earlier, i went back to 7.5.11 by deleting the pubic_html/updates/concrete5-8.0.2 directory and application/config/updates.php and noticed that 7.5.12 had been released, thinking that the errors (plural as I have had other issues in trying to get 8 installed) I had been seeing had been fixed. But alas to my chagrin the same PDOException came up (I didn't compare the errors word for word but at a glance it was the exact same error message). I am pleased to say that rolling back to stable version is easy.
There is also a caution notice before installing saying that I have over 100 overrides and that sometimes overrides interfere with updates. I checked the contents of the override files and they all theme design options / customizations. I am thinking of moving them and trying to update again, logic being that I can just put them back after the update (hopefully) is successful but am afraid that I will break my site...even with a back up it's time I really don't feel like wasting...
Any other insights? Any light you can shed is appreciated.
Thanks again.
@MarcYBB
I believe I had the same overrides warning on a brand new 5.7.5.12 install, so I don't think moving them is recommended as a solution.
Do you have a lot of custom code in this site?
I believe I had the same overrides warning on a brand new 5.7.5.12 install, so I don't think moving them is recommended as a solution.
Do you have a lot of custom code in this site?
No custom code.
I packaged up my custom theme and installed it as a package, so it does not appear in the overrides list.
I also added some customs blocks to my package for the same reason.
This removed a lot of the entities in the overrides list.
Is it now normal practice to strip down an upgrade to just the concrete folder before adding it to the updates folder?
I would have thought that would cause it to fail?
I also added some customs blocks to my package for the same reason.
This removed a lot of the entities in the overrides list.
Is it now normal practice to strip down an upgrade to just the concrete folder before adding it to the updates folder?
I would have thought that would cause it to fail?
Stripping down the /concrete directory and placing it in the updates folder worked for all upgrades from 5.7 to 5.7.12 and nothing I can see anywhere in the 8.0 documentation / forums indicates to do otherwise.
I have only done that when renaming the original concrete folder to concrete_old and then placing the new concrete folder in the ROOT before manually running the upgrade script..
And only then, after I have thoroughly tested the update by putting the update package in the updates folder and installing via the system & settings section.
This is the first time I have heard of doing it the way you have..
That was I why asked the question if this was now a normal practice?
And only then, after I have thoroughly tested the update by putting the update package in the updates folder and installing via the system & settings section.
This is the first time I have heard of doing it the way you have..
That was I why asked the question if this was now a normal practice?
I am referring to the manual dashboard update method and you are referring to replacing the concrete directory method - both methods are described here:
http://documentation.concrete5.org/developers/installation/upgradin...
So to answer your question yes it is normal practice depending on the update method.
http://documentation.concrete5.org/developers/installation/upgradin...
So to answer your question yes it is normal practice depending on the update method.
Thanks for that info @MarcYYB, that's something else I have learned..
I'm experiencing the same problem, getting the same error.
Tried to update from version 7.5.12 to version 8.0.2 by replacing the concrete directory and running .../index.php/ccm/system/upgrade.
Trying to switch back to version 7.5.12 breaks the site completely. The error is:
Class \Concrete\Core\Permission\Key\CategoryTreeNodeKey does not exist
Tried to update from version 7.5.12 to version 8.0.2 by replacing the concrete directory and running .../index.php/ccm/system/upgrade.
Trying to switch back to version 7.5.12 breaks the site completely. The error is:
Class \Concrete\Core\Permission\Key\CategoryTreeNodeKey does not exist
Trying to upgrade again, without running ".../index.php/ccm/system/upgrade" resulted in a success.
I have no clue why...
I have no clue why...
http://documentation.concrete5.org/developers/installation/upgrading-concrete5
"If you want to minimize disk space usage and don't need to use the web interface for update Concrete5, you can replace the original concrete directory with a new version, and then upgrade through a particular route.
-> Download the latest core fromhttp://www.concrete5.org/download...
-> Unzip the file.
-> Replace the concrete directory in the web root with the concrete directory you downloaded.
-> Visit your site in a browser.
That's it! concrete5 version 8 and above will automatically run any database migrations that need to be run to bring the site up to date."
As described in the article, the update script is no longer necessary for version 8, but for me it's still not clear, if that affects also updating from 7.5.12 to version 8.
"If you want to minimize disk space usage and don't need to use the web interface for update Concrete5, you can replace the original concrete directory with a new version, and then upgrade through a particular route.
-> Download the latest core fromhttp://www.concrete5.org/download...
-> Unzip the file.
-> Replace the concrete directory in the web root with the concrete directory you downloaded.
-> Visit your site in a browser.
That's it! concrete5 version 8 and above will automatically run any database migrations that need to be run to bring the site up to date."
As described in the article, the update script is no longer necessary for version 8, but for me it's still not clear, if that affects also updating from 7.5.12 to version 8.
I have the same question, I think the documentation is a bit unclear here, it says:
"Replacing the original concrete Directory (Version 8 and above)"
Does this mean: This method only works to upgrade an already installed v8.x or does it also work for an upgrade from the latest 5.7 version to a current 8.x version?
Thanks!
"Replacing the original concrete Directory (Version 8 and above)"
Does this mean: This method only works to upgrade an already installed v8.x or does it also work for an upgrade from the latest 5.7 version to a current 8.x version?
Thanks!
I would try updating to the latest 5.7.5.12 and then to 8.0.2.