I've been hitting a wall on this module for some time now. I have an otherwise stable working postnuke site on 2003 web server/II6 with php4.3.4 and postnuke 0.726.
I've tried removing and re-installing several times using Gedview versions 2.6.,2.61, & 2.61.1.
I have created a separate database 'phpgedview' and a user with full rights to it and those creditials are listed in config.php.
Write permission assigned to index folder, config.php;authenticate.php.
I'm also attempting to use the postgedview-v2[1].zip files as it reads as if those are intended to make Gedview work under postnuke?
Write permissions also assigned to postgedview.php.
That error is not part of the postnuke code but does appear to have been caused by the $PGV_BASE_DIRECTORY setup. Unfortunately I have never set the postnuke system up on a windows environment so can't comment on how that path statement should be coded - but I am sure that someone on the list will be ablew to help - it may be night time though wherever that person may be :-) and so you may need to wait a short while for the fix
The postnuke code is to allow a logged in user on your postnuke system to be automatically logged in (or created and logged in) in gedview. You call it by creating a link like: http://carey.id.au/modules.php?op=modload&name=phpGedView&file=pgvindex
on your postnuke site and doing the various standard activation tasks in postnuke etc. Details are in the readme.
cheers
jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
But I'm now getting another error after I run the config page successfully:Fatal error:
Cannot redeclare print_submitter_info() (previously declared in c:inetpubmysite.commodulesphpgedview unctions_print.php:36) in c:inetpubmysite.commodulesphpgedview unctions_print.php on line 36
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you can send me your config.php file from your site I will take a look at it. I don't have a print_submitter_info() routine in my code so dont know how that is happening - it sort of looks like routines are being required twice. I assume you are using the very latest postgedview-v2.zip ?
Yes, I am using the v2 postgedview files, and yes both of those links when pointed at my site end in the same error condition.
I took the config.php-sample file and changed the dbuser;dbpassword;dbname fileds, added my path(which I think have closer to correct now) and changed your gedcom file name to my own which I placed in the index folder.
I'll send the file later when I get home.
Haven't had a chance yet today, but I want to go back and change my path variable again to match the case perfectly. Also when I do, I completely remove the module and start with a fresh copy of it from the zip. btw: thus far my database has not been populated by tables yet! and I'm positive of the user name/pw & rights to that database.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ok - if it happens the same on both links then it is an underlying problem - not a postnuke interface problem - going via the index.php doesn't load the postnuke interface - so we need to look at what may be wrong in the config
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, now with the path using the seemingly correct I've discovered that if I substitute the authentication_mysql.php for postgedview.php in config.php I find it all works!! Except that it requires a second login. What could that mean?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It shouldn't have had the postgedview.php in there - the sample shows authentication_mysql in there (and you would put authentication_index.php if you were using index files)- that would certainly cause an issue :-)
I think, from the emails that you may have simply uploaded my sample config after making some changes. The aim of the sample was to show you the sort of things to put in when you go through the initial congfiguration.
If your $CONFIGURED variable in config.php is set to false (default with distributed system) then the system will ask you to setup an admin user. You should do your initial configuration then using that new admin user. When the coinfig is all done then you should be able to set up other users (either via the postnuke direction or as part of the admin are).
Have you setup an admin user - and is it asking for that admin user login so that it can configure your tables etc ?
If not I suggest you re-upload that config.php with $CONFIGURED=false in there and try again
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, now the lights are coming on! I have been copying the files from the postnuke zip straight into the phpGedView module folder and renaming the original config.php to use your sample file, which I was tweaking.
So my whole problem has nothing to do with windows or IIS?? Guess not.
So once I copy back a fresh config file from the distro, I am able to open the config page and setup an admin user. From that point users from my site seem to flow right into GedView with their postnuke user names. I was thinking that the authentication file had to be postgedview.php since I thought I read that somewhere?
"Installation.
Create a phpGedView directory in your PostNuke modules directory
Upload all of your gedview code to this directory.
upload the pgvindex.php, post-config.php (make sure you have set your defaults) and postgedview.php
check your config.php so that the paths to image, index etc are similar to what I have done in my sample config here in the zip
- specifically make sure that $PGV_BASE_DIRECTORY is inserted and initialised similar to mine - should be there from the curent
releases - but may not.
make sure permissions on the index dir are correct etc"
This is the language which I was confused about. See now it doesn't say what I thought it said, which was that I should use postgedview.php as the authentication file.
Still I have one error. When I attempt to open the administrative icon for GedView from the postnuke adminstration page I get:
Fatal error: main(): Failed opening required '' (include_path='.;c:php4pear') in C:Inetpubmysite.commodulesphpGedViewadmin.php on line 29
Any thoughts on this?
Update:since drafting this message above I've re-installed once again using the correct path, and config from the original distro, and no problems! :-)
Now to just sitdown & learn howto....
Thanks so much for the help :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I should have a look at the readme and make it clearer.
yep - looks like I haven't put in a phpGedView admin module for under postnuke. I never needed to code it as there is nothing we need to do under postnuke for it - all the admin is done in phpGedView. But I should at least put in a module that redirects to the right place - will fix that soon
cheers
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thinking about this, as there is no need for an admin function for gedview under PostNuke - all admin should be done over in phpGedView by going into admin there - the easiest thing is to simply deactivate the module in postnuke admininstration. This wont affect any use - will simply remove the module name from the admin menu
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been hitting a wall on this module for some time now. I have an otherwise stable working postnuke site on 2003 web server/II6 with php4.3.4 and postnuke 0.726.
I've tried removing and re-installing several times using Gedview versions 2.6.,2.61, & 2.61.1.
I have created a separate database 'phpgedview' and a user with full rights to it and those creditials are listed in config.php.
Write permission assigned to index folder, config.php;authenticate.php.
I'm also attempting to use the postgedview-v2[1].zip files as it reads as if those are intended to make Gedview work under postnuke?
Write permissions also assigned to postgedview.php.
Module was initalized & actived.
Here's the problem: when I go to http://www.mysite.com/modules/phpgedview/
I get:
Parse error: parse error, unexpected T_STRING in C:\Inetpub\mysite.com\modules\phpgedview\config.php on line 40
Fatal error: main(): Failed opening required '' (include_path='.;c:\php4\pear') in C:\Inetpub\mysite.com\modules\phpgedview\index.php on line 41
The config.php was taken from the postnuke zip and modifed to point to
$PGV_BASE_DIRECTORY = "C:\Inetpub\mysite.com\modules\phpGedView\";
I think this last bit is my error. Can Gedview scripts read windows file paths?
Anybody?
That error is not part of the postnuke code but does appear to have been caused by the $PGV_BASE_DIRECTORY setup. Unfortunately I have never set the postnuke system up on a windows environment so can't comment on how that path statement should be coded - but I am sure that someone on the list will be ablew to help - it may be night time though wherever that person may be :-) and so you may need to wait a short while for the fix
The postnuke code is to allow a logged in user on your postnuke system to be automatically logged in (or created and logged in) in gedview. You call it by creating a link like:
http://carey.id.au/modules.php?op=modload&name=phpGedView&file=pgvindex
on your postnuke site and doing the various standard activation tasks in postnuke etc. Details are in the readme.
cheers
jim
I might have fixed my own problem with the help posted here:
http://perl.about.com/library/weekly/aa121901b.htm
But I'm now getting another error after I run the config page successfully:Fatal error:
Cannot redeclare print_submitter_info() (previously declared in c:inetpubmysite.commodulesphpgedview unctions_print.php:36) in c:inetpubmysite.commodulesphpgedview unctions_print.php on line 36
If you can send me your config.php file from your site I will take a look at it. I don't have a print_submitter_info() routine in my code so dont know how that is happening - it sort of looks like routines are being required twice. I assume you are using the very latest postgedview-v2.zip ?
I assume that this happens whether you go into phpGedView via the postnuke route - ie via a
http://carey.id.au/modules.php?op=modload&name=phpGedView&file=pgvindex type of entry (modified for your site)
or directly into phpgedview eg:
http://carey.id.au/modules/phpGedView/index.php (or wherever you have your index) - if it does thenthe issue wont be in the postnuke interface it will be in a config area.
I also asume that you used the sample config in the postnuke interface code simply as a model for what needed to go into yours
Jim
jim at carey.id.au
Instead of
$PGV_BASE_DIRECTORY = "C:Inetpubmysite.commodulesphpGedView";
You could also try:
$PGV_BASE_DIRECTORY = "C:/Inetpub/mysite.com/modules/phpGedView/";
PHP can usually work with either backslashes or forward slashes.
I don't know much about PostNuke though, so I don't know why it is trying to redeclare the functions.
Jim might have more ideas on that one.
--John
Yes, I am using the v2 postgedview files, and yes both of those links when pointed at my site end in the same error condition.
I took the config.php-sample file and changed the dbuser;dbpassword;dbname fileds, added my path(which I think have closer to correct now) and changed your gedcom file name to my own which I placed in the index folder.
I'll send the file later when I get home.
Haven't had a chance yet today, but I want to go back and change my path variable again to match the case perfectly. Also when I do, I completely remove the module and start with a fresh copy of it from the zip. btw: thus far my database has not been populated by tables yet! and I'm positive of the user name/pw & rights to that database.
ok - if it happens the same on both links then it is an underlying problem - not a postnuke interface problem - going via the index.php doesn't load the postnuke interface - so we need to look at what may be wrong in the config
Jim
Ok, now with the path using the seemingly correct I've discovered that if I substitute the authentication_mysql.php for postgedview.php in config.php I find it all works!! Except that it requires a second login. What could that mean?
It shouldn't have had the postgedview.php in there - the sample shows authentication_mysql in there (and you would put authentication_index.php if you were using index files)- that would certainly cause an issue :-)
I think, from the emails that you may have simply uploaded my sample config after making some changes. The aim of the sample was to show you the sort of things to put in when you go through the initial congfiguration.
If your $CONFIGURED variable in config.php is set to false (default with distributed system) then the system will ask you to setup an admin user. You should do your initial configuration then using that new admin user. When the coinfig is all done then you should be able to set up other users (either via the postnuke direction or as part of the admin are).
Have you setup an admin user - and is it asking for that admin user login so that it can configure your tables etc ?
If not I suggest you re-upload that config.php with $CONFIGURED=false in there and try again
Jim
Ok, now the lights are coming on! I have been copying the files from the postnuke zip straight into the phpGedView module folder and renaming the original config.php to use your sample file, which I was tweaking.
So my whole problem has nothing to do with windows or IIS?? Guess not.
So once I copy back a fresh config file from the distro, I am able to open the config page and setup an admin user. From that point users from my site seem to flow right into GedView with their postnuke user names. I was thinking that the authentication file had to be postgedview.php since I thought I read that somewhere?
"Installation.
Create a phpGedView directory in your PostNuke modules directory
Upload all of your gedview code to this directory.
upload the pgvindex.php, post-config.php (make sure you have set your defaults) and postgedview.php
check your config.php so that the paths to image, index etc are similar to what I have done in my sample config here in the zip
- specifically make sure that $PGV_BASE_DIRECTORY is inserted and initialised similar to mine - should be there from the curent
releases - but may not.
make sure permissions on the index dir are correct etc"
This is the language which I was confused about. See now it doesn't say what I thought it said, which was that I should use postgedview.php as the authentication file.
Still I have one error. When I attempt to open the administrative icon for GedView from the postnuke adminstration page I get:
Fatal error: main(): Failed opening required '' (include_path='.;c:php4pear') in C:Inetpubmysite.commodulesphpGedViewadmin.php on line 29
Any thoughts on this?
Update:since drafting this message above I've re-installed once again using the correct path, and config from the original distro, and no problems! :-)
Now to just sitdown & learn howto....
Thanks so much for the help :-)
excellent :-)
I should have a look at the readme and make it clearer.
yep - looks like I haven't put in a phpGedView admin module for under postnuke. I never needed to code it as there is nothing we need to do under postnuke for it - all the admin is done in phpGedView. But I should at least put in a module that redirects to the right place - will fix that soon
cheers
Jim
Thinking about this, as there is no need for an admin function for gedview under PostNuke - all admin should be done over in phpGedView by going into admin there - the easiest thing is to simply deactivate the module in postnuke admininstration. This wont affect any use - will simply remove the module name from the admin menu
Jim