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 2.1.25 to 2.1.26-RC1 #1284

Closed
BenoitPel opened this issue May 9, 2016 · 5 comments
Closed

upgrade 2.1.25 to 2.1.26-RC1 #1284

BenoitPel opened this issue May 9, 2016 · 5 comments
Labels

Comments

@BenoitPel
Copy link

hi,

I try to upgrade 2.1.25 to 2.1.26-RC1 and i have a problem on step4

Step 4
The upgrader will now update the database by running several upgrade scripts.
An error occurred. Please check and relaunch.
13:54:6 - ERROR: An error appears when adding field can_manage_all_users to table Users! !
13:54:06 - upgrade_run_2.1.26.php - Loop #1
13:54:05 - upgrade_run_db_original.php - Loop #1

@nilsteampassnet
Copy link
Owner

Just tried to upgrade from 2.1.25 to 2.1.26-RC1 and could not reproduce.
2016-05-09 19_35_44-teampass installation
When did you download the RC1 package?
Can you check the structure of table Users and tell me if field can_manage_all_users exists?

@BenoitPel
Copy link
Author

hi,

i try this yesterday morning.

can_manage_all_users exists.

@nilsteampassnet
Copy link
Owner

Confirmed if this field already exists.

Corrected in 2.1.26-RC1 branch

nilsteampassnet added a commit that referenced this issue May 10, 2016
#1284 fix for can_manage_all_users update during upgrade
nilsteampassnet added a commit that referenced this issue May 10, 2016
#1284 fix for can_manage_all_users update during upgrade
@BenoitPel
Copy link
Author

thanks, i will try this today and get you feedback !

@BenoitPel
Copy link
Author

nice resolution, its work :)

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

No branches or pull requests

2 participants