[wp-hackers] Re: PHP notice warnings

[Computer Guru]

Think we can add a page to the codex about these "hidden constants"?

Here's what I have:

define('DB_NAME', 'blog');    // The name of the database
define('DB_USER', 'user');     // Your MySQL username
define('DB_PASSWORD', "pass"); // ...and password
define('DB_HOST', 'localhost');    // 99% chance you wont need to change
this value
define('ENABLE_CACHE', true); //WP in-built object cache
define('WP_HOME', 'http://neosmart.net/blog'); //Homepage
define('WP_SITEURL', 'http://neosmart.net/blog'); //Redirected homepage or
something :shrug:
define('DB_CHARSET', ''); //database character set
define('DB_COLLATE', ''); //database collation
define ('WPLANG', 'en_US'); //wordpress localization language
define('ABSPATH', dirname(__FILE__).'/'); //just the location of WP on the
HD
When I need one I look for it, see if it is defined... I think there are
probably some more I haven't looked for yet though....


On 9/22/07, Tom Barta <tbarta at gmail.com> wrote:
>
> > a developer who's not wandering into the source must be the kind of
> > developer who does not care about notices :)
>
> I care about notices, but I've probably only read 20% of the wordpress
> core source.  I know when I first looked at wordpress, the constants
> defined in wp-config.php stood out as an obvious place to look for
> developer-configurable settings.  I shouldn't have to look through
> *all* of the code just to find a list of available settings.
>
> Take /etc/ for example.  Most linux config files have commented-out
> options assigned to the defaults, which makes it easier to make
> modifications.  This is despite the fact that most of those options
> are 100% discoverable through man-pages... it's just a courtesy to
> sysadmins.
>
> --
> Tom
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Computer Guru
Director,
NeoSmart Technologies
http://neosmart.net/blog/