-
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
Bug: Cannot Assign Member to Group #6807
Comments
I was unable to reproduce this on the latest code on the master branch. |
I don't get the error on a new install, when I restore from backup and then the message appears to upgrade DB, and then when I log back in once restored I cannot populate group and see no results. |
@bja2u this sounds like an issue with the data in your database then. Can you look at your database and see the person which your |
yes mu user_usr and all the users assigned in the DB line up with a personper record. I downgraded back to 5.1.1 (last version used prior to upgrading) and I don't have this issue. |
Please review the rollback/restore from back instructions on our wiki here: https://github.com/ChurchCRM/CRM/wiki/Rollback#restoring-a-broken-database-from-backup Specifically step 2 which states: "Restore the database over the existing one. This is ONLY possible if you are restoring a database backup from the SAME version of ChurchCRM." In other words, don't restore a database and the use a different application version. Restotre the database, install the SAME application version, then attempt the application upgrade. |
Yes I still had my backup of my db from 5.1.1 and I reinstalled churchcrm from that version as well. |
YES YES YES!!! Issue resolved with 5.5.0 new release! Tested all functionality I mostly use and found no issues. Thank you!!!! |
Description
When going to a member profile and selecting "Assign New Group" application does not show list of groups available; displays as "No results found".
Steps To Reproduce
Expected behavior
Listing of available groups to assign
Screenshots and/or logs
Debugging Steps
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: