I do have this working for the DBMan FAQ so I'm not sure anything is wrong with the coding.
Do you set to the correct path to perl for your server:
#!/usr/local/bin/perl5
You also need to insert your body tags in the code such as:
print "<insert body tag here><center>\n";
should look something like this:
print "<BODY BGCOLOR="#FFFFFF" TEXT="#110000" LINK="#3333FF" VLINK="#23238E" ALINK="#000000">\n";
If you add the keywords.txt file in a file one directory up from your dbman files then in the following line use the full PATH (not url) to the .txt file:
open (DB, "keywords.txt") or die $!;
Perhaps for some reason it's not able to write to the file, if for instance you have this within your cgi-bin directory.
Did you try setting the keywords.txt file to 666?
If you view the file using FTP is it remaining empty?
I'm really not sure it's not working for you. There is nothing wrong with the coding.
In your db.cgi file did you make the change in sub query? It would look like this:
# First thing we do is find out what we are searching for. We build a list of fields we want to search on in @search_fields.
if ($in{'keyword'}) { # If this is a keyword search, we are searching the same
&track_kwords; ## Log Table-izer
$i = 0; # thing in all fields.
There are built-in errors messages, are you getting any error messages when you perform searches? It would warn it that it can't write to the file.
Just for the heck of it in your .cfg file move the line:
$db_debug = 0;
to above the section: # File and URL's
and turn on debugging to see if you get any error messages.
Unoffical DBMan FAQ
http://creativecomputingweb.com/dbman/index.shtml/
Do you set to the correct path to perl for your server:
#!/usr/local/bin/perl5
You also need to insert your body tags in the code such as:
print "<insert body tag here><center>\n";
should look something like this:
print "<BODY BGCOLOR="#FFFFFF" TEXT="#110000" LINK="#3333FF" VLINK="#23238E" ALINK="#000000">\n";
If you add the keywords.txt file in a file one directory up from your dbman files then in the following line use the full PATH (not url) to the .txt file:
open (DB, "keywords.txt") or die $!;
Perhaps for some reason it's not able to write to the file, if for instance you have this within your cgi-bin directory.
Did you try setting the keywords.txt file to 666?
If you view the file using FTP is it remaining empty?
I'm really not sure it's not working for you. There is nothing wrong with the coding.
In your db.cgi file did you make the change in sub query? It would look like this:
# First thing we do is find out what we are searching for. We build a list of fields we want to search on in @search_fields.
if ($in{'keyword'}) { # If this is a keyword search, we are searching the same
&track_kwords; ## Log Table-izer
$i = 0; # thing in all fields.
There are built-in errors messages, are you getting any error messages when you perform searches? It would warn it that it can't write to the file.
Just for the heck of it in your .cfg file move the line:
$db_debug = 0;
to above the section: # File and URL's
and turn on debugging to see if you get any error messages.
Unoffical DBMan FAQ
http://creativecomputingweb.com/dbman/index.shtml/
