Links 2.0 is really easy to reinstall...
Copy the *.cfg files and *.def files and the stuff in the DATA directory. (Make a back up).
Reinstall links, and then copy those files over their counterparts.
All the information telling links what to do and how to act is in the 3 config files in the admin directory, and the data in the *.db files in the 'data' directory. The two .txt files in the 'data' directory store the pointers to the next available ID.
Possibly the easiest thing to do is copy the nph_build.cgi from the distribution back over the current one and see if for some reason that got corrupted.
Make a backup of your current nph_build.cgi if you have made any changes to it so you have a guide of what to do to modify the new one, and do it step by step until it breaks <G>
you can just use a
print "this linke of text will show up somewhere ... \n";
inside routines called from the 'admin.cgi' script, since it has already sent a response header back to the browser to expect text back. The messages should show up in the message window between the Links notification messages.
Don't forget at least one '\n' to make the output more readable.
Hope this helps.
Copy the *.cfg files and *.def files and the stuff in the DATA directory. (Make a back up).
Reinstall links, and then copy those files over their counterparts.
All the information telling links what to do and how to act is in the 3 config files in the admin directory, and the data in the *.db files in the 'data' directory. The two .txt files in the 'data' directory store the pointers to the next available ID.
Possibly the easiest thing to do is copy the nph_build.cgi from the distribution back over the current one and see if for some reason that got corrupted.
Make a backup of your current nph_build.cgi if you have made any changes to it so you have a guide of what to do to modify the new one, and do it step by step until it breaks <G>
you can just use a
print "this linke of text will show up somewhere ... \n";
inside routines called from the 'admin.cgi' script, since it has already sent a response header back to the browser to expect text back. The messages should show up in the message window between the Links notification messages.
Don't forget at least one '\n' to make the output more readable.
Hope this helps.
