Hi.
Great job John, I like the way you think (and code hehe). I run "www.usgenealogy.net" and would love to use this as a service at my site. I'm testing it now and ppl are gaga over the nice presentation. We run Geneweb also, which with a php hack, can output GEDCOM's which we wish to use for this. Our problem with full throttle implementation is we require the use of "Mulitple Gedcoms". That, is , some persons have several family sets they use. I can see an easy way to pick and choose on the front-end, plug that into $GEDCOM. Am having some problems with the /index folder. Figured to use like, "/$GEDCOM1" "/$GEDCOM2" but that isn't working as I'd of liked. Perhaps a structure like,
/index
/Gedcom1
/Gedcom2
/Gedcom3
I dunno. Have you persued this avenue at all? If so, love to type/type to you to discuss this future feature idea.
Thanks and keep up the good work!
cyber830
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This functionality is available in the MySQL version of phpGedView. The MySQL version is much faster and doesn't require as much system resources. It is probably a much better option for you in offering phpGedView to your clients and allowing them to use multiple gedcoms.
However, this requires that your sight have MySQL. If the MySQL version won't work for you, and you need this functionality, then I'd be happy to work with you to make it work. It sounds like you are really close. Probably, what I would do is add a prefix to the index files, and set up an array in the config.php file. Something like this:
$gedcomsite = array();
$gedcomsite["surname1.ged"]["index_folder"]="./index/";
$gedcomsite["surname1.ged"]["index_prefix"]="gd1_";
$gedcomsite["surname2.ged"]["index_folder"]="./index/";
$gedcomsite["surname2.ged"]["index_prefix"]="gd2_";
Then in session.php add the following line:
$INDEX_DIRECTORY = $gedcomsite[$GEDCOM]["index_folder"].$gedcomsite[$GEDCOM]["index_prefix"];
Then use the $GEDCOM variable to say which gedcom you want to look at.
Another option is to just have a different phpGedView folder for each gedcom and just copy the config.php, header.html. footer.html, and style.css files so that they are all the same.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-03-11
Cool, thanks John. I have MySql on another server which doesn't have member info on it. The thought of passing member info, plus requests to it seem a bit much. Kinda like to keep such items "in house" (off my network) as much as possible. Your suggestion # 1 makes sense. I'll give that a spin and advise. # 2 was considered as your proggie doesn't have a big footprint. Will continue the experimenting as time allows. Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has this lead to a solution to the problem of multiple GEDCOMs without mySQL. If so i (an absolute nitwit as far as PHP is considered) do am interested in how to implement it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
Great job John, I like the way you think (and code hehe). I run "www.usgenealogy.net" and would love to use this as a service at my site. I'm testing it now and ppl are gaga over the nice presentation. We run Geneweb also, which with a php hack, can output GEDCOM's which we wish to use for this. Our problem with full throttle implementation is we require the use of "Mulitple Gedcoms". That, is , some persons have several family sets they use. I can see an easy way to pick and choose on the front-end, plug that into $GEDCOM. Am having some problems with the /index folder. Figured to use like, "/$GEDCOM1" "/$GEDCOM2" but that isn't working as I'd of liked. Perhaps a structure like,
/index
/Gedcom1
/Gedcom2
/Gedcom3
I dunno. Have you persued this avenue at all? If so, love to type/type to you to discuss this future feature idea.
Thanks and keep up the good work!
cyber830
Hi cyber830,
This functionality is available in the MySQL version of phpGedView. The MySQL version is much faster and doesn't require as much system resources. It is probably a much better option for you in offering phpGedView to your clients and allowing them to use multiple gedcoms.
However, this requires that your sight have MySQL. If the MySQL version won't work for you, and you need this functionality, then I'd be happy to work with you to make it work. It sounds like you are really close. Probably, what I would do is add a prefix to the index files, and set up an array in the config.php file. Something like this:
$gedcomsite = array();
$gedcomsite["surname1.ged"]["index_folder"]="./index/";
$gedcomsite["surname1.ged"]["index_prefix"]="gd1_";
$gedcomsite["surname2.ged"]["index_folder"]="./index/";
$gedcomsite["surname2.ged"]["index_prefix"]="gd2_";
Then in session.php add the following line:
$INDEX_DIRECTORY = $gedcomsite[$GEDCOM]["index_folder"].$gedcomsite[$GEDCOM]["index_prefix"];
Then use the $GEDCOM variable to say which gedcom you want to look at.
Another option is to just have a different phpGedView folder for each gedcom and just copy the config.php, header.html. footer.html, and style.css files so that they are all the same.
--John
Cool, thanks John. I have MySql on another server which doesn't have member info on it. The thought of passing member info, plus requests to it seem a bit much. Kinda like to keep such items "in house" (off my network) as much as possible. Your suggestion # 1 makes sense. I'll give that a spin and advise. # 2 was considered as your proggie doesn't have a big footprint. Will continue the experimenting as time allows. Thanks again.
Has this lead to a solution to the problem of multiple GEDCOMs without mySQL. If so i (an absolute nitwit as far as PHP is considered) do am interested in how to implement it.