Family Historian User Group

Try as I might I cannot fault the functionality in this latest version of the plugin, that now behaves as I think the average user (and tester) would expect in all respects. I've noticed that no update is performed when changing a Generic Source Type value to the same value as existing - but I can u...

I was initially convinced that ths new version was perfect but finally I discovered that blank Generic Source Type records are once again only updated if the "Force update" box is ticked - strictly correct but confusing for those who do not know the background. I'm not sure if this is deliberate but...

Many thanks for the amazingly quick turnaround in updates to your plug code! The good news is that in the version 0.2 of the plugin, Generic Source Types are added correctly when the previous value was blank whether or not the Force update was ticked or not - and the result(s) displayed in the query...

I was out all day yesterday but having run the new plugin several times this morning, I'm delighted to say that it does indeed fix all the issues I raised and happily re-runs under all circumstances that I've tried. Thanks for such a rapid and comprehensive job in addressing my suggestions. But I un...

Mike, Actually, looking back at my open browser windows it seems I had been looking in the FH PlugIn Store - but got confused about where I had been looking when posting! The behaviour of the plugin seems understandable yet seems inconsistent with the Search & Replace plugin which always brings up t...

Mike, Once again you deliver the goods - this time even before asking! Since the Plugin does not yet appear in the FHUG Downloads directory, I'm treating this as an alpha version where you welcome feedback. I've posted the comments to the other thread Add Source Type to Source plugin (21492) for the...

Mike, I would like to suggest changing the naming convention throughout (including in the Title of the Plugin) to include the word Generic - the column heading in the Source Records window actually just uses the term "Generic Type" not "Source Type" - so I suggest perhaps "Set Generic Source Type" e...

I know this thread is old but it touches upon exactly the area where I'm having issues at the moment. I understand that, to add a Generic Source Type to an individual source record, I just have to insert this into the source record and it will then be available for selection when adding any future r...

Brilliant thanks - now I know what those curly brackets are for! For the record the resulting syntax for three sets of template entries are in full: {individual} was {=CombineText( "", %FACT.TYPE%, " " )}baptised {date} {place} {age}. {=CombineText("", %FACT.TYPE%, " ")}Baptised {=CombineText("", %F...

It has taken me a while to work out how to adapt the syntax of the changes suggested in the post on Civil Unions for my requirement to handle Private Baptisms. For the benefit of others who wish to adopt this approach, the procedure is to start by duplicating the Baptism event for the individual con...

My apologies for not responding earlier to the helpful responses posted by community - while my notifications settings appear to be correct, my default posting options were not, so I was not aware that anyone had responded (and I've been busy in the garden!). I've now fixed that so hopefully should ...

To start at the beginning I wanted to tighten up my issues with duplicated facts and discovered that where an individual has both a public and private baptism I've inadvertently created such a duplicate. So the obvious answer seemed to me to be to create an additional Fact Type for the Private Bapti...

From reading the discussion here I think you are doing yourself a disservice in the title of this series of posts if all that stops working is the Google Maps while you already have the Leaflet Maps alternative up and running.... As I'm sure you are aware Open Street Maps seems to be a very popular ...