Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic Upgrades #5260

Closed
dleigh opened this issue Jun 3, 2020 · 5 comments
Closed

Automatic Upgrades #5260

dleigh opened this issue Jun 3, 2020 · 5 comments

Comments

@dleigh
Copy link

dleigh commented Jun 3, 2020

Hi, I'm using 4.0.2 and I had modified a handful of files waiting for certain features to show up. Consequently the hash checks on those files fail, of course. I'd like to update to 4.0.4 but I don't see the automatic update task. Is that BECAUSE of the files failing the integrity check? If so, can I bypass that to access the automatic update? Thanks!

@MrClever
Copy link
Collaborator

MrClever commented Jun 4, 2020

Failed integrity checks won't prevent the automatic update from occurring, but it will mean your modified files are replaced with the released version after the upgrade. If you want to keep your changes, please back them up before upgrading.

Having said that, occasionally the automatic update process doesn't get triggered (I've seen it twice on my production system and never been able to determine why). In those cases, simply download the release file and unzip it. Then copy all the files over the top of the existing setup and log back in. ALWAYS create a backup before running a manual upgrade. We have some more detailed documentation on the process in the wiki: https://github.com/ChurchCRM/CRM/wiki/Upgrade

@MrClever
Copy link
Collaborator

@dleigh - is this still a problem? If so, what steps have you executed so far? Are there any errors/warnings etc in Apache's logs (error.log and/or access.log) and also the ChurchCRM application logs - /path/to/churchcrm/logs/*.log?

If this isn't a problem any more, please let us know so we can close this ticket out.

@dleigh
Copy link
Author

dleigh commented Jul 20, 2020

Thanks for the reminder. I just did the update as you suggested and it seemed to work fine except that 6 files end up with hashes that don't match:

api/routes/people/people-family.php
ChurchCRM/utils/GeoUtils.php
vendor/composer/autoload_classmap.php
vendor/composer/autoload_psr4.php
vendor/composer/autoload_static.php
vendor/ocramius/package-versions/src/PackageVersions/Versions.php

I redid the unzip a 2nd time to see if that changed anything but it did not. I then did another WGET for the file and a 3rd unzip but still no change. Also those files all have the June 18th timestamp and are not the files that I modified in the 4.0.2 release. So I don't know if that's a problem or not.

@MrClever
Copy link
Collaborator

MrClever commented Jul 20, 2020

You could always just delete them and replace them with the respective versions from the release zip...to be "sure". Not sure why you're getting a warning about integrity checks for unmodified files from the zip though - that's weird. Also, the 4.1.0 release has come out since this ticket was opened and I know it closes a number of bugs so that might be worth a shot too. Having said that, there are some known calendar bugs in 4.1.0 but there's a fix (#5292) for that coming soon in 4.1.1; if you rely heavily on the calendar features, maybe wait for the 4.1.1+ release.

Given the original problem (failed upgrade) sounds like it is resolved, are you comfortable if we close this one out?

@dleigh
Copy link
Author

dleigh commented Jul 21, 2020

I was probably not clear but I jumped straight to 4.1.0 - so that's the version I'm talking about. I tried unzipping the file to another, new directory and then copied one of the files in question from the newly unzipped directory over the directory structure on the live system but it didn't change anything.

I'm fine with closing this. I'll open a different one if I have the problem again.

@dleigh dleigh closed this as completed Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants