-
Notifications
You must be signed in to change notification settings - Fork 52
Unable to import .gramps file to gramps web #630
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
Comments
The import function used by Gramps Web is the same as the one used by Gramps Desktop. You can try importing it in Gramps Desktop to check if you get an error there as well. |
I can load the export in teh desktop app without any errors |
I suspect you have a setup issue and your celery container can't access the cache volume. Try creating a file in |
Ive setup the infra using the default docker-compose.yml file as instructed in your install manual: https://www.grampsweb.org/install_setup/deployment/. So I dont expect any setup issue. Import of the .ged file is working fine. When I try to load the media files for it, I get red cross again and this time I see this error: grampsweb_celery | [2025-03-21 11:01:18,094: INFO/MainProcess] Task gramps_webapi.api.tasks.import_file[6e8f2fa4-ab7a-4f85-966c-d2800a786500] received I belive that cache folder access is working just fine. This is content of all volumes post clean install, import of the .ged file and attempt of import the media files: root@databox:/mnt/.ix-apps/docker/volumes# find grampsweb_gramps_* |
I'm also seeing this message frequently: grampsweb-grampsweb-1 | ERROR:root:Error parsing list of recent DBs from file /root/.gramps/recent-files-gramps.xml: no element found: line 1, column 0. |
whenever I try to load media files that match the media from the .GED export, I get the error: grampsweb_celery | File "/usr/local/lib/python3.11/dist-packages/gramps_webapi/api/resources/util.py", line 1043, in update_object Loading media that are not referenced by teh GED file (wrong path) is working fine... |
Please help me fix this |
Ok, this is a bug I believe. We should not have https://github.com/gramps-project/gramps-web-api/blob/master/gramps_webapi/api/tasks.py#L337 But it's unrelated to your original problem. |
I see that this "bug" is not a recent code change. Meaning I have no recent version to downgrade to to skip the impact of this bug. When do you expect this bug would be fixed ? Thanks |
Please don't ask this question. Feel free to submit a PR. |
Ive exported my tree from Gramps AIO64-6.0.0--1 using "Grams XML (family tree)" to data.gramps file. Trying to import it to fresh new instance of self hosted gramps web:
Gramps 5.2.4
Gramps Web API 2.8.2
Gramps Web Frontend 25.3.1
Gramps QL 0.3.0
Sifts 1.0.0
locale: en
multi-tree: false
task queue: true
OCR: true
chat: false
When I select the .gramps file in the admin section "Import", I get almost immediately a red cross icon with description "Failed importing GRAMPS file".
docker output logs:
grampsweb_celery | [2025-03-21 10:06:25,251: INFO/MainProcess] Task gramps_webapi.api.tasks.import_file[b0528977-e0e9-4aa7-9121-3c0876aa65d5] received
grampsweb_celery | [2025-03-21 10:06:25,267: ERROR/ForkPoolWorker-1] Task gramps_webapi.api.tasks.import_file[b0528977-e0e9-4aa7-9121-3c0876aa65d5] raised unexpected: ValueError('Failed importing gramps file')
grampsweb_celery | Traceback (most recent call last):
grampsweb_celery | File "/usr/local/lib/python3.11/dist-packages/celery/app/trace.py", line 453, in trace_task
grampsweb_celery | R = retval = fun(*args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File "/usr/local/lib/python3.11/dist-packages/gramps_webapi/util/celery.py", line 20, in call
grampsweb_celery | return self.run(*args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File "/usr/local/lib/python3.11/dist-packages/gramps_webapi/api/tasks.py", line 207, in import_file
grampsweb_celery | raise ValueError(f"Failed importing {extension} file")
grampsweb_celery | ValueError: Failed importing gramps file
The text was updated successfully, but these errors were encountered: