|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 10:40 PM
Posts: 1,579,
Visits: 31,433
|
Happy New Year to you all and here's hoping somebody can make us happy here. I created a new file and created a local file which is fine. I then created a dummy file and saved it online to GenoPro. I then password protected it. I then overwrote this file to create an online version. Apart from the odd missing photo there were no error messages. Looking at the online report today it contains the message This genealogy report was generated by GenoPro® version 3.1.0.1 on 2024.1.1 using skin template (2023.02.23) with code base 2023.02.23.At the foot it saysCopyright © 2011 GenoPro Inc. All rights reserved.I have attached a screen shot of this report and have a copy of the message.Any suggestions for a solution?
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 6:04 AM
Posts: 3,378,
Visits: 25,908
|
I can only see two reasons for you seeing an out of date version of the Narrative Report. Either you are seeing a cached copy of an old report or that you have inadvertently used an old version of the skin when generating the report. Clearing the browser cache will eliminate the first possibility. The Message Log when generating the report will show the code base version used, e.g. for the current release: Using 'Common\Code' scripts version 2023.11.29 so checking this should eliminate the second possibility. Otherwise it remains a mystery 
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 10:40 PM
Posts: 1,579,
Visits: 31,433
|
The jpg shows the report is of the new file. It also shows that it reckons that the correct skin was used but it has that odd copyright 2011. The message log says Cloning document josh-hannah... Opening configuration file Config.xml for skin '\{EN}Narrative Report\* (2023.02.23)'... Loading Dictionary.xml... [0.00] Processing template 'bootstrap.vbs'... [3.21] Processing template 'Code\init.htm'... Using 'Common\Code' scripts version 2023.02.23 Report Language code 'EN' Dictionary version '2020.03.13' The only specific things to this problem is that I had several other files in different windows and the file was on my PC but I wrote the report from this laptop. I will save the file locally, close everything else and try again and report progress (hopefully positive).
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Yesterday @ 6:04 AM
Posts: 3,378,
Visits: 25,908
|
Ok, I got hold of the 'wrong end of the stick' when I read your post. When you said 'online report has old format' I wrongly assumed that your issue was it was showing a report from skins version 2023.02.23 instead of the latest version 2023.11.29
But now I see you are referring to the text Copyright 2011. This is a red herring as this text is hardcoded in the report skins script and hasn't been updated over the years. I think I should remove the date from this message. But the other issue is that you are displaying a page from the report, i.e. home.htm, but outside the frameset that is normally the case. The report is normally displayed as a multi-frame page or 'frameset' that is defined in the start page 'default.htm'. I do not understand how you arrived at that page. The script should normally detect that the page is outside the frameset and then redirect to default.htm with a request to open at the desired page. This obviously hasn't worked here and instead it has appended the message about a frameset and the erroneous copyright date. |
|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 10:40 PM
Posts: 1,579,
Visits: 31,433
|
I had not noticed that I was not using the latest skins - although that should have not have caused the odd frameset display - which did not happen locally. However I have now used the latest report set and the problem has not repeated itself.
|