* Add a General Record Source & optionally event Version 1.3

For users to report plugin bugs and request plugin enhancements; and for authors to test new/new versions of plugins, and to discuss plugin development (in the Programming Technicalities sub-forum). If you want advice on choosing or using a plugin, please ask in General Usage or an appropriate sub-forum.
Post Reply
User avatar
Richard_Hyland
Gold
Posts: 25
Joined: 06 Jun 2011 18:04
Family Historian: V7

Add a General Record Source & optionally event Version 1.3

Post by Richard_Hyland » 11 Feb 2022 10:06

I am having a problem with the plugin Add a General Record Source & optionally event Version 1.3.

Most of the time it works and adds a record. However occasionally when I enter all the information and press OK, Family Historian closes, and nothing is updated. There are no error messages and I have no idea why it has not worked. Even when I try again FH just closes.

This can happen with any of the three GRO Index Types.

Richard

User avatar
tatewise
Megastar
Posts: 27080
Joined: 25 May 2010 11:00
Family Historian: V7
Location: Torbay, Devon, UK
Contact:

Re: Add a General Record Source & optionally event Version 1.3

Post by tatewise » 11 Feb 2022 10:19

As it says in the Plugin Store, that plugin is not designed to work in FH V7.
It says: "Family Historian Version(s): V5 V6 "
You have discovered what happens when run in FH V7 ~ it sometimes crashes FH.
This is a known symptom of plugins not yet updated for FH V7.

I suspect the reason it hasn't been updated is that FH V7 Source Templates and various DEA effectively replace that plugin.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

User avatar
Mark1834
Megastar
Posts: 2147
Joined: 27 Oct 2017 19:33
Family Historian: V7
Location: South Cheshire, UK

Re: Add a General Record Source & optionally event Version 1.3

Post by Mark1834 » 11 Feb 2022 11:22

It's worth bearing in mind that plugins are not written on stone tablets (either physically or metaphorically...). While it is generally considered unhelpful if other members post uninvited modifications to published plugins, any user is free to modify downloaded plugins for their own use. Making a relatively short and simple plugin like this compatible with FH7 may be as simple as adding a single new line of code.

Perhaps a good protocol in these circumstances would be for the plugin author to either update the plugin for FH7, or confirm that it will not be updated, as there are now better ways of doing the same thing. If a user is particularly attached to an old plugin and wants to continue using it, they are then free to seek advice on how feasible it would be to modify if they are not comfortable with doing it themselves.
Mark Draper

Post Reply