Gossamer Forum
Home : Products : Others : Gossamer Community :

Debugging GCommunity Installation

Quote Reply
Debugging GCommunity Installation
I'm getting an error installing GCommunity at the point where the installation script attempts to access my database. It looks like GCommunity has code for displaying debugging output. How can I turn this on so that I can see the string that GCommunity is using to connect to the database? The error is:

Quote:
Error:Could not connect to database. Reason: Access denied for user: '(name changed for the post)@localhost' (Using password: YES)


(Also, maybe the installation process could be clarified a bit by saying whether the database is created automatically by the community.cgi script, or whether the datbase should be created manually in a separate step by the person doing the installation.)
Quote Reply
Re: [AS] Debugging GCommunity Installation In reply to
Anyone? I'd really appreciate some help with this -- I want to try GCommunity and am stuck at this part in the installation process. Any information about how to turn debugging on or even about to add a line to print something from within GCommunity code would be appreciated. I have tried just printing to STDERR but that didn't seem to do anything. Setting "debug = 1" in the community.conf file didn't seem to do anything either. I have used this database user name and password before with other products.
Quote Reply
Re: [AS] Debugging GCommunity Installation In reply to
The information that is used to connect to the database is in a file called 'database.def', which is stored in the 'private/defs' directory.

Ivan
-----
Iyengar Yoga Resources / GT Plugins
Quote Reply
Re: [yogi] Debugging GCommunity Installation In reply to
Hmm, right now database.defs is empty. I bet that database.defs is supposed to be created and filled in as part of the installation script that I am stuck in. If I knew how to turn debugging on, or how to print debug output myself, then maybe I could see the connection string that is being generated and then compare it to the one that I know worked in other applications. The obvious things I tried like using "print", setting $DEBUG=1, and changing the value of "Debug" in the configuration file didn't work. Any ideas?