Gossamer Forum
Home : Products : DBMan : Installation :

Some problems....

Quote Reply
Some problems....
My knowledge of CGI is extremely limited. Reconfiguring scripts to my own server is pretty much the extent of my capabilities. :) I am not sure what information I need to give so I will tell the problem and put a link to my database.

The database is here - http://www.plahfeeg.com/cgi-bin/dbman/db.cgi?db=equine - the admin login is still admin/admin and you can test the features using that login.

The problems I am having are-

List All feature gives me a message "no search terms specified"

When adding a record- click add, and it tells me "the following record was successfully added to the database" but the record shown is blank

I didn't find anyone else having the same problem though I read several posts with similar situations- when checking my cfg file against the suggested fixes everything seems to be in order. Any help would be appreciated. :)

Sarah
Quote Reply
Re: [pfeeg] Some problems.... In reply to
It would help if you were to provide a copy of your files to be viewed.

Please save a text copy of your .cfg, and html.pl files on your server, and then provide the url to where they can be viewed.

Are you using autogenerate or did you setup your own add_form and html_record_form layouts?

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/
Quote Reply
Re: [LoisC] Some problems.... In reply to
I set it to autogenerate.

http://www.plahfeeg.com/equinecfg.txt

http://www.plahfeeg.com/htmlpl.txt

I appreciate that you are willing to take the time to look at them for me. :)



Sarah
Quote Reply
Re: [pfeeg] Some problems.... In reply to
In the .cfg file, for %db_def values you should use
'40x3'
not
40 * 3
The single quotes are important, and it's a lowercase x not a *

You also only have a single value for Title and Parent_Title in %db_select_fields

Having only one option in the drop down menu is a little pointless. ;)

You might also want to change the value of $auth_logoff near the bottom of the file.
Quote Reply
Re: [wysardry] Some problems.... In reply to
You may want to change:

$db_key = 'ID';

to:

$db_key = 'EQ';

as you don't have an ID field specified.

And as stated by wysardry your textaread need to be defined as for example:

Associations => [14, 'alpha', '40x3', 40, 0, '', ''],

where you have the 40, you may want to change that to the maximum amount of characters allowed in your textarea such as 600 (for 600 characters)

Hope this helps

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/
Quote Reply
Re: [LoisC] Some problems.... In reply to
Thank you very much for the suggestions, I made all the changes (except the title selection because I don't have the list of options for those fields yet.)

The list all feature now works.

However when adding a record, it still shows me a blank form, also, when adding or modifying records, there are no submission buttons. :/

I REALLY am a newbie at this, so if and when you have time, I would be most appreciative of any assistance. :)

I uploaded a new cfg text file same address. The htmlpl txt is the same as the original I didn't make any changes to it.

Thanks again :)
Quote Reply
Re: [pfeeg] Some problems.... In reply to
You still don't have 40x3 in single quotes:
'40x3'

You must change all instances of EQ to ID or vice versa - you can't refer to the key field by different names. It would be safest to use the default ID or be prepared to check all the scripts for references to ID and change them.

It's standard paractice to use ID as a name for a unique identifying field.
Quote Reply
Re: [wysardry] Some problems.... In reply to
It's not necessary to use "ID" as long as you have the key field identified properly within the .cfg file.

The script uses a variable to identify the record, so the name doesn't really matter.

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/
Quote Reply
Re: [LoisC] Some problems.... In reply to
Well, no, it isn't absolutely essential to use ID, but it does make more sense and is a good habit to get into if you intend to use other database systems.

That's so the key value can be referenced by dbname.field (or tablename.field), or in this case equine.EQ or equine.ID

Which makes more sense in that context? Wink

It's also going to help when asking questions here, as most people know which field you're talking about if you mention 'ID' but few will realise what 'EQ' is without being told.

More importantly though, $db_key must match the name of a valid field, and currently it's set to 'ID' which is non-existent.
Post deleted by Paul In reply to

Last edited by:

Paul: Jan 24, 2003, 1:19 AM
Quote Reply
Re: [wysardry] Some problems.... In reply to
Thank you both for your help, everything is now working! :)