-
Notifications
You must be signed in to change notification settings - Fork 430
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
fix: Typo alt_name -> alt_names #1854
base: master
Are you sure you want to change the base?
fix: Typo alt_name -> alt_names #1854
Conversation
This issue does not seem to occur if creating the places from the Places View |
I can't reproduce this. I don't understand step 4 - "Go to Places tab". What places tab do you mean? If I create a new place from within the event editor, it seems to create the "alt_names" entry correctly. |
I'll do a screen recording tonight, from start to end. I'll also do another pull incase it has been resolved in the last week. Cheers |
@coldkick2 Does this bug affect Gramps 5.2.x release, or only the master branch? |
Only master, it did not affect the release branch when I tested |
@dsblank Can you reproduce this problem? |
Yes, this is a simple typo: "alt_name" should be "alt_names". @coldkick2 do you want to fix it here? |
Sorry, I've been very busy. It's always something small and simple. My arch install also is crashing on boot now, so if I can't get that resolved quickly I'll close my ticket so the fix can go in on another branch. |
When editing a place the application can crash if the alt_name is not set.
Steps to reproduce:
An alternative solution would be to ensure the alt_name field always exists, but it is unclear to me why it doesn't exist in this usage pattern, and this protection would ensure it doesn't break in the same way again in the future.