-
Notifications
You must be signed in to change notification settings - Fork 70
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
Gramps XML export fails with 'can only concatenate str (not "NoneType") to str #474
Comments
Hi, that error is already tracked here But it would be great if you could help investigate. Can you please go to the list views (people etc.), open the filter, choose GQL and try out the following filter:
for all of the object types except media and notes? Does it give any results? Background: There is an object in your database that has a |
Thanks - no results, though. I restarted the container and tried again, still no result, and also same error when exporting. My instance is public if you want to investigate :) |
😱 public? |
I mean, a public URL but you need an account still, of course... |
Anyway, I would appreciate suggestions on how to proceed, I an uneasy having no backups with all the work I have been doing :) |
Yep understood. So you need to find out which of your objects has a "None" in the https://www.grampsweb.org/dev-backend/queries/ You need to fetch the You could also employ my poorly known library https://github.com/DavidMStraub/gramps-web-api-client. |
I finally got around to learning how to do this - sorry for being slow :) Anyway, I queries the API and retrieved:
None of them (heh) have 'None' written anywhere in the json, but maybe I am searching for the wrong thing. What exactly am I looking for? :) |
Python |
All dates have a "format": null value - what exactly am I looking for?
? |
I imported a family tree-backup from the desktop version to gramps web, and now I've done a bunch of work on it (thanks for the tool!), and would like to back it up but I am met with this error when trying.
I assume I have some weird data somewhere, but I am not sure how to proceed to fix it.
The text was updated successfully, but these errors were encountered: