# Fixing a Addon for an Earlier Version of Gramps **URL:** \ **Category:** Development\ **Tags:** third-party-addon\ **Created:** [December 10, 2025, 8:50pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919 "2025-12-10T20:50:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Jakim\_Friant](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/jakim_friant/32/7954_2.png) [@Jakim\_Friant](https://gramps.discourse.group/u/Jakim_Friant)\ **Post date:** [December 10, 2025, 8:50pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919/1 "2025-12-10T20:50:04Z")
Fifteen years ago I wrote a plugin for Gramps called [PedigreeChart](https://github.com/gramps-project/addons-source/tree/maintenance/gramps60/PedigreeChart) that would create a chart specifically for printing on letter or A4 sized pages. Recently a user reached out to me because he wanted to include the chart in the Book feature for reports. That’s easy enough to do, my issue though is that he is using Gramps 5.1. I’m still working my way through the new development process, setting up a Github fork of “addons”, “addons-source”, etc., and my question is whether it is appropriate to target my Pull Request against the “maintenance/gramps51” branch for this user. The fix works in both 5.1 and 6.0, so I can definitely create a pull request for gramps60 too. I just want to make sure I’m following the correct process before I move forward. ---
**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:** [December 10, 2025, 9:03pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919/2 "2025-12-10T21:03:31Z")
@GaryGriffin has been volunteering to curate the Addons Source repositories and publishing updates to the [Addon List](https://www.gramps-project.org/wiki/index.php/6.0_Addons#Addon_List). Tagging him here to draw his attention. _ **Iff** _ the only differences in your addon code for different Gramps versions is in the Registration files, you might want to look at how the Isotammi groups manages their `.gpr.py` files. [Example `.gpr.py`](https://github.com/Taapeli/isotammi-addons/blob/master/source/FilterParams/FilterParams.gpr.py) They make their `.gpr.py` file• adaptive. There are base registration attribtes common to all version of Gramps. But it registers different expanded attribute subsets specific to the Gramps version. This lets @kku release updates across versions without additional labor. And @ahs3 has volunteered to help shepherd developers having difficulties with navigating GitHub intricacies. ---
**Author:** ![anon44746896](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@anon44746896](https://gramps.discourse.group/u/anon44746896)\ **Post date:** [December 10, 2025, 9:08pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919/3 "2025-12-10T21:08:18Z")
> [@Jakim\_Friant](#): > > Fifteen years ago I wrote a plugin for Gramps called PedigreeChart Thanks for the addon use it quite a bit. _[https://www.gramps-project.org/wiki/index.php/Addon:PedigreeChart](https://www.gramps-project.org/wiki/index.php/Addon:PedigreeChart)_ Question about the optional prerequisite of numpy , what benefits do you get? [addons-source/PedigreeChart at maintenance/gramps60 · gramps-project/addons-source · GitHub](https://github.com/gramps-project/addons-source/tree/maintenance/gramps60/PedigreeChart) ---
**Author:** ![Jakim\_Friant](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/jakim_friant/32/7954_2.png) [@Jakim\_Friant](https://gramps.discourse.group/u/Jakim_Friant)\ **Post date:** [December 10, 2025, 9:26pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919/4 "2025-12-10T21:26:02Z")
@emyoulation I will look at the example you provided. Thank you. @anon44746896 Great question about the dependency on numpy. I wondered the same thing when I was looking back over my code. I will probably start by addressing the end users request first and then go back and look at cleaning up the plugin code later. ---
**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:** [December 10, 2025, 11:02pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919/5 "2025-12-10T23:02:12Z")
> [@Jakim\_Friant](#): > > I’m still working my way through the new development process, setting up a Github fork of “addons”, “addons-source”, etc., and my question is whether it is appropriate to target my Pull Request against the “maintenance/gramps51” branch for this user. The fix works in both 5.1 and 6.0, so I can definitely create a pull request for gramps60 too. My suggestion is a PR against gramps60 and another on gramps51. This is what I suggest if I see a PR on only gramps51, for instance. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\ **Post date:** [January 9, 2026, 11:02pm UTC](https://gramps.discourse.group/t/fixing-a-addon-for-an-earlier-version-of-gramps/8919/6 "2026-01-09T23:02:54Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.