* Possible Source Driven Data entry bug for Baptism

Questions regarding use of any Version of Family Historian. Please ensure you have set your Version of Family Historian in your Profile. If your question fits in one of these subject-specific sub-forums, please ask it there.
Post Reply
avatar
AndrewEllis
Platinum
Posts: 36
Joined: 02 Jun 2015 09:27
Family Historian: V7

Possible Source Driven Data entry bug for Baptism

Post by AndrewEllis » 19 Sep 2021 07:07

I'm using version 7.0.8.2 and have been entering baptisms using the Source, Create Source from template/prepare citation option from the toolbar.

Creating a source, I'm then used the Church Records, Parish Register Baptism, then entered the data and completed the fields in the Data Entry Asssistant

I've noticed that the text from source that is automatically created from this process reads as follows:

Baptisms solemnised in the Parish of St Wilfrid's Church Calverley, Yorkshire in the Year YYYY

Has anyone else noticed this?

I've reported it to Calico Pie as a possible bug

Many thanks

Andrew

User avatar
ColeValleyGirl
Megastar
Posts: 4854
Joined: 28 Dec 2005 22:02
Family Historian: V7
Location: Cirencester, Gloucestershire
Contact:

Re: Possible Source Driven Data entry bug for Baptism

Post by ColeValleyGirl » 19 Sep 2021 07:39

Can you post an example of the data entry screen showing how you've specified the date so I can take a look at what's gone wrong -- that plugin is one of mine, not Calico Pie's.

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

Re: Possible Source Driven Data entry bug for Baptism

Post by tatewise » 19 Sep 2021 09:23

Helen, I can repeat those symptoms.
The Autotext Plugin ends that line with " ... the Year YYYY"
i.e. YYYY is literal text.
I was expecting some form of field code with a YEAR qualifier, e.g. ... the Year {DT-DATE:YEAR}

I tried editing the plugin with that and it produced no year display.
I removed the :YEAR qualifier and {DT-DATE} displayed the full date correctly.
So it seems the :YEAR qualifier does not work in that context.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

User avatar
ColeValleyGirl
Megastar
Posts: 4854
Joined: 28 Dec 2005 22:02
Family Historian: V7
Location: Cirencester, Gloucestershire
Contact:

Re: Possible Source Driven Data entry bug for Baptism

Post by ColeValleyGirl » 19 Sep 2021 09:40

None of the standard field codes work as you would expect in plugin text templates, Mike, but the code should substitute YYYY with the year from the date.. Can somebody provide me with an example of the data entry please?

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

Re: Possible Source Driven Data entry bug for Baptism

Post by tatewise » 19 Sep 2021 10:21

Here is my data entry below.
Where is the Help advice on the YYYY code? I could only find the :YEAR qualifier.
Why does " ... the Year {DT-DATE}" display the full date correctly but the :YEAR qualifier does not work?

BaptismDataEntry.png
BaptismDataEntry.png (90.28 KiB) Viewed 1977 times
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

avatar
AndrewEllis
Platinum
Posts: 36
Joined: 02 Jun 2015 09:27
Family Historian: V7

Re: Possible Source Driven Data entry bug for Baptism

Post by AndrewEllis » 19 Sep 2021 16:10

Thanks Mike for checking and posting the screenshot, I can confirm Helen that this is exactly what I did. If you still need screenshots from me I can do this when I'm back home later.
Many thanks to you both
Andrew

User avatar
ColeValleyGirl
Megastar
Posts: 4854
Joined: 28 Dec 2005 22:02
Family Historian: V7
Location: Cirencester, Gloucestershire
Contact:

Re: Possible Source Driven Data entry bug for Baptism

Post by ColeValleyGirl » 19 Sep 2021 16:51

Version 1.5 is now in the plugin store.

You will need to delete the existing Autotext templates for this plugin, via:

1. Tools > Manage Autotext > Autotext for Plugins,
2. Expand Record Baptism Data (England and Wales)
3. Select and delete any existing autotext templates for the plugin, e.g. Baptism post 1812 (England and Wales) and/or Baptism pre 1813 (England and Wales).

Mike, the YYYY code is a hangover from a previous version of the plugin. The :YEAR etc. qualifiers don't work in Autotext...

avatar
AndrewEllis
Platinum
Posts: 36
Joined: 02 Jun 2015 09:27
Family Historian: V7

Re: Possible Source Driven Data entry bug for Baptism

Post by AndrewEllis » 19 Sep 2021 17:19

Thank you Helen for this quick fix, you're a star for writing and updating this

Andrew

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

Re: Possible Source Driven Data entry bug for Baptism

Post by tatewise » 19 Sep 2021 18:11

Helen, are CP aware that qualifiers (like :YEAR) don't seem to work in Autotext?
If not, does it need reporting?
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry

User avatar
ColeValleyGirl
Megastar
Posts: 4854
Joined: 28 Dec 2005 22:02
Family Historian: V7
Location: Cirencester, Gloucestershire
Contact:

Re: Possible Source Driven Data entry bug for Baptism

Post by ColeValleyGirl » 20 Sep 2021 06:47

Mike, Autotext is not processed in any way when it's used within FH, just copied on demand into a note, research note, text from source etc.

Token substitution within Autotext for plugins is the responsibility of the plugin author.

Post Reply