-
Notifications
You must be signed in to change notification settings - Fork 455
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
Upgrading via the UI on live host fails with 'slim application error' #2337
Comments
is this still an issue |
might be the same issue as #1797 |
I can't see how it would be a timeout issue like #1797 seems to imply. The error dialog is almost instantaneous. Also, I don't know if it's an issue after 2.6.3 - I downgraded back when 2.7.0 broke the family dashboard ( #2336 ). But it's certainly there on 2.6.3 (just tried the auto upgrade now, to 2.7.2). |
Sadly, this is still an issue, at least when trying to upgrade from 2.7.3 to 2.7.5. Exact same sequence of events, and screenshot above still applies. |
Updates: Now that the logging location issue has been fixed (before a recent update, I wasn't seeing any logs in /logs), I've been able to see the php error log, and on the most recent failure, I've got some useful data. The ZipArchive class isn't found. Now that I know that, I was able to reconfigure my shared hosting's PHP module list and include the zip module. That's fixed it for me. Woohoo! For future info, here's the log trace that helped me.
|
I have yet to be able to upgrade our hosted instance of ChurchCRM, since starting with 2.4.4. Most recent attempt was from 2.5.2 to 2.7.0. Each time, the Upgrade Process proceeds as expected from 'make and retrieve backup', through 'retrieve upgrade files':
but fails immediately on Apply update with a not-particularly-helpful dialog:
In every case, I have to manually upgrade by unzipping the new version into a fresh directory, move Config.php (and any images or custom files), and fixing permissions.
The hosted instance is set up as a subdomain (e.g., churchcrm.mydomain.tld), with the code in a directory (e.g., churchcrm, permissions = 755) within my public_html folder. Some potentially relevant settings from Config.php:
The text was updated successfully, but these errors were encountered: