Family Historian User Group

They had to be Templated Sources because Citation Detail and Reference are not Generic fields.
BTW: Once you create a Query it is immediately saved. You would have to specifically delete it.
You can use any existing Query to interrogate the Fields DRA without affecting the Query.

Unfortunately, the Query > Columns tab > Fields pane does not support Templated Named Metafields. Please refer to the Help for Understanding Data References and scroll down to Data References And Metafields . There it explains the data reference structure for metafields. e.g. %FACT.SOUR[1].~TX-REFER...

%FAMS.MARR[1].PLAC>STAN% is almost a perfectly correct Data Reference for the Standardized field. %CUR~FAMS>MARR.PLAC>STAN% is what you should use for the Marriage Standardized place. However, it is not allowed in the position you have used in a =FactText(...) function, so is ignored. The =FactText...

It might help if you could post screenshots of the Marriage Certificate and 1881 Census. See the FHUG Knowledge Base > Forum Usage under Attachments and Taking Screenshots for how to do that. Are you looking in Census records for a William about the right age with father John and mother Jane? Try th...

Welcome to the FHUG. It is quite common for entries on Census Returns to be erroneous and inconsistent. Unlike BMD Certificates that are completed near the date & place of the event, Census birth details rely on the person remembering and the enumerator hearing & recording the details correc...

Thank you for your reply but it does not answer either of my specific questions. If case sensitivity was an option and was enabled then: G%E%HAY% will NOT find Gordon Edward Hay or George Edmund Hays because HAY does not match. G%E%Hay% would work as long as the names did each start with upper-case ...

I'm not sure I fully understand how those wildcards work. In 21168|[Wish List 633] Name Filtering to handle inconsistent entry or miss slashing of names you say that the wildcard "%" covers any number of characters. Also, your examples suggest the filters are case-insensitive. So would G%E...

Plugin authors may no longer attach plugins to forum postings, so all old attachments have been deleted. Only a handful of users showed an interest in this plugin so did not seem worth publishing in the Plugin Store. If you have not deleted the plugin it should still be listed in Tools > Plugins... ...

Yes, it is not advisable to have various Projects in different locations. Why not? I have a live FH Projects folder for actual research projects, and a second FH Projects (Development) folder for test projects. It works very well, and I can easily flip between live and test projects using the Recen...

Yes, it is not advisable to have various Projects in different locations.
Ideally, all Projects should be in the File > Project Window... Location: path.

I presume in your examples that the Location: is just a drive letter.

What is it about paths under Parallels that are different from standard Windows paths? Some examples of paths you think are too long might help explain what needs changing. To ensure FH includes Media in backups requires the files to be within the Project folder. If the Project is called MyFamily th...

It is probably not the environment, just that FH hangs with the Not Responding message.

Use Unsourced Individuals link to download plugin V0.3 which adds a progress bar to prevent FH hanging.

An issue was discussed recently with regard to AS that has a SYSTEM.DATE option which is based on the PC locale format and may get mishandled when entered into FH source templates where the Short Date Format is different.
See Casting template data as a particular data-type (22911).

John, it is a bit more efficient to use the following to get day, month & year as integers. local dpDatePt = dtDate:GetDatePt1() local Day = dpDatePt:GetDay() local Month = dpDatePt:GetMonth() local Year = dpDatePt:GetYear() Once you have added the Date to a Fact it may be a good idea to use Get...

Mark, it was HKCU\SOFTWARE\Calico Pie\Family Historian\2.0\Preferences\ that I thought might need adjusting to match the PC locale date format read from the Windows Registry. Your suggestion of reminding the user of the expected short date format is probably better. John, yes, it is odd that SetValu...

Hmm does this plugin not like large files? I've just shy of 69k in the file and it basically just hangs with not responding ... or am I being impatient? ;) It was written as a one-off temporary plugin for a couple of FHUG users, so it is very unsophisticated. Thus it has no mechanism to keep Window...

Yes, it is a little inconsistent and could be reported to CP if you felt strongly.
However, there is a slightly awkward workaround using the ToUpper(...) function with LeftText(...) and MidText(...):
=ToUpper( LeftText( Relationship( Fileroot() ), 1 ) )=MidText( Relationship( Fileroot() ), 2 )

Mark, that is NOT entirely what Privacy and Security Standards for Published Plugins says! That would allow the PC locale settings to be read from the Windows Registry, and then the Preferences Date setting to be changed (temporarily) in the Windows Registry as it would be "essential to the sta...

Note that the EstimatedBirthDate function returns a Date Point value and not a Date value.
local dtpMin = fhCallBuiltInFunction( "EstimatedBirthDate", ptrIndi, "EARLIEST", 5 )

So you must use dtDate:GetDatePt1() to be able to compare with dtpMin.

To manipulate FH pointers you use fhNewItemPtr() and the Item Pointer object Methods. To manipulate FH dates you use fhNewDate() and the Date object Methods. You may also need to use fhNewDatePt() and the Date Point object Methods. Those are all covered by the How to Write Plugins help Function Inde...

As a plugin author, using iuplua, it is necessary to consider a wide (and narrow) variety of monitor screen sizes.
So you may need to split the dialogue into several tabs.

I click on the large blue DOWNLOAD (1.63KB) button that says underneath:
'The download button will start your download and show a message from our advertisers in a new window.'
It seems that the advertisers new window is infected:

Just for my edification is there a way to do a conditional statement like I had originally tried? No, not to govern the <br> and <para> codes because (as I said) the =TextIf(...) function requires text parameters and the formatting codes <br> and <para> are NOT text. Your {=TextIf(...)} conditional...

OK, I understand better now what you were trying to achieve. The cause of your original problem is the Box Types and Conditions settings. They determine which spouse the married info goes on. In your screenshot, the Box Types column summarises those settings. They must be the same for both the Marri...

Roberto, we are no longer allowed to attach plugins to posts for security reasons and must use file share links. The plugin was never popular enough to warrant publishing in the Plugin Store. Use the Unsourced Individuals link to download the plugin V0.2. ( BTW: My Avast anti-virus reported that Bil...