|
By Przytula - Sunday, August 30, 2015
|
|
whenever you generate a report I get strange messages as in screen, is this a local error or can this be corrected ? best regards, Guy Przytula
|
|
By maru-san - Monday, August 31, 2015
|
I am receiving the same message whenever I run the narrative report and whenever I run the Gedcom Export.
Any comments?
|
|
By genome - Tuesday, September 1, 2015
|
I am quite certain that the messages are not coming from the Report skin template but from GenoPro itself.
Have you tried looking at say Families under Table Layout and see if you have for example a custom tag 'Marriage.religious.date' present and if so is a value set on any record?
I also find the messages such as Try Family.Marriages[0].Date a little odd because I thought 'Marriages' had been replaced with 'Unions' (although 'Unions' entries still point to 'Marriage' records).
|
|
By maru-san - Tuesday, September 1, 2015
|
|
No such kind of custom tag in my files.
|
|
By IainTait - Sunday, September 13, 2015
|
I have had the similar problem .
When I updated to 2.9.0.6 recently, I had to remove all the unwanted tags manually as I couldn't find them in the xml as I did in previous versions.
This done, I personalised the 2015 Narrative Skin with more difficulty than the older versions, and then generated my trees.
I then updated to GenoPro 3.0.0.2 and started trying the Problem Spotter which I found very usefull.
Having corrected one small tree I used my 2015 Skin to generate a new report with GenoPro 3 but got these tag errors even though I checked that the I had removed had not come back - very confusing!
Another thing, Even though I installed GenoPro 3 in a separate folder, I can't open GenoPro 2011 even when I click on the 2.9.0.6 ikon I still get GenoPro2016 opening
[2088.33] The tag 'Family.Marriage.religious.date' is no longer valid. Try 'Family.Marriages(0).Date'
[2088.35] The tag 'Family.Marriage.civil.date' is no longer valid. Try 'Family.Marriages(0).Date'
[2088.35] The tag 'Family.separation.date' is no longer valid. Try 'Family.Marriages(0).Divorce.Date'
[2088.35] The tag 'Family.Divorce.date' is no longer valid. Try 'Family.Marriages(0).Divorce.Date'
[2088.35] The tag 'Education.Start.Date' is no longer valid. Try 'Education.DateStart'
[2088.35] The tag 'Education.End.Date' is no longer valid. Try 'Education.DateEnd'
[2088.35] The tag 'Occupation.Start.Date' is no longer valid. Try 'Occupation.DateStart'
[2088.35] The tag 'Occupation.End.Date' is no longer valid. Try 'Occupation.DateEnd'
[2088.36] The tag 'Contact.Start.Date' is no longer valid. Try 'Contact.DateStart'
[2088.36] The tag 'Contact.End.Date' is no longer valid. Try 'Contact.DateEnd'
I've just generated the same Beath tree again but this time I didn't see any errors ! ?
|
|
By IainTait - Sunday, December 13, 2015
|
I have just tried to update my Beath tree again and got the same errors as before
[1298.73] The tag 'Family.Marriage.religious.date' is no longer valid. Try 'Family.Marriages(0).Date'
[1298.75] The tag 'Family.Marriage.civil.date' is no longer valid. Try 'Family.Marriages(0).Date'
[1298.75] The tag 'Family.separation.date' is no longer valid. Try 'Family.Marriages(0).Divorce.Date'
[1298.75] The tag 'Family.Divorce.date' is no longer valid. Try'Family.Marriages(0).Divorce.Date'
[1298.76] The tag 'Education.Start.Date' is no longer valid. Try 'Education.DateStart'
[1298.76] The tag 'Education.End.Date' is no longer valid. Try 'Education.DateEnd'
[1298.76] The tag 'Occupation.Start.Date' is no longer valid. Try 'Occupation.DateStart'
[1298.78] The tag 'Occupation.End.Date' is no longer valid. Try 'Occupation.DateEnd'
[1298.78] The tag 'Contact.Start.Date' is no longer valid. Try 'Contact.DateStart'
[1298.78] The tag 'Contact.End.Date' is no longer valid. Try 'Contact.DateEnd'
I have removed all the Custom Tags I don't need from the Gno files but can't find these Tags anywhere in the Gnos or even in the Skin files.
If I could find them I would delete them.
Please could you indicate to me which file contains references to these Tags.
|
|
By maru-san - Sunday, December 13, 2015
|
|
I am receiving these messages these days only when I am running low on memory(Look at the status bar). But nevertheless they should not be there in the first place!
|