Freezing URL on Dynamic Web Report


Do you know if it’s possible to freeze URL of the Dynamic Web Report from one export of this report to another? New information must have a new URL but information present from one version of this report to another should be the same URL.

Curently, people, places, sources… URL change over exports and are difficult to use as links on other sites.

Thank you.

Can you explain this in detail ?
Can you provide an example ?


These url are about the same person (Catherine Tabourier), now and when I saved it in a web page on dec. 2017:

Url are different and particularly idx which I think is the key issue, it seems not permanently associated with the “Catherine Tabourier” people object in gramps and varies from one creation to another of DWR web pages (maybe when number of objects varies in gramps?)

Should it be possible to use something like handles instead?

There is no user visibility or control of Handles in the GUI. It seems like a persistent IDX could be based on IDs instead…

I wonder whether the generated number is based on the center person & filtering during generation?

I suppose the two versions are related to 2 different gramps version ?
The idx is not the ID for the person. The real ID is Bk00137. The idx is an index in the json data table.
As your data grew a lot between the two dynamic web, the index in these tables differ.
You probably start to create the dynamic web with different parameters.

The dynamicweb plugin is an addon and it appears the author is relatively silencious since 2016

I don’t like to share URL like that. This is a general problem for all web sites which are often modified.

I just clicked on the links and they are for different people.

Tabourier, Catherine [Bk00137]

Leveque, Aignan [I03600]

And the Leveque record has a date of 2019-10-08 14:43:53 so was created after 2017.

Are you indicating that this second URL used to point to Tabourier, Catherine [Bk00137] and is now pointing to Leveque, Aignan [I03600] ? Do you have an archived 2017 version of the webpages?

Obviously the IDX isn’t based on the ID. All the example IDX values were numeric, without an alpha leader. I was suggesting that maybe it could be changed to use IDs instead of the simple counter?

I suspect that one of the benefits @PLegoux (Patrice) was hoping for from permalinks is to make incremental revisions possible. Although his cited example of sharing URLs is also an excellent reason.

On the other had, it also looks like that modern search URL could be made to survive new IDX value by just eliminating that IDX search parameter. (It’d probably be slower and return multiple hits on namesakes.) The old example corresponds to a single individual.

1 Like

This is done by an external javascript library outside gramps, so no way to do that.

1 Like

Would it be possible to make a log file or an ini file with the used IDX paired with the Gramps ID, and to get the Library to check this list of data pair when regenerating a web site?

Would that be a workaround for this?

1 Like


I was not there to answer you. I apologize.

In the past I won’t have this issue because ID in my gramps db was “standard” IDs (Innnnn). If I wont persistent-like URL I used search of IDs instead of search of person’s names in DWR then I removed idx from the url and everything was fine.

Now I’ve changed IDs of my family into Beruck notation leaving all other persons with regular IDs. Bk IDs are not really unique for search engine (if I want to search the bk00001 person, search engine will provide bk00001 (me), bk00001v (my daughter)…)

So these past days, I’ve learned python and develop some code to homogenize my Bk persons ID. I changed them to bk00001_ instead of bk00001, bk00001v_ etc… The trailing underscore makes IDs unique again for search engine.

It’s a workaround but it works pretty well (it will be best to have persistent idx but it’s okay).

P.S: I don’t archived previous DWR I generated, I will in the future. I begin now. Url is now based on,
the first one is
So I’ll be able to save and compare results in the future

Thanks for your ideas and support !


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.