Hello i think my question may relate to this. I recently tried to link two individuals from two GEDCOM files that i have on my server, one was the son of another.
I recieved this error
"Fatal error: Call to a member function canDisplayDetails() on a non-object in /var/www/html/phpgedview/includes/controllers/remotelink_ctrl.php on line 421"
Perhaps i have missed something or not done something?
i am running PhpGedView 4.2.1 svn
# $Id: changelog.txt 5070 2009-02-18 16:22:58Z fisharebest $
any help would be great....
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it *is* now working. I don't use it myself, so am not going to look at it again unless someone reports a problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-01-13
Greg, no, sorry its not quite working . The original error wally reported has certainly gone, but the link is not correctly formed.
I created a 'stub' record for my wife:
0 @I178@ INDI
1 FAMS @F71@
I then used "link remote person", filling in all the correct details:
Same as current
Local site
Person ID: I7
Gecom file: Firtree.ged
It created:
0 @I178@ INDI
1 FAMS @F71@
1 RFN S59:I7
1 SOUR @S59@
At first glance this looks correct, but no details appeared for the individual. I checked S59, and it is this:
0 @S59@ SOUR
1 TITL Akehurst, Weeks & Lowin Families
1 URL http://www.our-families.info/famtree/
1 _DBID weeks.ged
2 _BLOCK false
That is a different, previously established (years ago) link to a different gedcom on my server.
I then manually created a new source, and added the necessary tags:
0 @S27@ SOUR
1 TITL Firth Families
1 URL http://www.our-families.info/famtree/
1 _DBID Firtree.ged
2 _BLOCK false
and changed the INDI record to:
0 @I178@ INDI
1 FAMS @F71@
1 RFN S27:I7
1 SOUR @S27@
then everything works as expected.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no problems with either creating new links (sources) or using existing links.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-01-13
Greg
<<I have no problems with either creating new links (sources>> - thats what I said. No problem creating the link as you can see from the examples above - just that with 5 GEDCOMs, despite me typing the right one, it used something different - a pre-existing source - instead of creating a new one.
<<using existing links>> - thats never been a problem, and is what I meant with the description of manually creating and using the source.
Anyway, I'll try again, with a new INDI, and a GEDCOM that hasn't been linked before.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-01-13
OK, done that. I created an un-connected INDI with no data:
0 @I233@ INDI
1 NAME
1 SEX U
I then remote linked to a GEDCOM that has NEVER had a remote link made to it before. The result:
0 @I233@ INDI
1 NAME
1 SEX U
1 RFN S59:I1
1 SOUR @S59@
Its used the existing S59 again, just as it did in the earlier example.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nigel - I still can't reproduce this. When you say "NEVER", are you *absolutely* sure. If you have previously created a link with the same URL, PGV will ignore your instruction to create a new link, and re-use the old one.
In any case, I've rewritten the GUI code for this, to make it a little more friendly. e.g. if you get a password wrong, you won't have to type out all the other details again.
I've also had a tinker with the code that creates links using close relatives (i.e. link as husband/wife/etc.). It *seems* to do like I'd expect, so I've submitted it to SVN.
Maybe you could take another look with the latest code?
Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You'll have to read up on SVN. It's described on this site in several places (start with the menu bar of this forum, click 'more' if you have to and then it's under Code) including http://wiki.phpgedview.net/en/index.php?title=SVN but AFAICT there is not a simple set of directions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-01-15
Wally - I don't believe you will be able to try out the remote linking code alone. The changes between svn (PGV 4.2+) and 4.1.6 are far too great. You would have to move totally to 4.2, whcih, unless you have an opportunity to set up a separate test site, is a considerable leap. SVN is beta code - pretty stable most of the time, but no guarantees. Not generally recommended for live site use (although I do - but it takes a lot of work). The planned relese date is the end of this month though, so not long too wait.
Meanwhile I'll continue to talk with Greg offline, as his latest changes still don't work for me.
One question for you - do you aim to link between GEDCOM files on your server, or between GEDCOM files on different servers?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't find it difficult to update to HEAD twice a day.
One GUI command in my SVN client and one shell command to sync the website.
BUT, I wouldn't recommend it to someone who doesn't first know the basics of SVN, because once in a great while I have to select an older revision due to a bug.
Nigel, I'm interested in remote linking also. Considering geography, we probably have no relatives in common, but I'd be happy to create some link targets for you and/or some stubs for me to link from, if you want to collaborate on some testing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-01-16
I can now confirm that Greg has addressed the issues preventing this from working. It now works a little better than it used to, although there are still plenty of problems.
Wes, thanks for the offer - but truly 'remote' linking has never interested me. I only use this feature to locally link GEDCOMs on my own site. I've always suspected this is the most common use of the feature, but it alwasy gets over-looked when any work is done on the code.
If anyone has the interest and ability to spend a lot of time on this feature's code, here are what I see as the main current issues (in respect of LOCAL linking only):
1 - no bi-directional linking. The natural expectation when linking locally is to see the links in GEDCOM B from a person in GEDCOM a AND VICE-VERSA. The code currently does not do that. It's one-way only (because that was deemed to be the most likely scenario in truly 'remote' linking). If you go to GEDCOM B and create a mirror image link of the same people back to GEDCOM A, you start seeing tags like CENS etc doubled up at both ends - as if each GEDCOM is getting data from the link to the data in itself!
2 - some of the Charts don't work across the links - most importantly the Relationship chart.
3 - Media item links are not transferred at all, so you have to upload new copies for the current GEDCOM file.
I'm sure there are others (try searching the Bug trackers here for 'Remote Linking' - as I recall there are a lot of open ones still). I still think this is a great feature, but it does need more work, and always has.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've had a look at this, and fixed a number of bugs. However, fixing each one just reveals another.....
Currently, you can create the remote link, and then link two indis.
However, the relationships get screwed up, so you get families where you want indis, etc.
Still not usable, but a little closer. I'll have another look later.
I've spent all weekend working on the remote-linking functions, and think the basics are working now.
It's all seems to work as I'd expect, although I didn't try *that* hard to break it :-)
Hello i think my question may relate to this. I recently tried to link two individuals from two GEDCOM files that i have on my server, one was the son of another.
I recieved this error
"Fatal error: Call to a member function canDisplayDetails() on a non-object in /var/www/html/phpgedview/includes/controllers/remotelink_ctrl.php on line 421"
Perhaps i have missed something or not done something?
i am running PhpGedView 4.2.1 svn
# $Id: changelog.txt 5070 2009-02-18 16:22:58Z fisharebest $
any help would be great....
This would be great to get working...
I've got several GedComs that I want to link together.
I think it *is* now working. I don't use it myself, so am not going to look at it again unless someone reports a problem.
Greg, no, sorry its not quite working . The original error wally reported has certainly gone, but the link is not correctly formed.
I created a 'stub' record for my wife:
0 @I178@ INDI
1 FAMS @F71@
I then used "link remote person", filling in all the correct details:
Same as current
Local site
Person ID: I7
Gecom file: Firtree.ged
It created:
0 @I178@ INDI
1 FAMS @F71@
1 RFN S59:I7
1 SOUR @S59@
At first glance this looks correct, but no details appeared for the individual. I checked S59, and it is this:
0 @S59@ SOUR
1 TITL Akehurst, Weeks & Lowin Families
1 URL http://www.our-families.info/famtree/
1 _DBID weeks.ged
2 _BLOCK false
That is a different, previously established (years ago) link to a different gedcom on my server.
I then manually created a new source, and added the necessary tags:
0 @S27@ SOUR
1 TITL Firth Families
1 URL http://www.our-families.info/famtree/
1 _DBID Firtree.ged
2 _BLOCK false
and changed the INDI record to:
0 @I178@ INDI
1 FAMS @F71@
1 RFN S27:I7
1 SOUR @S27@
then everything works as expected.
I have no problems with either creating new links (sources) or using existing links.
Greg
<<I have no problems with either creating new links (sources>> - thats what I said. No problem creating the link as you can see from the examples above - just that with 5 GEDCOMs, despite me typing the right one, it used something different - a pre-existing source - instead of creating a new one.
<<using existing links>> - thats never been a problem, and is what I meant with the description of manually creating and using the source.
Anyway, I'll try again, with a new INDI, and a GEDCOM that hasn't been linked before.
OK, done that. I created an un-connected INDI with no data:
0 @I233@ INDI
1 NAME
1 SEX U
I then remote linked to a GEDCOM that has NEVER had a remote link made to it before. The result:
0 @I233@ INDI
1 NAME
1 SEX U
1 RFN S59:I1
1 SOUR @S59@
Its used the existing S59 again, just as it did in the earlier example.
Nigel - I still can't reproduce this. When you say "NEVER", are you *absolutely* sure. If you have previously created a link with the same URL, PGV will ignore your instruction to create a new link, and re-use the old one.
In any case, I've rewritten the GUI code for this, to make it a little more friendly. e.g. if you get a password wrong, you won't have to type out all the other details again.
I've also had a tinker with the code that creates links using close relatives (i.e. link as husband/wife/etc.). It *seems* to do like I'd expect, so I've submitted it to SVN.
Maybe you could take another look with the latest code?
Greg
Sorry Newb question here.
Are there directions that show me how to download the new code and try it out? I've got backup of my site so I can revert if I need to.
Hi Wally,
You'll have to read up on SVN. It's described on this site in several places (start with the menu bar of this forum, click 'more' if you have to and then it's under Code) including http://wiki.phpgedview.net/en/index.php?title=SVN but AFAICT there is not a simple set of directions.
Wally - I don't believe you will be able to try out the remote linking code alone. The changes between svn (PGV 4.2+) and 4.1.6 are far too great. You would have to move totally to 4.2, whcih, unless you have an opportunity to set up a separate test site, is a considerable leap. SVN is beta code - pretty stable most of the time, but no guarantees. Not generally recommended for live site use (although I do - but it takes a lot of work). The planned relese date is the end of this month though, so not long too wait.
Meanwhile I'll continue to talk with Greg offline, as his latest changes still don't work for me.
One question for you - do you aim to link between GEDCOM files on your server, or between GEDCOM files on different servers?
I don't find it difficult to update to HEAD twice a day.
One GUI command in my SVN client and one shell command to sync the website.
BUT, I wouldn't recommend it to someone who doesn't first know the basics of SVN, because once in a great while I have to select an older revision due to a bug.
Nigel, I'm interested in remote linking also. Considering geography, we probably have no relatives in common, but I'd be happy to create some link targets for you and/or some stubs for me to link from, if you want to collaborate on some testing.
I can now confirm that Greg has addressed the issues preventing this from working. It now works a little better than it used to, although there are still plenty of problems.
Wes, thanks for the offer - but truly 'remote' linking has never interested me. I only use this feature to locally link GEDCOMs on my own site. I've always suspected this is the most common use of the feature, but it alwasy gets over-looked when any work is done on the code.
If anyone has the interest and ability to spend a lot of time on this feature's code, here are what I see as the main current issues (in respect of LOCAL linking only):
1 - no bi-directional linking. The natural expectation when linking locally is to see the links in GEDCOM B from a person in GEDCOM a AND VICE-VERSA. The code currently does not do that. It's one-way only (because that was deemed to be the most likely scenario in truly 'remote' linking). If you go to GEDCOM B and create a mirror image link of the same people back to GEDCOM A, you start seeing tags like CENS etc doubled up at both ends - as if each GEDCOM is getting data from the link to the data in itself!
2 - some of the Charts don't work across the links - most importantly the Relationship chart.
3 - Media item links are not transferred at all, so you have to upload new copies for the current GEDCOM file.
I'm sure there are others (try searching the Bug trackers here for 'Remote Linking' - as I recall there are a lot of open ones still). I still think this is a great feature, but it does need more work, and always has.