bitweaver
Wiki
wiki Home
List Pages
wiki Books
Orphan Pages
wiki Rankings
Photos
List Galleries
Forums
Browse forums
Files
List Galleries
Categories
List Categories
Sign In
Message Boards
»
08. Support - General talk
Newest
Oldest
Threaded
5
10
20
50
100
All
Messages
Installation problem : adodb.inc.php > white screen
Post Reply
Beta Byte
Joined: 26 Mar 2007
Installation problem : adodb.inc.php > white screen
Posted:26 Mar 2007 (14:03 UTC)
laetzer
Joined: 15 Mar 2004
Posted:26 Mar 2007 (15:33 UTC)
Beta Byte
Joined: 26 Mar 2007
Posted:26 Mar 2007 (17:03 UTC)
laetzer
Joined: 15 Mar 2004
Posted:26 Mar 2007 (17:46 UTC)
Beta Byte
Joined: 26 Mar 2007
Posted:26 Mar 2007 (20:40 UTC)
Lester Caine
Joined: 24 Apr 2004
Posted:28 Mar 2007 (05:01 UTC)
Beta Byte
Joined: 26 Mar 2007
Posted:28 Mar 2007 (13:01 UTC)
Post Reply
Page 1 of 1
1
Post
Title
Login
If you are already registered, please enter your login credentials.
Your Name
Anonymous Post
Content Format
Tiki Wiki Syntax
Allow HTML
{quote format_guid="bbcode" comment_id="7201" user="laetzer"}[code:1:a5823a58de] <?php // Copyright (c) 2006, bitweaver.org // Licensed under the GNU LESSER GENERAL PUBLIC LICENSE. // The following line is required and should not be altered global $gBitDbType, $gBitDbHost, $gBitDbUser, $gBitDbPassword, $gBitDbName, $gBitDbCaseSensitivity, $smarty_force_compile, $gDebug, $gPreScan; /******************************************************\ *************** Database settings **************** \******************************************************/ // You can choose between different Database abstraction layers. Currently we support: // adodb ADODB // this is the default setting and is bundled with bitweaver // pear PEAR::DB // when using this, you can even remove the util/adodb directory $gBitDbSystem = "adodb"; // bitweaver can store its data in multiple different back-ends. Currently we // support MySQL, MSSQL, Firebird, Sybase, PostgreSQL and Oracle. Enter the // hostname where your database lives, and the username and password you use to // connect to it. // // You must specify the name of a database that already exists. bitweaver will not // create the database for you, because it's very difficult to do that in a // reliable, database-neutral fashion. The user that you use should have the // following permissions: // // SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP // // The possible database types that we support are: // mysql Standard MySQL // mysqli New MySQL driver // sqlite SQLLite // mssql MS-SQL (experimental) // postgres PostgreSQL 7.x // oci8po Oracle (9i and newer) // firebird FireBird // sybase Sybase $gBitDbType = "mysql"; // Hostname or IP for your database. // Some examples: // 'localhost' if you are running the database on the same machine as bitweaver // If you use Oracle, insert your TNS Name here // If you use SQLite, insert the path and filename to your database file $gBitDbHost = "localhost"; // Database username $gBitDbUser = "XXXXXXXXXXXXXXXXXX"; // Database password $gBitDbPassword = "XXXXXXXXXXXXX"; // Database name $gBitDbName = "XXXXXXXXXXXXXXXXX"; // Database field case default $gBitDbCaseSensitivity = ""; // This prefix will be prepended to the begining of every table name to allow // multiple independent installs to share a single database. By ending the prefix // with a '.' (period) you can use a schema in systems that support it. Backticks // '`' around the '.' are required if present. A schema example is: 'bit`.`' define( 'BIT_DB_PREFIX', '' ); /******************************************************\ *************** Environment Settings **************** \******************************************************/ // Setting IS_LIVE to TRUE will let the application know that this site is a live // production site and is not used for testing purposes. This will prevent any // nasty error pages from appearing and will redirect the user to a 'nicer' error // page. Errors should still show up in your error logs. Please use these when // submitting bugs to http://sourceforge.net/tracker/?group_id=141358&atid=749176 define( 'IS_LIVE', FALSE ); // if you set AUTO_BUG_SUBMIT to TRUE bitweaver will automatically email the team // with details regarding the error. Alternatively you can submit bugs to // http://sourceforge.net/tracker/?group_id=141358&atid=749176 which will probably // get processed faster since more people have access to these. define( 'AUTO_BUG_SUBMIT', FALSE ); // This is the path from the server root to your bitweaver location. i.e. if you // access bitweaver as 'http://MyServer.com/applications/new/wiki/index.php' you // should enter '/applications/new/' define( 'BIT_ROOT_URL', '/' ); // This allows you to set a custom path to your PHP tmp directory - used for ADODB // caching if active, and other stuff This is usually only needed in very // restrictive hosting environments. //$gTempDir = '/path/to/private/directory'; // $gPreScan can be used to specify the order in which packages are scanned by // the kernel. In the example provided below, the kernel package is processed // first, followed by the users and liberty packages. Any packages not specified // in $gPreScan are processed in the traditional order //$gPreScan = array( 'kernel', 'users', 'liberty' ); /******************************************************\ *************** Debugging Options **************** \******************************************************/ // If you wish to force compiling of every page, you can set the next setting to // TRUE. this will, however, severly impact performance since every page that is // generated is generated afresh and the cache is recreated every time. $smarty_force_compile = FALSE; // Setting TEMPLATE_DEBUG = TRUE will output <!-- <called templates> --> in your // templates, which will allow you to track all used templates in the HTML source // of the page. This will also disable stripping of whitespace making it easier to // read the templates. You will only see the effect of the strip changes by // clearing out your cache or setting $smarty_force_compile = TRUE; // Note: be sure to set this to FALSE and clear out the cache once done since it // will increase the page size by at least 10%. //define( 'TEMPLATE_DEBUG', TRUE ); // This statement will enable you to view all database queries made //$gDebug = TRUE; // This will turn on ADODB performance monitoring and log all queries. This should // not be enabled except when doing query analysis due to an overall performance // drop. see kernel/admin/db_performance.php for statistics //define( 'DB_PERFORMANCE_STATS', TRUE ); ?> [/code:1:a5823a58de]{/quote}
Recent Page Changes
welcome to bitweaver.org
Bitweaver Overview
ReleaseTwo Schema Changelog 2006
PressReleaseOne
Spider's Web
Press Release Two
BitcommercePackage
InfiniBand vs Ethernet Performance
InfiniBand for Dummies
Show More…