Grafik Preview Doesn't work

Help
1

Hello,

I haven’t worked on Gramps for a while. Currently installed on LMDE6

GRAMPS: 5.2.2
Python: 3.11.2
BSDDB: 6.2.9 (5, 3, 28)
sqlite: 3.40.1 (2.6.0)
LANG: de_DE.UTF-8
Betriebssystem: Linux
Verteilung: 6.1.0-33-amd64

When I click on an image saved as a source and go to Preview, I get this error message: g-io-error-quark … gramps-media-ansicht hosted at ImgBB — ImgBB

I’ve never had any problems with this in the past! The file at the end of the path begins with Z#. If I delete the #, the preview is possible again.

But I can open images with this beginning from every graphics program on my system! Just not from Gramps… That must be Gramps, since I’ve always named these files that way and could open them in previous versions.

I don’t want to have to rename the filenames. Is there a way to determine if this is Gramps’ fault?

Best regards

2

The problem description is unclear about how the Media object path is stored. So isolating the problem is harder.

Please post a capture of the Media Object editors

Media Reference Editor opened from a Gallery tab showing the Shared Information

image
image714×898 82.4 KB

Media Object Editor opened from the Media category

image
image1428×545 48.2 KB

Cllicking the Path folder icon button will show a dialog will the full path and whether the Relative Path was applied. (Note that 5.2.x and earlier will not validate a URL path imported from other software. You have to use Cancel, not OK to exit the dialog. Fixing a bad path is not possible in these versions. However, Gramps 6.0.0 and newer will allow URLs.)

image
image1130×688 92.5 KB

3

Hello,

The error occurred here: gramps-fundstelle hosted at ImgBB — ImgBB

But also in the other windows mentioned.

As I mentioned, I’ve been using this file name for about four years, even under other Gramps versions, without any problems.

The path is found… but only if I remove the # in the file name.

I’ll probably have to install older Gramps to see when it will work again? :frowning:

But thanks for your attention. I hadn’t noticed it before because I hadn’t worked on the database since the upgrade to 5.2.2 :-/

Best wishes and Happy Easter!

4

Yes, I saw that before. But understanding the path is critical.

The most likely suspect is “linkrot” … that ImgBB changed the way it parsed parameters passed via the URL. So the test is find the full URL (including the # ) and pasting it into a browser addressbar. If it fails there, then they changed the ImgBB image hosting interface.

A fix might require writing a SuperTool script to trim off the trailing hashtag on all the Media Object ImgBB paths.