A new WebSearch gramplet is ready

I was hoping that it would use the same key name but wrap it with a Person override.

So more like WikiTree.ID uses the active person. And HomePerson.WikiTree.ID uses that key from the HomePerson.

So WikiTree.ID would be shorthand for ActivePerson.WikiTree.ID

Probably, we can do this. So, json no needs any changes.

  {
    "nav_type": "Person",
    "attribute_name": "WikiTreeID",
    "url_regex": ".*gedbas\\.de/uid/.*",
    "key_name": "WikiTree.ID",
  }

UID links will look like this:

https://www.wikitree.com/index.php?title=Special:Connection&action=connect&person1Name=%(WikiTree.ID)s&person2Name=%(HomePerson.WikiTree.ID)s&relation=4

If key name has “HomePerson.” then we extract data from Home person.

2 Likes

I’m using version 1.3.2 on Gramps V5.2 and there are two strange things:

  • when loading the version I had errors (it happens again if I reload the addons using the kku tool)
  • I have all the lines duplicated (a first series then the same a second time)
1 Like

got it. Could you give me the error stacktrace please?

I’m not sure if it’s from your addon but here it is:

77995181: ERROR: grampsapp.py: line 188: Unhandled exception
Traceback (most recent call last):
  File "C:\Program Files\GrampsAIO64-5.2.2\gramps\gui\widgets\styledtexteditor.py", line 698, in __set_fallback_icons
    icon = tool_button.get_child().get_child()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get_child'

And this happens 15 or 20 times in a row before the window disappears.

Otherwise this addon is awesome, thank you very much!

I dont see similar code in WebSearch. But now I already have v.1.8.4. Maybe it was already fixed. Anyway, lets try it again in the next beta version in several days.

1 Like

Looks like done. Will be available soon in beta v.1.9.4.


2025-05-23_21-13-23

Mary is home person here.

1 Like

Added the new feature to README

1 Like

I would prefer to use a working example instead of a not working example. So my suggestion is to replace GEDBAS by WikiTree and using real WikiTree IDs.

Other working services “show connection between person A an B” are beside WikiTree: Geni and FamilySearch. As far as I know they are showing only connections between a person and the logged in user. So they cannot be used by this nice new feature.

Examples for WikiTree and webtrees:

1 Like

But if you as a logged in user is available in your Gramps database, you can set yourself as Home person. Then click any other person - it will be ActivePerson. So, I think its possible to use the feature, right?

No, there is no URL parameter for two persons in Geni and FamilySearch.

2 Likes

I’ve updated README and json/csv files to the working example. v.1.9.5.

People,WikiTree Connection,1,https://www.wikitree.com/index.php?title=Special:Connection&action=connect&person1Name=%(WikiTree.ID)s&person2Name=%(HomePerson.WikiTree.ID)s
  {
    "nav_type": "Person",
    "attribute_name": "WikiTreeID",
    "url_regex": ".*wikitree\\.com/index\\.php.*Special:Connection.*",
    "key_name": "WikiTree.ID"
  },

yeah, we depend on data in url path and query parameters data. So, we can not use any feature if url doesn’t have attributes which are required for the feature working.

2 Likes

Now, the v1.9.5 beta version is available here

I tried install 1.9.5, and I have no issues in terminal. Your stacktrace doesn’t have enough info, I dont see WebSearch modules there. It can be not WebSearch issue, but I’m not sure 100% at the moment.

:magnifying_glass_tilted_left: What’s New in WebSearch v1.9.5 comparing with v1.3.2

1. Support for Multiple Contexts in UID Links

You can now use UID attributes not only from the currently active person (ActivePerson) but also from the default home person (HomePerson) within a single URL template.

2. Context Menu: Edit Attributes and Notes

(Please test this feature on a sandbox/test database before using it with real data.)
Added the ability to open the Gramps editor for attributes or notes directly from WebSearch.
Supported entity types: People, Families, Events, Sources, Media, Citations.
Changes are tracked in the Activities tab.

3. Improved AI Request Logic

AI requests for resource suggestions are now performed only when fewer than 10 domains remain unreviewed, helping reduce AI usage costs.
Added a separate AI request type for community resources (e.g., Telegram, Facebook, YouTube).
AI suggestions now use two different badge colors based on the resource type.

4. Support for underscored_place

A new key underscored_place was added for places, which automatically converts names like New YorkNew_York.
Useful for URL templates such as Wikipedia.

5. Extended Markdown in the Info Tab

The “Info” tab now shows:

  • System and user paths to JSON/CSV files
  • Tips on how to create or copy your own files
  • Clickable directory paths

6. Other Improvements

  • Updated record sorting logic in the internal database (ID → record references → metadata).
  • All changes are now logged in the Activities tab, including attribute and note edits.
  • Significant internal refactoring for better compatibility with both Gramps 6.0 and 5.2.
3 Likes

Yes. I am considering adding support for the Gedcom 7.0 identifier structure in the next feature release.

3 Likes

Could you amend the Info tab documentation?

It would be good to include 4 tab icons, the tab names and descriptions.

1 Like

Done. Now the README.md file contains:

1 Like

Good news!
The new stable WebSearch 1.10.8 version is released today and available for update.

Remember, this is major update. I dont recommend to update WebSearch from 0.81.74 to 1.10.8 if you want save your activities history like “visits” or “saves”.

3 Likes

@Urchello

The FamilySearch place lookup (mentioned by @DaveSch and @Davesellers) appears to be a nice addition for WebSearch’s Place searches

It looks like it can pass the Place title as a URL ?text= parameter with comma/spaces substituted with %2C and %20.

For instance, I did a search for “New Castle, Lawrence county, Pennsylvania, USA”

https://www.familysearch.org/en/research/places/?text=New%20Castle,%20Lawrence%20county,%20Pennsylvania,%20USA

It is not case-sensitive but returned more historical possibilities if I broadened the search by trimming out the the county (an administrative subdivision that is typically omitted in US postal addressing) and country/nation. I do not expect that WebSearch would trim the search parameters. I just found how the parameters affected the FamilySearch search results to be interesting.

https://www.familysearch.org/en/research/places/?text=New%20Castle%2C%20Pennsylvania

1 Like

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