I forgot to mention that I tried to rebuild my pages using telent, but it won't work.
If I try to rebuild using the "Perl nph-build.cgi" alone, it would exectue using telnet but with some problems. This is because the nph-build.cgi file that shiped with the original SQL 1.11 was modified.
The way the scripts were modified, from the admin framed page I could execute either “nph-build.cgi?troot=english” or “nph-build.cgi?troot=spanish.” In other words, I used to rebuild pages in the English and Spanish versions at the time in the admin page.
However, in telnet, I did try to execute the “Perl nph-build.cgi?troot=english”, but it didn't work. In this case I got an error message: “bash: Perl: command not found.” So I guess that telent tried to interpret "nph-build.cgi?troot=english" as if it was a single file.
Is there other way I can work around this cgi file?
I really don’t know much of Perl (other that this is the language that Links SQL 1.x uses). So I will really appreciate some help.
Thanks in advance,
Carlos
If I try to rebuild using the "Perl nph-build.cgi" alone, it would exectue using telnet but with some problems. This is because the nph-build.cgi file that shiped with the original SQL 1.11 was modified.
The way the scripts were modified, from the admin framed page I could execute either “nph-build.cgi?troot=english” or “nph-build.cgi?troot=spanish.” In other words, I used to rebuild pages in the English and Spanish versions at the time in the admin page.
However, in telnet, I did try to execute the “Perl nph-build.cgi?troot=english”, but it didn't work. In this case I got an error message: “bash: Perl: command not found.” So I guess that telent tried to interpret "nph-build.cgi?troot=english" as if it was a single file.
Is there other way I can work around this cgi file?
I really don’t know much of Perl (other that this is the language that Links SQL 1.x uses). So I will really appreciate some help.
Thanks in advance,
Carlos