Gossamer Forum
Home : Products : DBMan : Installation :

enable debugging

Quote Reply
enable debugging
Hello,

I would appreciate some assistance this morning. I have modified the default.cfg file and the html.pl and uploaded them to the server. All worked well until up until the last few changes to the .cfg file and the html file. At that point I received the following when pointing to http://viewpointdesign.net/cgi-bin/dbman/vrddb.cgi:

DBMan encountered an internal error. Please enable debugging to view.

I had already set: $db_debug = 1;

Because of this, I am unable to pinpoint the general location of my problem.

I made certain that both files were uploaded in ASCII, and that they were permissioned correctly. The perl path is correct, as well.

I noticed that before I received this error, that after the changing the database title name in the html.pl file, that my entry was not rendering, but rather the demo. Oddly, it seems that it is rendering a different file completely.

I have placed a text file at:

http://viewpointdesign.net/.../proofs/vrd_cfg.txt] to show the changes I have made to this file. Can someone please view it and tell me if something readily jumps out as an error. I followed the tutorial to the letter. But I am human and I may have fat fingered something that I can not see.

Thank you.

Best Regards,

Kim Lanners


Software Made Easy
http://sme-net.com
Quote Reply
Re: enable debugging In reply to
My apologies, I left a bracket in the URL to the text file. Here is the correct link:

http://viewpointdesign.net/...s/proofs/vrd_cfg.txt

Software Made Easy
http://sme-net.com
Quote Reply
Re: enable debugging In reply to
quote:
that after the changing the database title name in the html.pl file

just a guess, but does your title have an ' in it ..
such as gail's databsase?

If so, be sure to enclose the title as 'Gail's database'.

In the resource center you will find a little mod which can be used to find errors within cgi file. It's called "debugging - useful error messages or something like that. It can saves hours of trying to track down errors Smile

Unoffical DBMan FAQ
http://webmagic.hypermart.net/dbman/
Quote Reply
Re: enable debugging In reply to
Good Morning Lois,

Thank you for your reply!

No, I have no punctuation marks within the title. It simply says, 'Viewpoint Residential Design, LLC Home Plan Database'

I'll go on out to the resource you suggested and see if I can set that up without hosing it. Crazy

Best Regards,

Kim Lanners

Software Made Easy
http://sme-net.com
Quote Reply
Re: enable debugging In reply to
Hello again Lois,

I think I should probably opt to stay home
and bake cookies.Crazy

After telling you, 'No, I have no punctuation marks within the title' I looked again. I do in fact have a comma prior to ,LLC. Duh!

I imagine this has the same effect as if I had used 'Gail's'. Correct?

I will go make modifications and try again.

Thanks!

Best Regards,

Kim Lanners

Software Made Easy
http://sme-net.com
Quote Reply
Re: enable debugging In reply to
Hello LoisC,

I changed the title of the vrdhtml.pl file. It had no effect.

I inserted the code into the vrd.cgi file that you had posted at: http://webmagic.hypermart.net/dbman/trouble1.txt
I was unable to get this to work. As I said earlier, it seems as though my requests are being pulled from a file other than vrd.cgi. Yet, I can not pin point this.

Oddly, after I took all of my backup files and restored them to the directory, I still receive the message:

DBMan encountered an internal error. Please enable debugging to view.

This is the stage where all failed when I encountered the 404 error a couple of days ago and restoring backup files did not work at that point either. I had to bring in fresh copies of everything and start all over.

I will rebuild the files once again. Frown

Thanks!

Best Regards,

Kim Lanners

Software Made Easy
http://sme-net.com
Quote Reply
Re: enable debugging In reply to
I found your problem.

In your .cfg file, you need to set up your select field like this:


# Select fields. Field name => 'comma seperated list of drop down options'.
%db_select_fields = (
'Number of Bedrooms' => '1,2,3,4,5,6,7,8,9,10',
'Number of Full Baths' => '1,2,3,4,5,6,7,8,9,10',
'Master Bedroom Level' => 'Upper Level,Main',
'Number of Floors' => '1,1 1/2,1 1/2 reversed,2,3'
);


When you have spaces in the field names, you need to put single quotes around them. Also, you had some spaces after commas in your select field definitions. That would cause you problems later on.


JPD
http://www.jpdeni.com/dbman/
Quote Reply
Re: enable debugging In reply to
Hi JPD,

Thanks for your reply. Earlier in the day, I contacted support. Steven Chen was kind enough to look over every thing.

In addition to the '' closures you have mentioned. He also found that when I changed the names of all the files, I had failed to rename one reference to the newly named 'auth.pl' file in this line: require "auth.pl"; # Authorization Routines.

He indicated that he was not certain what went wrong. As you know, I had it up and working very early yesterday morning. I suspect that even though the script ran a couple of times yesterday morning with the auth.pl file not renamed properly and the quotes not included in the field names, that it finally all caught up and in doing so, hosed itself.

It is working now, in as much that I can add records. I will now go further in your tutorial to finish configuring the script.

Your pointing out the need for quotes around field names that include spaces was very much appreciate. Smile
This last week has been very enlightening, indeed. I have learned, "When working on a perl script....re-check code, re-check code, re-check code!!" Laugh

Thank you again for your help!

Best Regards,

Kim Lanners

Software Made Easy
http://sme-net.com
Quote Reply
Re: enable debugging In reply to
Smile I'm glad I could help. And that Steve found another problem.

I learned something from your .cfg problem, though. With the security change in the sub cgierr, if the problem is within the .cfg file, you won't get any messages even if you set $db_debug=1;. The script stops working as soon as it encounters a problem, so it never sees the setting of $db_debug. The only way around it may be to move the "debug" switch to the beginning of db.cgi. I'll have to test that a bit.

JPD
http://www.jpdeni.com/dbman/