I'm using Upgrade .04a for the upgrade of my test site. Upon launching the script on first run, I saw the message at the bottom of the display.
Warning: chdir(): No such file or directory (errno 2) in /home/jtrainer/public_html/genealogy/ged_indx/upgradev4a.php on line 99
Please fill in both fields.
Ok fine, not an issue. However after filling in both fields, and selecting the Includes, I get the following errors. (Upgrade script renamed and in the PGV directory on the host.)
Warning: opendir(D:\phpGedView\): failed to open dir: No such file or directory in /home/jtrainer/public_html/genealogy/ged_indx/upgradev4a.php on line 322
Warning: opendir(D:\phpGedView\images/): failed to open dir: No such file or directory in /home/jtrainer/public_html/genealogy/ged_indx/upgradev4a.php on line 322
Performing the upgrade from a WinXP client. Note the first error the final slash is the correct \ case per this OS. The second error as all subsequent errors altered the slash to a / which is correct for my host. The current version on this site is 2.61b5.
The paths are correct, so what might I have missed.
Thanks
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-12-05
Hey John,
Thanks for running the upgrade script, more testing is needed ;) Of course it runs fine on my installation :)
Back to the real issue. The text "Please fill in both fields" is always displayed. This is not an error but by design.
Slash issue:
I added the forward slash as this is recognized by both *nix and windows machines. Windows has no trouble with mixed slashes in its path.
Does it copy any files, or none at all? The errors indicate that the folder d:\phpGedView does not exist, hence that d:\phpGedView\images does not exist either.
This path works right?
regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As for the other errors, I always avoided the mixed slashes, I thought it caused errors. Now I can do less back spacing.
Yes the path is 100% correct. I orginally tried to get the files from a folder off my desktop, but wasn't sure if the spaces caused issues. So I coppied my expanded pgv folder to the root of d:.
No files ever copy.
Thanks
john
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-12-05
John,
I do want to change the message but haven't gotten round to it yet. ;)
I am at work now, so not able to testdrive it ;)
Just a hunch, in the first field you have to fill in the location of your current phpgedview installation. In the second field the location of the new phpgedview files.
I.e.
Field 1: d:\phpgedview <-- this is your current installation
Field 2: d:\upgrade <-- the location of the new phpgedview files
Am I correct you have set it up in this manner?
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry I too am at work. (Opps hope the boss isn't watching)
No my paths are different. First my site is housed on a *nix server. So my path (off my head) is /home/jtrainer/public_html/genealogy/gedview
and my upgrade source files are stored in d:\phpgedview
So for my first path, was that to be an ftp link, http, etc, what format do you expect my string to be in?
Thanks
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-12-05
Hey John,
The good thing is you run a *nix system, as I just have a fw based on a *nix system. As it is pnp it shows my knowledge of *nix (very unfortunate I don't have more knowledge)
I tried copying files with the script from my XP machine to the *nix machine. It went flawless. I specified the first path as \\servername\folder\folder2 etc. In this case it had to be backspaced because of the network connection.
This is a line from the log:
\\webserver\website\virtual\themes/ocean/style.css copied successfully.
So your first path should include the FQDN of your *nix machine.
A new version of the upgrade util has been uploaded to the patches section. It has quite a few improvements. It should produce a lot less errors.
Let me know how you get along.
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it's best to copy John's upload routine from the upload media, and upload gedcom functions. You could provide an upgrade conf file, that one could alter default paths. Using these functions, you could upload the files easier. I see no reason why we shold have to include a target path. The script should be run from the pgv directory.
I have no issue with John's functions, the files all upload fine. I think by having the users select the target directory will be a troublesome support issue. With some having user loacl to the site, and others without shell access etc... I think John's functions will be fine. Perhaps a second file, or within the conf file, you could have a list of all included files that need to be uploaded.
BTW, I like the new screen layout. Much nicer display.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-12-08
The other John,
Youa re just ahead of me ;) Yesterday I already decided to remove the destination path, as I agree with you that it is already known where the files are supposed to be going.
Yes, the upgrade script is maturing. I noticed that it can run perfectly fine on 1 machine and totally not on another (eh Kurt ;)).
Tonight, I will upload the new version which will exclude the input of the destination path. I guess by now, the issue mentioned in 0.4a should be gone also.
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First, John thanks for 2.61.
I'm using Upgrade .04a for the upgrade of my test site. Upon launching the script on first run, I saw the message at the bottom of the display.
Warning: chdir(): No such file or directory (errno 2) in /home/jtrainer/public_html/genealogy/ged_indx/upgradev4a.php on line 99
Please fill in both fields.
Ok fine, not an issue. However after filling in both fields, and selecting the Includes, I get the following errors. (Upgrade script renamed and in the PGV directory on the host.)
Warning: opendir(D:\phpGedView\): failed to open dir: No such file or directory in /home/jtrainer/public_html/genealogy/ged_indx/upgradev4a.php on line 322
Warning: opendir(D:\phpGedView\images/): failed to open dir: No such file or directory in /home/jtrainer/public_html/genealogy/ged_indx/upgradev4a.php on line 322
Performing the upgrade from a WinXP client. Note the first error the final slash is the correct \ case per this OS. The second error as all subsequent errors altered the slash to a / which is correct for my host. The current version on this site is 2.61b5.
The paths are correct, so what might I have missed.
Thanks
John
Hey John,
Thanks for running the upgrade script, more testing is needed ;) Of course it runs fine on my installation :)
Back to the real issue. The text "Please fill in both fields" is always displayed. This is not an error but by design.
Slash issue:
I added the forward slash as this is recognized by both *nix and windows machines. Windows has no trouble with mixed slashes in its path.
Does it copy any files, or none at all? The errors indicate that the folder d:\phpGedView does not exist, hence that d:\phpGedView\images does not exist either.
This path works right?
regards,
Roland
Roland,
Ok, I'll accept the designed message.
As for the other errors, I always avoided the mixed slashes, I thought it caused errors. Now I can do less back spacing.
Yes the path is 100% correct. I orginally tried to get the files from a folder off my desktop, but wasn't sure if the spaces caused issues. So I coppied my expanded pgv folder to the root of d:.
No files ever copy.
Thanks
john
John,
I do want to change the message but haven't gotten round to it yet. ;)
I am at work now, so not able to testdrive it ;)
Just a hunch, in the first field you have to fill in the location of your current phpgedview installation. In the second field the location of the new phpgedview files.
I.e.
Field 1: d:\phpgedview <-- this is your current installation
Field 2: d:\upgrade <-- the location of the new phpgedview files
Am I correct you have set it up in this manner?
Regards,
Roland
Roland,
Sorry I too am at work. (Opps hope the boss isn't watching)
No my paths are different. First my site is housed on a *nix server. So my path (off my head) is /home/jtrainer/public_html/genealogy/gedview
and my upgrade source files are stored in d:\phpgedview
So for my first path, was that to be an ftp link, http, etc, what format do you expect my string to be in?
Thanks
John
Hey John,
The good thing is you run a *nix system, as I just have a fw based on a *nix system. As it is pnp it shows my knowledge of *nix (very unfortunate I don't have more knowledge)
I tried copying files with the script from my XP machine to the *nix machine. It went flawless. I specified the first path as \\servername\folder\folder2 etc. In this case it had to be backspaced because of the network connection.
This is a line from the log:
\\webserver\website\virtual\themes/ocean/style.css copied successfully.
So your first path should include the FQDN of your *nix machine.
A new version of the upgrade util has been uploaded to the patches section. It has quite a few improvements. It should produce a lot less errors.
Let me know how you get along.
Regards,
Roland
Rolland,
I think it's best to copy John's upload routine from the upload media, and upload gedcom functions. You could provide an upgrade conf file, that one could alter default paths. Using these functions, you could upload the files easier. I see no reason why we shold have to include a target path. The script should be run from the pgv directory.
I have no issue with John's functions, the files all upload fine. I think by having the users select the target directory will be a troublesome support issue. With some having user loacl to the site, and others without shell access etc... I think John's functions will be fine. Perhaps a second file, or within the conf file, you could have a list of all included files that need to be uploaded.
BTW, I like the new screen layout. Much nicer display.
John
The other John,
Youa re just ahead of me ;) Yesterday I already decided to remove the destination path, as I agree with you that it is already known where the files are supposed to be going.
Yes, the upgrade script is maturing. I noticed that it can run perfectly fine on 1 machine and totally not on another (eh Kurt ;)).
Tonight, I will upload the new version which will exclude the input of the destination path. I guess by now, the issue mentioned in 0.4a should be gone also.
Regards,
Roland
Hey hey hey...
Roland...
The latest script I got from you seemed to run :-)
Please remember in the future:
My system has also feelings and doesn't like it, if anybody talks bad about it ;-)
bye, Kurt