Gramps / Interactive Family Tree / net::ERR_BLOCKED_BY_CLIENT

[johnjohndoe]

I am trying to visualize my Gramps project via the plugin by launching the "Interactive Family Tree" in order to render images. Showing images seems not to be possible when launching the viewer locally as a standalone application.

I do not understand if the launched website should be able to load the data and images just by itself or whether I have to do something. I read in the related issues that CORS is important but that is addressed in the URL. I also read about serving the *.ged file from a public web server. I tried that, too - which resulted in different errors. It would be great if someone could clarify how exactly the Gramps plugin is supposed to work. Thank you!

How to reproduce

1. Start Gramps 5.1.2
2. Select Tools / Analysis and Exploration / Interactive Family tree...
3. The default browser (Brave) opens the following website:

   https://pewu.github.io/topola-viewer/#/view?utm_source=gramps&handleCors=false&standalone=false&url=http://127.0.0.1:8156/
   

Observed behavior

• The website renders without content, only Failed to load file. Failed to fetch.
  

• The browser console outputs:

  Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.
  pewu.github.io/:1 GET https://www.googletagmanager.com/gtag/js?id=UA-334534-14 net::ERR_BLOCKED_BY_CLIENT
  load_data.ts:70 GET http://127.0.0.1:8156/ net::ERR_BLOCKED_BY_CLIENT
  

Expected behavior

• The website renders the family tree with pictures.

Related

• Showing Images of People When Loading GEDCOM From URL Using Topola Viewer Online #66
• Pictures / thumbnails do not display as expected in Interactive Family Tree  #38
• Security issue #35

[PeWu]

Thanks for the report.
The issue here is that Brave by default blocks access to localhost connections.
See e.g. here: brave/brave-browser#15004
So, to make the Topola Viewer work in the Gramps addon mode, you'd have to allow it to access localhost.

[johnjohndoe]

👍 Nice. Thank you. For some reason I did not try another browser. It works fine with Firefox!

Maybe you still want to mention this in the README and Gramps wiki. It could be a big initial blocker for people to use your tool.

Other than that this issue can be closed.