Descendant indented tree: local workaround no longer working in 5.2.4, plus total failure in 6.0.1

Gramps 5.2.4 on Windows 10 and in Firefox 137.0.1

Today, the fix for the known issue described here:

no longer works for Firefox.

I can’t say when it stopped working but it was OK as recent as Dec 2024 when I made this post:
https://gramps.discourse.group/t/descendant-indented-tree/6657/3

Any suggestions?

This is a security issue.
You need to set security.fileuri.strict_origin_policy to False as indicated in the page you cited earlier

1 Like

You didn’t read my reply, that fix no longer works on my set up.

It did work back in Dec 2024, but not today, even though the relevant ‘securtity… …policy’ is still set to false.

It works for me on linux with firefox 137.0.1
Is it a local page or a remote page ?

Local.

I also uploaded the output to a small bit of webspace I have and tried it from there. It didn’t work there either.

I also just discovered that this report fails completely when used with Gramps 6.0.0 (Win 11):

Gramps v6.0.1 on Win 10 and Win 11

I’ve now discovered that the Descendant Indented Tree report fails on Win 10 as well as reported previously (Descendant indented tree: local workaround no longer working - #5 by stuck) on Win 11.

Is it just me or can others here reproduce this crash:

Please create a bug report.

Be sure to start Gramps AIO from the console and recreate the error then copy the out in console to the bug report please.

C:\Program Files\GrampsAIO64-6.0.1>gramps
Traceback (most recent call last):
  File "C:\Program Files\GrampsAIO64-6.0.1\gramps\gen\plug\_manager.py", line 270, in load_plugin
    _module = self.import_plugin(pdata)
              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\GrampsAIO64-6.0.1\gramps\gen\plug\_manager.py", line 304, in import_plugin
    module = __import__(pdata.mod_name)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\myUserName\AppData\Roaming\gramps\gramps60\plugins\D3Charts\DescendantIndentedTree.py", line 1499
    ErrorDialog(_("Failure writing {target_path}: {message}").(target_path=self.desthtml, message=str(msg)),
                                                              ^
SyntaxError: invalid syntax

Bug report submitted:

I’ve had an email from the bug tracker saying this has been fixed now.

As mere mortal user with no coding ability or real grasp of how open-source development works, can I ask how long it will be before the fix is available in the Windows AIO package?

Thanks

The problems was in an addon. So the fix is available more immediately.

It looks like @GaryGriffin has already pushed the fix out to the D3Charts addon.

Since he is also the volunteer curator of the addons repository, the Addon Manager should already list an Report update you can install.

Please update and let us know if the update fixes the ussue on you system.

Ah, yes, I understand now.

Yes, the update means the report no longer crashes but it still doesn’t work because the problem as given in my original post still persists.

Namely that the local workaround for “Charts appearing without content - related to a security vulnerability update to Browsers. (i.e. local HTML files ought not to be authorized to open files from different sub-directories)” no longer works in Firefox. Nor can I get the report to work using Edge.

NB my mention of using Edge should make it clear that I’m using Gramps on Windows (both 10 and 11).

The bug report (Failed Loading Plugin) 0013785: [Addon D3Charts] Descendant indented tree fails in Gramps v6 [ SyntaxError: invalid syntax ] - Gramps - Bugtracker – Free Genealogy Software was about the report failing due to typo. This typo was fixed.

I ran on gramps 6.0 and used Mac Safari and the reports displayed correctly.

This does not address the Issues listed in the Addon wiki for Firefox and Chrome.

1 Like

Is there any point in me submitting a new bug report about this failure on Firefox?

I just loaded Firefox 137.0.2 on my Mac and followed the instructions in the wiki page, going to about:config and setting security.fileuri.strict_origin_policy to False.

I then opened the Ancestral Fan Chart and it had the expected content. I then tested the other two reports (Ancestral Collapse and Descendant Indented Tree) and they also had content.

So everything worked fine with the latest Firefox on a Mac (once the browser config was set as described in the Addon wiki page).

1 Like

OK but is there anyone here that can check the behaviour on Windows?

I’ve got both a Win 10 and a Win 11 device and it’s not working any more on either of those machines. It was fine a few months ago.

Thanks

I can confirm it works as I took the time to test and then edit and update the wiki for the addon .

Windows 10 - Gramps 6.0.1

Will updating the libraries resolve the security issues and remove the need for the patch?

Hmm, it’s definitely not working for me. All I get is:


and neither of the buttons do anything.

and in about:config the relevant policy is set correctly:

I’m open to suggestions…

No as pointed out in the linked issue 9602: [Upstream Browser Security Change]HTML & SVG generated report doesn’t work for local file system with browser

This is how browsers are by default now due to an upstream browser security change!

1 Like