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

Upgrade on production site failed #1523

Closed
gyphon opened this issue Dec 5, 2016 · 5 comments
Closed

Upgrade on production site failed #1523

gyphon opened this issue Dec 5, 2016 · 5 comments

Comments

@gyphon
Copy link

gyphon commented Dec 5, 2016

image

@DawoudIO
Copy link
Contributor

DawoudIO commented Dec 5, 2016

you get this when you login with a person who does not have admin perms

@crossan007
Copy link
Contributor

@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

@crossan007 crossan007 modified the milestones: 2.4.1, 2.4.2 Dec 6, 2016
@crossan007
Copy link
Contributor

@gyphon for now - i recommend reverting to your 2.3.5 database and code.

Sorry for the false-start.

@crossan007
Copy link
Contributor

@gyphon you should be able to upgrade successfully 2.3.5 -> 2.4.2 now.

as always, ensure a good backup before upgrade :-)

@crossan007
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants