upgrading from churchinfo #3420
Comments
|
What version of churchinfo |
|
1.2.14
…On 11/23/2017 8:10 PM, George Dawoud wrote:
What version of churchinfo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t4LNk-C5HiQBCW8HVHulLWhUDRKXks5s5iWPgaJpZM4QpTEu>.
|
|
If you can revert the dB back I can help you with the steps We have not tested it in a while but you should be able to run the following scripts in order and tell me which one breaks https://github.com/ChurchCRM/CRM/tree/master/src/mysql/upgrade |
|
Don’t run 2.9.0 yet |
|
OK, I used a mysql dump to obtain the database from my 1.2.14 installation.
I started with a fresh install of ChurchCRM and an empty database. I let logged in and went straight to the Restore from Backup option.
I uploaded the database to restore, and that's when I got the message.
I started with a clean dB and restored 2.0.0.sql, but that failed. I got the following (where I've replaced my directory tree with DIRECTORY):
Error making API Call to: /api/database/restore
Error text: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' query('...')", "#1 DIRECTORY/vendor/propel/propel/src/Propel/Runtime/Connection/StatementWrapper.php(85): Propel\\Runtime\\Connection\\PdoConnection->query('...')", "#2 [internal function]: Propel\\Runtime\\Connection\\StatementWrapper->query()", "#3 DIRECTORY/vendor/propel/propel/src/Propel/Runtime/Connection/ConnectionWrapper.php(434): call_user_func_array(Array, Array)", "#4 DIRECTORY/ChurchCRM/SQLUtils.php(142): Propel\\Runtime\\Connection\\ConnectionWrapper->query('...')", "#5 DIRECTORY/ChurchCRM/SQLUtils.php(52): ChurchCRM\\SQLUtils::query('...', Object(Propel\\Runtime\\Connection\\DebugPDO))", "#6 DIRECTORY/ChurchCRM/Service/SystemService.php(88): ChurchCRM\\SQLUtils::sqlImport(Resource id #15, Object(Propel\\Runtime\\Connection\\DebugPDO))", "#7
DIRECTORY/api/routes/database.php(28): ChurchCRM\\Service\\SystemService->restoreDatabaseFromBackup(Array)", "#8 [internal function]: Closure->{closure}(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response), Array)", "#9 DIRECTORY/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(41): call_user_func(Object(Closure), Object(Slim\\Http\\Request), Object(Slim\\Http\\Response), Array)", "#10 DIRECTORY/vendor/slim/slim/Slim/Route.php(325): Slim\\Handlers\\Strategies\\RequestResponse->__invoke(Object(Closure), Object(Slim\\Http\\Request), Object(Slim\\Http\\Response), Array)", "#11 DIRECTORY/vendor/slim/slim/Slim/MiddlewareAwareTrait.php(116): Slim\\Route->__invoke(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))", "#12 DIRECTORY/vendor/slim/slim/Slim/Route.php(297): Slim\\Route->callMiddlewareStack(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))", "#13 DIRECTORY/vendor/slim/slim/Slim/App.php(443): Slim\\Route->run(Object(Slim\\Http\\Request),
Object(Slim\\Http\\Response))", "#14 DIRECTORY/vendor/slim/slim/Slim/MiddlewareAwareTrait.php(116): Slim\\App->__invoke(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))", "#15 DIRECTORY/vendor/slim/slim/Slim/App.php(337): Slim\\App->callMiddlewareStack(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))", "#16 DIRECTORY/vendor/slim/slim/Slim/App.php(298): Slim\\App->process(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))", "#17 DIRECTORY/api/index.php(70): Slim\\App->run()", "#18 {main}" ]
…On 11/23/2017 8:52 PM, George Dawoud wrote:
If you can revert the dB back I can help you with the steps
We have not tested it in a while but you should be able to run the following scripts in order and tell me which one breaks
https://github.com/ChurchCRM/CRM/tree/master/src/mysql/upgrade
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t8cof96HfG716isnBWbynL59hAasks5s5i-CgaJpZM4QpTEu>.
|
|
Install a fresh copy of church crm and use the top right corner bug button and file a bug so that we can see you system setup |
|
I realized I didn't download the .sql files properly, so I did that and tried restoring from 2.0.0.sql. Still failed, but this is what I got this time, which looks pretty similar to the errors I'm getting on my own sql file:
Error making API Call to: /api/database/restore
Error text: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'cfg_type' in 'field list'
Stack Trace:
[
"#0 DIRECTORY/vendor/propel/propel/src/Propel/Runtime/Connection/PdoConnection.php(109): PDO->query('INSERT INTO con...')",
"#1 DIRECTORY/vendor/propel/propel/src/Propel/Runtime/Connection/StatementWrapper.php(85): Propel\\Runtime\\Connection\\PdoConnection->query('INSERT INTO con...')",
"#2 [internal function]: Propel\\Runtime\\Connection\\StatementWrapper->query()",
"#3 DIRECTORY/vendor/propel/propel/src/Propel/Runtime/Connection/ConnectionWrapper.php(434): call_user_func_array(Array, Array)",
"#4 DIRECTORY/ChurchCRM/SQLUtils.php(142): Propel\\Runtime\\Connection\\ConnectionWrapper->query('INSERT INTO con...')",
"#5 DIRECTORY/ChurchCRM/SQLUtils.php(52): ChurchCRM\\SQLUtils::query('INSERT INTO con...', Object(Propel\\Runtime\\Connection\\DebugPDO))",
"#6 DIRECTORY/ChurchCRM/Service/SystemService.php(88): ChurchCRM\\SQLUtils::sqlImport(Resource id #15, Object(Propel\\Runtime\\Connection\\DebugPDO))",
"#7 DIRECTORY/api/routes/database.php(28): ChurchCRM\\Service\\SystemService->restoreDatabaseFromBackup(Array)",
"#8 [internal function]: Closure->{closure}(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response), Array)",
"#9 DIRECTORY/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(41): call_user_func(Object(Closure), Object(Slim\\Http\\Request), Object(Slim\\Http\\Response), Array)",
"#10 DIRECTORY/vendor/slim/slim/Slim/Route.php(325): Slim\\Handlers\\Strategies\\RequestResponse->__invoke(Object(Closure), Object(Slim\\Http\\Request), Object(Slim\\Http\\Response), Array)",
"#11 DIRECTORY/vendor/slim/slim/Slim/MiddlewareAwareTrait.php(116): Slim\\Route->__invoke(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))",
"#12 DIRECTORY/vendor/slim/slim/Slim/Route.php(297): Slim\\Route->callMiddlewareStack(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))",
"#13 DIRECTORY/vendor/slim/slim/Slim/App.php(443): Slim\\Route->run(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))",
"#14 DIRECTORY/vendor/slim/slim/Slim/MiddlewareAwareTrait.php(116): Slim\\App->__invoke(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))",
"#15 DIRECTORY/vendor/slim/slim/Slim/App.php(337): Slim\\App->callMiddlewareStack(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))",
"#16 DIRECTORY/vendor/slim/slim/Slim/App.php(298): Slim\\App->process(Object(Slim\\Http\\Request), Object(Slim\\Http\\Response))",
"#17 DIRECTORY/api/index.php(70): Slim\\App->run()",
"#18 {main}"
]
|
|
give me a few days as I need to build a new DB install ChurchInfo and test and fix the upgrade as needed... but we will get you upgraded so fear not. |
|
Thank you! I noticed that there were a few stones I haven't turned over yet, so in the meantime I'll do that and let you know if anything changes.
…On 11/24/2017 2:11 PM, George Dawoud wrote:
give me a few days as I need to build a new DB install ChurchInfo and test and fix the upgrade as needed... but we will get you upgraded so fear not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t8wQKsbgS9eXmRuiV7waVh2refUWks5s5yLggaJpZM4QpTEu>.
|
|
https://github.com/ChurchCRM/CRM-QA should give you a quick way to spin up 1.2 |
|
is this your #3431 |
|
I am working on a fix for you now. Going from 1.2.14 to 2.8.x |
|
ok found the issue it is in 2.7.0 upgrade code... looking for the fix now |
|
@sjreeves I have a fix, I can't get auto upgrade to work 100% can you test it manually please
run the following upgrade scripts one by one (https://github.com/ChurchCRM/CRM/tree/master/src/mysql/upgrade)
|
|
using #3443 to track auto DB upgrade issue |
|
Ok, I was able to get the issue fixed to auto upgrade. After merging #3443 we should have a 2.9.0 RC build is ready |
|
Does that mean it's ready now to try? If so, I'm not sure how to get the 2.9.0 RC build. I don't know my way around github that well.
Stan
…On 11/25/2017 4:38 PM, George Dawoud wrote:
Ok, I was able to get the issue fixed to auto upgrade. After merging #3443 <#3443> we should have a 2.9.0 RC build is ready
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t-XEgODNuZGZlYvPiAO7vT4tIp1bks5s6JbVgaJpZM4QpTEu>.
|
|
Get it from http://demo.churchcrm.io/ |
|
I am finally back to trying to do this upgrade. I have restored my old database, and it says it needs to upgrade the database. Then I get the following:
SQLSTATE[HY000]: General error: 1347 '<database>.email_count' is not BASE TABLE
This could be an issue with the original database, as there seemed to be something inconsistent in the state of my 2.8.14 table.
|
|
I created a brand new 2.8.14 installation and got the same error when I created a new 2.10.4 ChurchCRM installation and then restored the pristine 2.8.14 database to it. So it doesn't appear to be my database.
…On 3/1/2018 8:00 PM, Stan Reeves wrote:
I am finally back to trying to do this upgrade. I have restored my old database, and it says it needs to upgrade the database. Then I get the following:
SQLSTATE[HY000]: General error: 1347 '<database>.email_count' is not BASE TABLE
This could be an issue with the original database, as there seemed to be something inconsistent in the state of my 2.8.14 table.
|
|
Make sure your dB user has full admin power over the dB. The error is due to a missing View |
|
I'm using the root user.
…On 3/1/2018 9:18 PM, George Dawoud wrote:
Make sure your dB user has full admin power over the dB. The error is due to a missing View
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t3YzBkDAGJHP5fWVZeWZCkRimItBks5taLoMgaJpZM4QpTEu>.
|
|
I double-checked. I'm using the root user, and it has all privileges on the database.
…On 3/1/2018 9:18 PM, George Dawoud wrote:
Make sure your dB user has full admin power over the dB. The error is due to a missing View
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t3YzBkDAGJHP5fWVZeWZCkRimItBks5taLoMgaJpZM4QpTEu>.
|
|
Do you have any suggestions? Is there a way to upgrade the database outside the web interface? I'm dead in the water as it is. |
|
I'm spinning up a 1.2.14 VM now to test this. |
ghost
assigned
|
@sjreeves If you're comfortable trying new code before release - take a look at the changes in PR #4085. I wouldn't recommend an unreleased branch for "production use," but we are close to 3.0.0 and it will be part of that relese It should solve the issues you're having. Please let me know if it does allow you to run the upgrade. P.S. - you should also now be able to use the GUI "restore" method with your 1.2.14 database. |
|
Thanks for looking into this. I'm not sure how to get the new code and incorporate it into my installation. Do I hit "View" and then download all the updated files and replace them? Or is there a better way?
|
|
@sjreeves there's a few ways to help with testing changes to the system: Best:
Option 2: Option 3: Option 4: |
|
@sjreeves #4085 was just merged. There will be a ZIP file with the full "pre-release" build on the demo site in about 15 minutes (or whenever the tests pass and automated builds complete). You can check there for the zip file. Again - this is not meant for production use, so best to wait for full 3.0.0 before fully committing to running it ;) |
|
OK, I'm trying to drill back down to this tomorrow morning. It's unclear how or whether I can use the modifications you've made to install a copy of 2.10.4 and then import my 1.2.14 database. Is the only option to wait for the 3.0.0 release? Any projection on when that might happen?
I can test the import on the 3.0.0 pre-release but am not sure if that's going to help with my immediate problem.
|
|
I went ahead and used the latest package on github. After attempting to restore the database, I got the very informative message: "Restore Status: Restore Error." Any suggestions?
…On 3/7/2018 10:07 AM, Charles wrote:
Try this - http://demo.churchcrm.io/builds/master/ChurchCRM-3.0.0-98960fc.zip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t5GGWqQ3e7iNUG1-xsN6WYMQVPY8ks5tcAXegaJpZM4QpTEu>.
|
|
lol, it is informative ;) try looking into the /logs dir for -php.log or -app.log for more info |
|
Ah, that helps!
I get a large number of these:
Column not found: 1054 Unknown column 'events_event.location_id' in 'field list'
Looking at the various versions of ChurchInfo, I can't see that this is ever defined. So maybe ChurchCRM is expecting a column in the import that ChurchCRM uses but hasn't been introduced in ChurchInfo?
|
|
@crossan007 you worked on events... do you recall where this was added |
|
The column should have been added with 112d47d#diff-3ca2a2f49ad4ea70a36f43e59d1451c1R2 |
|
I used http://demo.churchcrm.io/builds/master/ChurchCRM-3.0.0-4848834.zip
Just double-checked.
Edit:
commit: 4848834
|
|
ok 3.0.0 Release is going on today please download once it is released and let us know if you are still having the same issue, you will need to rollback to churchinfo backup and then apply the upgrade |
|
Got it working! Thanks!
…On 3/15/2018 3:44 PM, George Dawoud wrote:
ok 3.0.0 Release is going on today please download once it is released and let us know if you are still having the same issue, you will need to rollback to churchinfo backup and then apply the upgrade
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#3420 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgX3t5fLlOLpTtGiZ8sedtBV1iLDwTDlks5tetLHgaJpZM4QpTEu>.
|
I am trying to upgrade from churchinfo. I have tried every possible way, and I'm getting database errors no matter what. If I restore the database from backup, I get
Error text: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'icon' in 'field list'
If I try to ignore this error and proceed (for example, going to View All Persons), I get
There was an error upgrading your ChurchCRM database:
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'grp_active'
I have spent an inordinate amount of time setting up the server and getting this ready to go, so I sure hope this isn't a dead end. Any help will be greatly appreciated.
The text was updated successfully, but these errors were encountered: