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

**URL:** <https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447>\
**Category:** Beta Testing\
**Tags:** hacks, bug-filed\
**Created:** [April 13, 2025, 2:02pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447 "2025-04-13T14:02:10Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 13, 2025, 2:02pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/1 "2025-04-13T14:02:10Z")

</div>

Gramps 5.2.4 on Windows 10 and in Firefox 137.0.1

Today, the fix for the known issue described here:

> **[Addon:D3 Ancestral and Descendant Charts - Gramps](https://www.gramps-project.org/wiki/index.php/Addon:D3_Ancestral_and_Descendant_Charts#Issues)**

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](https://gramps.discourse.group/t/descendant-indented-tree/6657/3)

Any suggestions?

---

<div class="post-metadata">

**Author:** ![SNoiraud](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/snoiraud/32/72_2.png) [@SNoiraud](https://gramps.discourse.group/u/SNoiraud)\
**Post date:** [April 13, 2025, 4:36pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/2 "2025-04-13T16:36:07Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 13, 2025, 5:18pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/3 "2025-04-13T17:18:45Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![SNoiraud](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/snoiraud/32/72_2.png) [@SNoiraud](https://gramps.discourse.group/u/SNoiraud)\
**Post date:** [April 13, 2025, 5:21pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/4 "2025-04-13T17:21:32Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 13, 2025, 5:28pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/5 "2025-04-13T17:28:35Z")

</div>

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):

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/0/01ad668cc1a2819bf3f7c0268516743a241d8b46.png)

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 20, 2025, 11:49am UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/6 "2025-04-20T11:49:17Z")

</div>

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](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working/7447/5)) on Win 11.

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

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/8/8c4e65f53e7a9d7faab192f59199a1586a74950f.png)

---

<div class="post-metadata">

**Author:** ![anon44746896](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@anon44746896](https://gramps.discourse.group/u/anon44746896)\
**Post date:** [April 20, 2025, 1:12pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/7 "2025-04-20T13:12:14Z")

</div>

Please create a [bug report](https://www.gramps-project.org/wiki/index.php/Using_the_bug_tracker).

Be sure to start [Gramps AIO from the console](https://gramps-project.org/wiki/index.php/Gramps_6.0_Wiki_Manual_-_Command_Line#MS_Windows) and recreate the error then copy the out in console to the bug report please.

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 20, 2025, 1:16pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/8 "2025-04-20T13:16:48Z")

</div>

```python
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

```

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 20, 2025, 1:31pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/9 "2025-04-20T13:31:38Z")

</div>

Bug report submitted:

> **[0013785: Descendant indented tree fails in Gramps v6 - Gramps - Bugtracker –...](https://gramps-project.org/bugs/view.php?id=13785)**

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 23, 2025, 8:59am UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/10 "2025-04-23T08:59:50Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [April 23, 2025, 9:44am UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/11 "2025-04-23T09:44:52Z")

</div>

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](https://gramps-project.org/wiki/index.php/Gramps_Glossary#addon) should already list an Report update you can install.

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

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 23, 2025, 11:27am UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/12 "2025-04-23T11:27:25Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![GaryGriffin](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/garygriffin/32/6525_2.png) [@GaryGriffin](https://gramps.discourse.group/u/GaryGriffin)\
**Post date:** [April 23, 2025, 4:21pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/13 "2025-04-23T16:21:30Z")

</div>

The bug report (Failed Loading Plugin) [0013785: [Addon D3Charts] Descendant indented tree fails in Gramps v6 [SyntaxError: invalid syntax] - Gramps - Bugtracker – Free Genealogy Software](https://gramps-project.org/bugs/view.php?id=13785) 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.

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 23, 2025, 5:59pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/14 "2025-04-23T17:59:37Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![GaryGriffin](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/garygriffin/32/6525_2.png) [@GaryGriffin](https://gramps.discourse.group/u/GaryGriffin)\
**Post date:** [April 23, 2025, 10:31pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/15 "2025-04-23T22:31:01Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 24, 2025, 12:48pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/16 "2025-04-24T12:48:31Z")

</div>

> [@GaryGriffin](#):
>
> everything worked fine with the latest Firefox on a Mac

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

---

<div class="post-metadata">

**Author:** ![anon44746896](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@anon44746896](https://gramps.discourse.group/u/anon44746896)\
**Post date:** [April 24, 2025, 12:56pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/17 "2025-04-24T12:56:58Z")

</div>

> [@stuck](#):
>
> OK but is there anyone here that can check the behaviour on Windows?

I can confirm it works as I took the time to test and then [edit and update the wiki for the addon](https://www.gramps-project.org/wiki/index.php/Addon:D3_Ancestral_and_Descendant_Charts#Charts_appear_without_content_when_using_local_mode) .

Windows 10 - Gramps 6.0.1

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [April 24, 2025, 1:06pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/18 "2025-04-24T13:06:03Z")

</div>

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

> **[0011800: \[D3 Chart Addon\] Update of d3.js and jquery libraries to newer...](https://gramps-project.org/bugs/view.php?id=11800)**

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 24, 2025, 1:10pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/19 "2025-04-24T13:10:00Z")

</div>

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

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/a/aa3de45aecafc6e660d9400c74c26dd0cbffbe13.png)  
and neither of the buttons do anything.

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

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/9/9ecab79ee45f20bf14fe8f86cab03ba2ec878b28.png)

I’m open to suggestions…

---

<div class="post-metadata">

**Author:** ![anon44746896](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@anon44746896](https://gramps.discourse.group/u/anon44746896)\
**Post date:** [April 24, 2025, 1:11pm UTC](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/20 "2025-04-24T13:11:56Z")

</div>

> [@emyoulation](#):
>
> Will updating the libraries resolve the security issues and remove the need for the patch?

No as pointed out in the linked issue [9602](https://gramps-project.org/bugs/view.php?id=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!

[Next page](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447.md?page=2)
