ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig(ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig(ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store'data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can storeke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig(ta files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store'data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?> ke it available via your * web server then you probably won't have any security for your data files. * * Don't make this the same as your gallery directory! */ $gallery->setConfig('data.gallery.base', '/usr/www/users/outdoosv/gallery2/n8imMKhhf'); /* * Gallery can store its data in multiple different back ends. Currently we * support MySQL, 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. Gallery 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 * * You must specify a table and column prefix. This is a few characters that * is prepended to any table or column name to avoid conflicting with reserved * words in the database or other tables you have in the same database. In * fact, it's fine to let Gallery uses the same database as other applications * (including other instances of Gallery itself); the prefix is enough * to distinguish Gallery's tables from other applications. * * We provide some reasonable default prefixes below. If you modify these * after Gallery has created its various tables, it will stop working until * you modify it back. * * The possible database types are: * mysql Standard MySQL * mysqlt MySQL with transactions (3.23.34a and newer) * postgres PostgreSQL 6.x (not rigorously tested) * postgres7 PostgreSQL 7.x * oci8po Oracle (9i and newer) */ $storeConfig['type'] = 'mysql'; $storeConfig['hostname'] = 'dedi132.cpt4.host-h.net'; $storeConfig['database'] = 'outdoorv_db1'; $storeConfig['username'] = 'outdoorv_1'; $storeConfig['password'] = 'GXgZCj38'; $storeConfig['tablePrefix'] = 'g2_'; $storeConfig['columnPrefix'] = 'g_'; $storeConfig['usePersistentConnections'] = false; $gallery->setConfig('storage.config', $storeConfig); /* * Put Gallery into debug mode. Useful for tracking down problems with the * application. Not a good idea to leave it this way, though. Possible debug * choices are: 'buffered', 'logged', 'immediate' or false. Don't forget to * use the quotes for any value but false! * * If you choose 'immediate', you'll see debugging information as soon as * Gallery generates it. This can be useful at times, but it'll screw up some * parts of the application flow. * * If you choose 'buffered', Gallery will display debug information in a table * as part of the application. You won't necessarily get *all* the debug * information but the application should work normally. * * If you choose 'logged', you must also specify: * $gallery->setDebugLogFile('/path/to/writeable/file'); * and all debug output will get printed into that file. You'll get all the * debug output and the application will work normally. * * For best debugging output use this line: * * $gallery->setDebug('buffered'); * */ $gallery->setDebug(false); /* * Profiling mode. You can enable profiling for different parts of G2 to get an * idea of what's fast and slow. Right now the only options are to enable SQL * profiling: * * $gallery->setProfile(array('sql')); * */ $gallery->setProfile(false); /* * Embedded mode. You can disable direct access to main.php (standalone G2) * by setting this this flag to true. */ $gallery->setConfig('mode.embed.only', false); /* * Allow a particular IP address to access the session (it still must know the * session id) even though it doesn't match the address/user agent that created * the session. Put the address of validator.w3.org ('128.30.52.13') here to allow * validation of non-public Gallery pages from the links at the bottom of the page. */ $gallery->setConfig('allowSessionAccess', false); /* * URL of Gallery codebase; required only for multisite install. */ $gallery->setConfig('galleryBaseUrl', ''); ?>

Who's Online

We have 1 guest online

© 2019 OutdoorPhotos - Kobus Robbertze
Website by SnapSites - http://www.snapsites.net
All rights reserved.