* Project Specific Settings Greyed out
Project Specific Settings Greyed out
Hi,
I'm using AS 7.6.6 64 bit and have had the same issue as the post "not given option to save image to media folder" viewtopic.php?f=34&t=21261.
However when I try to reset, the option is greyed out? Thanks
Kev
I'm using AS 7.6.6 64 bit and have had the same issue as the post "not given option to save image to media folder" viewtopic.php?f=34&t=21261.
However when I try to reset, the option is greyed out? Thanks
Kev
Kev
- tatewise
- Megastar
- Posts: 27075
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Project Specific Settings Greyed out
I suspect you have not opened a Project but simply a standalone GEDCOM file called Full 20_6_20.ged
There are many features of Projects in AS and FH that are not available to a standalone GEDCOM.
There are many features of Projects in AS and FH that are not available to a standalone GEDCOM.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Project Specific Settings Greyed out
Hi Mike,
I've opened via File > Open FH Project > Select Project and selecting from the list, but it's still greyed out.
However, I have noticed that when I open the sample project and then mine again, via the path above, the option is still greyed out, and the "File > Recent Files" is populated with the ged files relating to the projects I have just opened, but "File > Recent Projects" isn't. So it looks like you might be right that I am opening the GEDCOM file and not the project.
I'm just confused as to why as I'm going via "Open Project".
AS is still working as expected and populating my project in FH though, just with the wrong media path, populating to D:\Downloads\ rather than Media\
Kev
I've opened via File > Open FH Project > Select Project and selecting from the list, but it's still greyed out.
However, I have noticed that when I open the sample project and then mine again, via the path above, the option is still greyed out, and the "File > Recent Files" is populated with the ged files relating to the projects I have just opened, but "File > Recent Projects" isn't. So it looks like you might be right that I am opening the GEDCOM file and not the project.
I'm just confused as to why as I'm going via "Open Project".
AS is still working as expected and populating my project in FH though, just with the wrong media path, populating to D:\Downloads\ rather than Media\
Kev
Kev
- tatewise
- Megastar
- Posts: 27075
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Project Specific Settings Greyed out
Clearly something is amiss!
If AS thinks a Project is open the very top border says Ancestral Sources v7.6.6: Project: <projectname>
Whereas if AS thinks a GEDCOM is open it says instead Ancestral Sources v7.6.6: <filename>.ged (as in your screenshot).
So despite using the File > Open FH Project... command you are actually opening GEDCOM files, but I cannot explain why.
If AS thinks a Project is open the very top border says Ancestral Sources v7.6.6: Project: <projectname>
Whereas if AS thinks a GEDCOM is open it says instead Ancestral Sources v7.6.6: <filename>.ged (as in your screenshot).
So despite using the File > Open FH Project... command you are actually opening GEDCOM files, but I cannot explain why.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Project Specific Settings Greyed out
Thanks Mike,
I've tried a few other scenarios and all come to the same end result.
When opening a project via "File > Open FH Project" AS does show "Ancestral Sources v7.6.6: [project name].ged" in the top bar.
Also the File menu also shows "Make Current File Default" which I think confirms that the GEDCOM is being opened and not the project.
Through the scenarios I ran using two different projects and the sample, the following were confirmed:
- The list of projects that appear in AS in the "File> Open FH Project" selection box match those in FH "File> Project Window"
- in AS, "File>Open FH Project>Browse" and selecting the [project name].fh_proj file has the same effect in that it opens the GEDCOM file and not the project
- using the "Ancestral Sources Data Entry" plugin in FH opens AS with the correct GEDCOM (not Project) and opens the correct screen (Census/Baptism etc)
Everything else works as expected in AS with my Census Template alterations still working correctly, and to be honest it's only that I noticed that the images are being linked to D:\Downloads and not Media\ in FH that alerted me to anything being wrong.
I haven't yet tried re-installing 7.6.6 as an in-situ upgrade. Would that be worth a try? I didn't want to do it immediately in case a root cause could be found.
Many Thanks for your help
I've tried a few other scenarios and all come to the same end result.
When opening a project via "File > Open FH Project" AS does show "Ancestral Sources v7.6.6: [project name].ged" in the top bar.
Also the File menu also shows "Make Current File Default" which I think confirms that the GEDCOM is being opened and not the project.
Through the scenarios I ran using two different projects and the sample, the following were confirmed:
- The list of projects that appear in AS in the "File> Open FH Project" selection box match those in FH "File> Project Window"
- in AS, "File>Open FH Project>Browse" and selecting the [project name].fh_proj file has the same effect in that it opens the GEDCOM file and not the project
- using the "Ancestral Sources Data Entry" plugin in FH opens AS with the correct GEDCOM (not Project) and opens the correct screen (Census/Baptism etc)
Everything else works as expected in AS with my Census Template alterations still working correctly, and to be honest it's only that I noticed that the images are being linked to D:\Downloads and not Media\ in FH that alerted me to anything being wrong.
I haven't yet tried re-installing 7.6.6 as an in-situ upgrade. Would that be worth a try? I didn't want to do it immediately in case a root cause could be found.
Many Thanks for your help
Kev
- tatewise
- Megastar
- Posts: 27075
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Project Specific Settings Greyed out
I think it may be best to let Nick see this thread before doing anything further.
As the author of AS he is best placed to know what may be going wrong.
As the author of AS he is best placed to know what may be going wrong.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
- johnmorrisoniom
- Megastar
- Posts: 882
- Joined: 18 Dec 2008 07:40
- Family Historian: V7
- Location: Isle of Man
Re: Project Specific Settings Greyed out
It should open the project, unless you had only opened a gedcom not a project, which would explain why the project options are greyed out.- using the "Ancestral Sources Data Entry" plugin in FH opens AS with the correct GEDCOM (not Project) and opens the correct screen (Census/Baptism etc)
- tatewise
- Megastar
- Posts: 27075
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Project Specific Settings Greyed out
John, if you check through the thread, Kev is doing all the correct things to open a Project that is a Project in FH, and the AS Project List says the same, but still only opens the GEDCOM file.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
- johnmorrisoniom
- Megastar
- Posts: 882
- Joined: 18 Dec 2008 07:40
- Family Historian: V7
- Location: Isle of Man
Re: Project Specific Settings Greyed out
Mike - I just noticed that he used your plugin to invoke AS, which will open with the PROJECT , IF a project is in use.
It is only opening a Gedcom, therefore the OP is NOT using a project
It is only opening a Gedcom, therefore the OP is NOT using a project
- tatewise
- Megastar
- Posts: 27075
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Project Specific Settings Greyed out
That is the problem. The OP is using a Project. Kev even tried the Family Historian Sample Project.
Even the AS File > Open FH Project... command Select Project, lists everything Kev tried as a Project.
( I've checked that AS only lists genuine FH Project folders. )
Something is broken in AS but it is best if Nick investigates.
Even the AS File > Open FH Project... command Select Project, lists everything Kev tried as a Project.
( I've checked that AS only lists genuine FH Project folders. )
Something is broken in AS but it is best if Nick investigates.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Project Specific Settings Greyed out
John, Mike
As far as I am aware I AM using a project in FH.
Opened via File>Project Window.
But after using the plug-in AS opens the .ged
As far as I am aware I AM using a project in FH.
Opened via File>Project Window.
But after using the plug-in AS opens the .ged
Kev
- NickWalker
- Megastar
- Posts: 2401
- Joined: 02 Jan 2004 17:39
- Family Historian: V7
- Location: Lancashire, UK
- Contact:
Re: Project Specific Settings Greyed out
When AS opens a GEDCOM file, for it to be treated as a project the following things need to be true
1) The file name extension is .ged
2) The GEDCOM file has to be in a folder with the same name as the file but with .fh_data on the end. So if your file is Full 20_6_20.ged then this needs to be in a folder called Full 20_6_20.fh_data
3) The name of the folder that the .fh_data folder is in has to have the same name (without the .fh_data) on the end. So in your case the Full 20_6_20.fh_data has to be in a folder called Full 20_6_20
I am puzzled though because very similar checks are carried out when AS lists the projects to choose from and you've said that it is shown as a project there but is being rejected as not being project when opened. I haven't managed to find a scenario where this would be the case but there must be one as it isn't working for you!
Can you double-check the 3 steps above, check there are no additional spaces, etc. in the file or folder names and assuming all looks OK can you email me via Nick AT ancestralsources DOT com and I'll send you a version of AS to run with some diagnostic testing built in.
Thanks
Nick
1) The file name extension is .ged
2) The GEDCOM file has to be in a folder with the same name as the file but with .fh_data on the end. So if your file is Full 20_6_20.ged then this needs to be in a folder called Full 20_6_20.fh_data
3) The name of the folder that the .fh_data folder is in has to have the same name (without the .fh_data) on the end. So in your case the Full 20_6_20.fh_data has to be in a folder called Full 20_6_20
I am puzzled though because very similar checks are carried out when AS lists the projects to choose from and you've said that it is shown as a project there but is being rejected as not being project when opened. I haven't managed to find a scenario where this would be the case but there must be one as it isn't working for you!
Can you double-check the 3 steps above, check there are no additional spaces, etc. in the file or folder names and assuming all looks OK can you email me via Nick AT ancestralsources DOT com and I'll send you a version of AS to run with some diagnostic testing built in.
Thanks
Nick
Re: Project Specific Settings Greyed out
Thanks Nick,
Just sent you an email confirming the three points listed are correct
Just sent you an email confirming the three points listed are correct
Kev
- NickWalker
- Megastar
- Posts: 2401
- Joined: 02 Jan 2004 17:39
- Family Historian: V7
- Location: Lancashire, UK
- Contact:
Re: Project Specific Settings Greyed out
Kev and I have now discovered the problem. A windows update in 2018 introduced a setting to allow a drive or folder to be marked as 'case sensitive' so e.g. a file called Project1 is not the same as a file called project1, This is a facility introduced for users of the Windows Subsystem for Linux (WSL) that allows software from the Linux OS to run on Windows. Although Kev hadn't turned the setting on, some encryption software he uses had done this. The routine in AS which detects if the GEDCOM file is part of a project was assuming that the file paths were case insensitive (the only option in Windows when this area of AS was developed) and this is what caused the problem for Kev. This will be fixed in the next version of AS.
Nick
Nick