-
Notifications
You must be signed in to change notification settings - Fork 445
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
Upgrade on production site failed #1523
Comments
you get this when you login with a person who does not have admin perms |
@gyphon this is likely the issue addressed in #1511, where the upgrade succeeds, but displays the failure message. Can you open your DB to see if 2.4.0 was added to your version_ver table? Alternatively, just try navigating to /Menu.php on your environment. If the error was incorrectly displayed, navigating directly to /Menu.php will work. Alternatively, You could revert to 2.3.5 from the backup you took before upgrading and wait for 2.4.1, which will address this upgrade issue |
@gyphon for now - i recommend reverting to your 2.3.5 database and code. Sorry for the false-start. |
@gyphon you should be able to upgrade successfully 2.3.5 -> 2.4.2 now. as always, ensure a good backup before upgrade :-) |
If you're already on 2.4.0 or 2.4.1 for production, you can copy the file from the release file at ChurchCRM\service\SystemService.php to your 2.4.0 or 2.4.1 setup, and the built-in upgrade should work. Otherwise, you can always just do a manual upgrade. |
The text was updated successfully, but these errors were encountered: