Toby Turner wrote: > I got to my computer first thing this morning and made > your suggested FAG website address: > [SNIP] > I still get the Content Blocked error message on the re-built site. Toby, I just tested using one footnote template with target="_blank" and one without. Both worked as expected, i.e., the one with target="_blank" opened the FAG site and the other one got the error message. I do not know why your results with target="_blank" are different. It's possible that there is some issue related to me using the development version of SS for testing. There is one unreleased change in the development version related to SS detecting the https protocol in source URLs, and that may be affecting how SS works for you. Can you change the source footnote to use the http protocol in place of https and see if that changes the outcome to match what I observe? > Because I am unwilling to change my frame style, I guess the thing > to do is to forget about providing a link to a grave site. I'd like to understand why I get different results than you do. I do not like mysteries where SS is concerned. > Even had your fix worked, I suspect FAG would close this loop hole. Nope. The method with target="_blank" is not a loophole. Their server has no idea that the target attribute was used to open their site in a new tab or window. To the server, the browser is fetching a particular URL and displaying the result in an unframed tab or window, which is no different from most requests to the server. If they reject that request, *ALL* requests to that URL would fail, effectively making their site useless. > Thanks for trying to fix this If you really want to thank me, you can do that by performing the test I asked about above. Your results may indicate a bug in SS, and if so, I want to fix it. Given I can't replicate the behavior you have reported, I need your help to do further tests to determine what the problem is. John

There is a curly bracket here instead of a square one. Is that the issue? [CD} is: Plot 104-D|| ||40956381 On Wed, Aug 7, 2019 at 5:16 PM Mark (LI) <[email protected]> wrote: > John, I have been trying to use the format you gave for Find-A-Grave > citations, without success. > Here's what I currently have for the full footnote: > <[COMPILER], ><[ITAL:][TITLE][:ITAL].> > <; Memorial Number: \<a > href="http://www.findagrave.com/memorial/[CD3]"\>[CD3]\</a\>> > < [COMMENTS],>. > > [TITLE] is: Find-A-Grave web site > [Url] is: http://www.findagrave.com/ > [CD} is: Plot 104-D|| ||40956381 > > And here is the result I see in a TMG narrative report footnote: > 9. Find-A-Grave web site. > <; Memorial Number: unknown detail</a>>. > > Using ver 9.05 > What am I doing wrong? > Thanks, > Mark > > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >

Toby Turner exposed issues with trying to have a Web reference in a citation detail to output in both TMG reports and Second Site. Several suggestions were made to try to overcome some issues and bugs in TMG report handling of HTML codes with varying success. As I have made a point to have such Web citation references appear in both types of output I thought I would offer another suggestion based on my own custom FindAGrave source definition. I have found what seems to reliably work is to construct the Source Definition to output the Web code in two parts: one for TMG reports and one for Second Site. This separaton can be accomplished by using the TMG codes [HID:][:HID] and the Second Site codes [SS:][:SS] and [SS-HID:][:SS-HID]. While several aspects of my example template probably "should" not be necessary, I know that it does work in both TMG reports and Second Site. This template may seem a bit complex, but it can be carefully constructed just once in the Source Definition. Further, following John's suggestion the URL is a Source Element in the Source Definition and it allows a split CD to simply have the necessary data. Also if entering multiple citations for the same cemetery, the F3 key will be useful for the CD. The following is a "simplified" construct (though not very simple) to somewhat reflect the output Toby was trying to accomplish. I am only showing an example Full Footnote template. I leave enhancing it with other data as well as the Short Footnote and Bibliography templates as the traditional "exercise for the reader" <grin>. There are no line feeds in any of the details below, they are inserted by email. Finally I have tried this citation structure on a Second Site page which has Frames, and the link to FindAGrave works perfectly in FireFox using the target="_blank" parameter in the hyperlink. Source Definition ----------------- TITLE source element Find A Grave Memorials URL source element https://www.findagrave.com/memorial/ FF template [ITAL:][TITLE][:ITAL]<; [CD1]>[HID:][SS-HID:][:HID]<; [CD3]. > \<Memorial Number: <[URL]><[CD2]>\>[HID:][:SS-HID][SS:]. \<[HTML:]\<A target="_blank" HREF="[URL][CD2]"\>[CD3]\</A\>[:HTML]\>[:SS][:HID] Citation Detail --------------- CD1 (name and location of cemetery) CD2 (URL fragment after "memorial", usually just the memorial number) CD3 (Complete name of individual) So an example full CD is: Manor Presbyterian Church Cemetery, Cochranville, Chester County, Pennsylvania; Plot 104-D||40956381||Mary Cowan Boyd ================== The footnote in TMG that is produced is: Find A Grave Memorials; Manor Presbyterian Church Cemetery, Cochranville, Chester County, Pennsylvania; Plot 104-D; Mary Cowan Boyd. <Memorial Number: https://www.findagrave.com/memorial/40956381>. -------- The visible text of the footnote citation in Second Site that is produced is as follows where the individual's name is a hyperlink to the FindAGrave memorial: Find A Grave Memorials; Manor Presbyterian Church Cemetery, Cochranville, Chester County, Pennsylvania; Plot 104-D. <Mary Cowan Boyd> ====================== Hope this provides one idea of how to get Web references to appear in both TMG reports and Second Site. Michael

Regarding TMG's DNA Log and the fact that TMG does not provide any output method, I looked at the files and thought I'd mentions some of my findings. First, the DNA Log is basically a database consisting of DNA records created from one of the 16 provided Templates based on available tests of five different y-DNA testing labs and 2 provide Templates for 15 different mt-DNA testing labs. The newest of these Template files was created in 2013 with the earliest in 2007. These should serve for most cases, although there may be newer labs/tests that have been added and some may have changed (added more data). In such a case, one could possibly create their own Custom Templates based on how the others are created, but there may be some parameters that are not obvious. Each DNA Template is a ZIP file that includes two files. One file is an image file representing the individual lab providing the test data. The second file is a text file similar to a number of other files used by TMG (i.e., the project PJC file, the APP.INI, etc.). These files contain the parameters used to describe/select various available options. For the DNA file, some of the parameters are: Laboratory, TMG, Test, Markers, and Fields. When a Template is selected for use in the DNA Log, TMG creates a form based on the parameters described in the Template. Then the user enters the data in the provided form. The form is then stored in the database as a single reccord. To output data from the DNA Log, the project DNA database is accessed and the desired record(s) are extracted. Depending on the testing lab and the test, the data could be as few as about a dozen items of information to over a hundred items. Probably the best output would be through use of a spreadsheet. This could be done on a manual basis although there would be some work involved. For one or two persons (records) (especially of small data tests), this might be acceptable, but any more would need a program to extract the data from the record. The problem is that there is not really a standard format or style of output for DNA data. Then, there is the problem of trying to compare apples and oranges in that different labs give different data. Some data from different labs/tests will be the same and allow direct comparison, but other data may be different. Not sure anyone can use this information, here it is -- Lee

At 8/8/2019 09:29, Alexander Payne wrote >Has anyone created a Haplogroup tag to record mtDNA and if so what >would the sentence structure be? > >Pros and cons of a Haplogroup tag. >Did not want to use a flag because I want to include it in the journal report. First, a Flag cannot be used (at least, efficiently) to record Haplogroup information because Flag can only record single characters. I suppose that a user could define a Flag for each of several Haplogroups found in a project which might help in selecting persons in each Haplogroup for further processing, but even this might be inefficient. Still, it depends on the needs of a user. TMG's method for recording DNA data in through the DNA Log feature. I have used this only very little as I only have DNA test information from about two dozen persons in my project. This and the fact that there is presently no method in TMG to output the data from the DNA Log. I recall discussion here about third-parties providing that ability, but don;t know if that ever came about. The methods I have seen elsewhere have been somewhat based on a spreadsheet style output for comparing results of a group of persons. TMG's DNA Log provides for recording some 18 DNA Fingerprint Templates. Most of these include recording Predicted and Confirmed Haplogroups. Again, no method is provided for output of this data. This leaves the user wanting some type of output only the option of creating Custom Tags. One could use one of the Standard Tags (Anecdote, Note, etc.) to record the desired data in the TMG Memo field in such a way that it is output as desired. The same could be said for creating Custom Tags. The differenc is that Custom Tags would be created with desired Tag Sentence Structures as needed. Multiple Custom Tags could be created or one Tag could handle multiple uses via creating multiple Roles within the Tag. That is, a Custom Haplogroup Tag might be created with four Roles: -- Predicted y-DNA Haplogroup -- Confirmed y-DNA Haplogroup -- Predicted mt-DNA Haplogroup -- Confirmed mt-DNA Haplogroup The Tag Sentence Structure for the Predicted y-DNA Haplogroup Role might be: [SS] predicted y-DNA Haplogroup is [M] and if the predicted Haplogroup is "RL-48" then that (excluding the quotes) would be entered in the Tag Memo field. and the resulting sentence in a narrative report would be: Joe Smith's predicted y-DNA Haplogroup is RL-48. Pros and Cons? These would be different for each user and depend on their needs and desires. But, the above Custom Tag for Haplogroupd could be used with modifications for outputing most any DNA data. Lee

1. DNA tag (Alexander Payne) > > ---------------------------------------------------------------------- > > Date: Thu, 8 Aug 2019 13:29:23 +0000 > From: Alexander Payne <[email protected]> > Subject: [TMG] DNA tag > To: The Master Genealogist Rootsweb Email List <[email protected]> > Message-ID: <[email protected] > prd22.prod.outlook.com> > Content-Type: text/plain; charset="us-ascii" > > Has anyone created a Haplogroup tag to record mtDNA and if so what would the sentence structure be? > > Pros and cons of a Haplogroup tag. > Did not want to use a flag because I want to include it in the journal report. > > Alexander Payne > > ------------------------------ > Alexander, A friend tracks her DNA through new tags.  She copies the Note tag (go to Tools, etc.) and renames them mtDNA or Y-DNA and then uses the format  [:CR:] <[P].> <M.>[:CR:]  I am not sure exactly what she puts in the sentence format, but you could work out what you want to need and add that.  Anyway, it works well for her.

John I got to my computer first thing this morning and made your suggested FAG website address: \<a target="_blank" href="https://www.findagrave.com/memorial/[CD5]">...</a> I still get the Content Blocked error message on the re-built site. Because I am unwilling to change my frame style, I guess the thing to do is to forget about providing a link to a grave site. Even had your fix worked, I suspect FAG would close this loop hole. Because I cannot get the link to work I can't tell if the issue for FAG is that not as many adds are displayed once the content is displayed via a link or if it's for some other reason. Thanks for trying to fix this, Toby

At 8/8/2019 21:54, John Cardinal wrote >In my original example, I used https, and that biased what I read in your >example. Also, I discovered a change I made in my development version of SS >where there is new code that checks the https protocol, and that was a hint >that you were seeing different behavior because that change is not in the >public version. > >Are you using a test TMG project? It is basically my main project from which I copied one person to a new data set. The main data set is disabled for these tests and I make sure that I select the test data set for SecondSite builds. Lee

From: Lee Hoffman wrote: > I wrote: > > Hmm. Change the URL in the footnote to use "http:" rather than "https:" and > > let me know if that changes anything. > > Huh? I don't have "https:" in the URL. Lee, Sorry, I thought you had: href="https://www.findagrave.com/... But evidently you have href="http://www.findagrave.com/... In my original example, I used https, and that biased what I read in your example. Also, I discovered a change I made in my development version of SS where there is new code that checks the https protocol, and that was a hint that you were seeing different behavior because that change is not in the public version. Are you using a test TMG project? John

At 8/8/2019 18:51, John Cardinal wrote >In your test, did you make sure the HTML < and > characters were escaped? The Source Template was: [ITAL:][TITLE][:ITAL]<; Memorial: \<a href="http://www.findagrave.com/memorial/[CD3]"\>[CD3]\</a\>>. I added the line break here again after pasting (only reason is to show the margin offset here as the e-mail program already did it). >You asked: > > It does not look like the Citation Detail (#3) is being > > picked up by SecondSite in either of the methods. Any > > idea why? > >I don't see that behavior. > >Hmm. Change the URL in the footnote to use "http:" rather than "https:" and >let me know if that changes anything. Huh? I don't have "https:" in the URL. Any "http:" URL for Fins-A-Grave entered in a browser from any source (copy/paste or clicked) results in either the browser (Firsfox in my tests) or Find-A-Grave returning the page showing the "https:" URL. Just out of curiosity, I changed the URL to include the "https:" rather than "http:" and got the "s" in the output which was otherwise unchanged from what I reported earlier. Lee

At 8/8/2019 18:27, John Cardinal wrote >Did you test without a linebreak in the source template? I only added the line breaks as I pasted the results into the message. Lee

Toby, You were right to suspect the framed site. I converted a test site (local only) to a Side-by-Side site, and I got this error when using a valid Find-a-Grave link: "Blocked by Content Security Policy. An error occurred during a connection to www.findagrave.com. Firefox prevented this page from loading in this way because the page has a content security policy that disallows it." I got a similar error when using Chrome, though the message was somewhat hidden: "Refused to display 'https://www.findagrave.com/memorial/123456' in a frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors https://adm.findagrave.com"." The Chrome message is more hidden, but it identifies the cause: "frame-ancestors". The "ancestors" part has nothing to do with genealogy. It indicates that the Find-A-Grave page must be the top-most, it can't have a frame as an ancestor in the browser's window hierarchy. Evidently, FindAGrave.com objects to their site being loaded under a frame. So, if you use Side-by-Side, you'll get this error even if you use a valid URL. You might find that using a different URL works, but I suspect that hole won't stay open for long. There is one escape hatch: if you add target="_blank" to the HTML, that will avoid the content policy issue by opening the Find-A-Grave URL in a new window/tab: <a target="_blank" href="https://www.findagrave.com/memorial/...">...</a> John

I asked: > Lee, > > Did you test without a linebreak in the source template? Lee, Nevermind. That doesn't matter. In your test, did you make sure the HTML < and > characters were escaped? You asked: > It does not look like the Citation Detail (#3) is being > picked up by SecondSite in either of the methods. Any > idea why? I don't see that behavior. Hmm. Change the URL in the footnote to use "http:" rather than "https:" and let me know if that changes anything. Thanks. John

I went to your site. Yes, it works. But, your site has consists of a single "frame". Mine consists of a side by side style. If I understood the explanation I found on a software developer message board, some sites will not load properly if the load request comes from a site with more than one frame to a site having only one frame. I do not understand these issues, but I did right click on the error message to inspect the html element. Alas, my understanding of html coding is insufficient to understand what I saw. Would somebody who also uses a side by side style verify if the FAG website address works for them? My site has no problem with direct website links from sources such as FHL online records. Toby Sent from my iPad > On Aug 8, 2019, at 3:23 PM, John Cardinal <[email protected]> wrote: > > Toby, > > Go to: https://bezansons.com/g1/p1361.htm#i27208 > > Citation number 2 for Melissa Gayle Barkhouse is a Find A Grave citation > using the method I described here earlier, including the simplified URL. It > works for me in Chrome and Firefox. That page was created by Second Site. > > John > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/[email protected] > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

Lee, Did you test without a linebreak in the source template? John

At 8/8/2019 16:46, John Cardinal wrote >Regarding this construct (or similar) in a TMG footnote template: > > <; Memorial: \<a href="https://.../[CD2]"\>[CD2]\</a\>> I tried this in a test project and the result is that the Preview shows: Find-A-Grave Web Site<; Memoria: <a href="http://www.findagrave.com/memorial/[CD3]">[CD3]</a>>. I did a line break after the "<a ". The Journal report shows: Find-A-Grave Web Site<; Memoria: a href="http://www.findagrave.com/memorial/40956381"40956381</a>>. I placed the line break in the same place. In Second Site, the Citation is: 12. [<file:///D:/LHH/Second%20Site%20Test/NewTest-o/s1.htm#s2588>S2588] Find A Grave Plot 104-D The Source Page for the Citation gives: [S2588] Find-A-Grave Web Site. Note that this loses the memorial number. =============== Another similar entry uses the Source Template: [ITAL:][TITLE][:ITAL]; [URL]memorial/[CD3]. with the Preview: Find-A-Grave Web Site; http://www.findagrave.com/memorial/[CD3]. The Journal entry is: Find-A-Grave Web Site; http://www.findagrave.com/memorial/40956381. The Second Site Citation is: 13. [<file:///D:/LHH/Second%20Site%20Test/NewTest-o/s1.htm#s4046>S4046] Find A Grave Plot 104-D. and the Source Page entry is: [S4046] Find-A-Grave Web Site; <http://www.findagrave.com/memorial/unknown>http://www.findagrave.com/memorial/unknown * cd3. I did a line break after the semi-colon. I entered the asterisk in place of the symbol pointer to the actual web page which, of course, results in a 404 error. It does not look like the Citation Detail (#3) is being picked up by SecondSite in either of the methods. Any idea why? Lee

Further to my prior post on this topic. I experimented to see if there was some way to include HTML for a link in a source template when the output should be conditional based on the presence or absence of a CD part. I succeeded, but it involves a hack and some unreasonable rules for data entry and so I am going to stick with my original method. I rarely use TMG reports for output and so I don't care that my original method doesn’t work in TMG because of a bug. Here is some output copied from a TMG Descendant Journal report. I used Endnotes with "Unique" unchecked, and I also tested Footnotes with the same result. Various Contributors, "Find A Grave," online http://www.findagrave.com, Melissa Gayle Barkhouse, Anglican Cemetery, Dalhousie East, Nova Scotia ; Memorial Number: <a href="https://www.findagrave.com/memorial/114989516">114989516</a>. There were no linebreaks in the actual output. I added linebreaks in this message at convenient places to try to avoid unpredictable linebreaks introduced by email clients. There is an unwanted space between "Nova Scotia" and ";". Onb a quick glance, I don';t see what caused that and I didn't investigate further. The key ingredient of this method is a trick to add the HTML "<" and ">" characters. If you enter "#LT#" in a source template, TMG will output "<". If you enter "#GT#" in a source template, TMG will output ">". TMG has not documented the "#LT#" and "#GT#" sequences, so use at your own peril. I discovered them while hacking around. "#LT#" and "#GT#" will not work in any of my programs. Also, I had to make sure that the [CD2] value did not include any spaces. So, for example, a CD of "part one || 123456" would NOT work because of the space after the "||" and before the "123456". When I changed the CD to "part one ||123456", the HREF= value was correct in the Journal report output. BUT... 1 - A HTML link in a Journal report won't work anyway. 2 - I don't want to worry about spaces before or after the "||" characters. That's fragile. (I typically use "part one || 123456", and my programs trim the leading and trailing spaces.) 3 - The "#LT#" and "#GT#" clutter the source footnote template, and they don't work in my programs. So, I'm going to continue to use my original method because it produces exactly the output I want in Second Site, GedSite, and Gedcom Publisher, and those are my primary output vehicles. John

Michael, I created a new thread because the discussion of the incorrect behavior in TMG is not related to the prior subject, "Check of All Online Source Web Addresses". Regarding this construct (or similar) in a TMG footnote template: <; Memorial: \<a href="https://.../[CD2]"\>[CD2]\</a\>> There are no nested conditional brackets in that expression. The "\" character is used to escape the "<" and ">" characters that are part of the HTML. Only the outermost < and > characters (one each) are conditional expression brackets. (I elided the full URL to try and avoid wrapping that template when it is sent through email. The actual contents of the URL don't matter much as long as there are no special characters in it.) There are two references to the same variable ([CD2]) in that expression. If one is empty, and if the universe does not turn inside out, the other will be empty, too. And, of course, the opposite is true. The footnote works in the preview when editing a tag citation in TMG. It also appears to work when previewing from the Source Definition window, but in that case, there is no CD in scope so the "CD2" value is empty and the Source Definition version of the Preview feature shows "[CD2]" as a literal and makes other adjustments to cope with that. HOWEVER, when I use a Narrative Preview with sources, I get similar results to what you and Lee reported. Evidently, TMG has a bug where it does not properly implement the escape character before the < and > characters when processing source footnote templates. The bug does not apply to the preview feature but does apply to citation output in printed reports. I rarely use TMG printed reports and that's why I didn't notice the bug. SS supports the escape character and produces the expected output. As a result of this bug, there may not be a way to reliably include HTML in a Source Footnote Template when the HTML is inside a conditional expression. The [HTML:] and [:HTML] printer codes won't help because they don't do much. As far as I can tell, they have some impact on newline handling but I've never bothered to investigate further and I don't believe the rules are documented. I am confident that the [HTML:] and [:HTML] codes do not switch the meaning of the < and > characters with respect to conditional expression handling so they aren't a factor in this matter. John

Toby, Go to: https://bezansons.com/g1/p1361.htm#i27208 Citation number 2 for Melissa Gayle Barkhouse is a Find A Grave citation using the method I described here earlier, including the simplified URL. It works for me in Chrome and Firefox. That page was created by Second Site. John

At 8/8/2019 13:24, Mark (LI) wrote >Thank you Lee for your suggestion. >I have tried it, and greatly simplified the full >footnote format to (copy & pasted from TMG): > >[ITAL:][TITLE][:ITAL]; [URL]memorial/[CD3] > >[URL] is:Â https://www.findagrave.com/ >Tag Memo is:Â Plot 104-D|| ||40956381 > >footnote from Journal Report is: >9. Find-A-Grave web site; https://www.findagrave.com/memorial/unknown detail. > >Could there be something wrong with my installation of TMG ver 9.05? I doubt it. What does Preview show (in the Output Form Tab of the Source Definition Screen? I copy/pasted your Template above into TMG an Preview shows: Find-A-Grave Web Site; http://www.findagrave.com/memorial/[CD3]. This indicates that the Citation Detail is not known at preview time. But the Journal shows: 21. Find-A-Grave Web Site; http://www.findagrave.com/memorial/40956381. Again, note that my e-mail program recognizes a URL and converts it to a clickable version. The actual DOC or even HTML output from TMG is just plain text. As for SecondSite, I get the following: 13. [<file:///D:/LHH/Second%20Site%20Test/NewTest-o/s1.htm#s4046>S4046] Find A Grave Plot 104-D. Expanding [S4046], I get: [S4046] Find-A-Grave Web Site; <http://www.findagrave.com/memorial/unknown>http://www.findagrave.com/memorial/unknown * cd3. The asterisk replace the "go to" symbol that normally takes you to the page, but here take you to the 404 page indicating it can't find the page. John??? Lee