Comment out Webbleyou text for now

Commenting out (not reverting) this change to Editing wp-config.php because a user who installed WordPress at 2.2 would legally have DB_COLLATE and DB_CHARSET in wp-config.php.

MichaelH (talk)

Protecting the article

Is there any way we can protect the wp-config-sample part of this page? Despite the big red warning box people still come along and edit it with their own details. sigh.

mrmist 12:26, 17 January 2009 (UTC)

I though for sure that red box would be a good idea, It did cut back a little bit though.Charles F-M 12:31, 19 January 2009 (UTC)

I could always protect the page, but then valid editors would not be able to change the page. --MichaelH (talk) 14:07, 19 January 2009 (UTC)

Depends on how much admin overhead that would create I guess. Then it becomes a toss-up between having to unlock the page for valid edits, or reverting the stuff that people leave in by mistake. Hmm.

The red box was a good idea for sure - you just can't stop some folk, it seems. mrmist 17:59, 19 January 2009 (UTC)

Add examples

Please add examples. E.g., should we

define('DB_NAME', 'wordpress'); #or
define('DB_NAME', 'wp_nurdsboro');

I would think the latter, but then I see

$table_prefix  = 'wp_';

So you need examples for each item so we can establish conventions. Jidanni 21:20, 19 January 2009 (UTC)

Is there a valid example for "database name"? It could pretty much be anything. Table prefix is a (relatively) advanced option. I'm not sure that you necessarily help people by supplying examples, as in most cases you wouldn't need to change it. mrmist 21:24, 19 January 2009 (UTC)

Any example without a wp_ would at least show the user that this is not the place for putting wp_... Jidanni 20:30, 20 January 2009 (UTC)

Examples for table prefixes are actually given further down in the table prefix advanced option section. I am not convinced that there's a valid example for database name, when it could be anything, and is in some cases pre-defined by your hosting provider. Also, just to play Devil's advocate, some of my WordPress database names do start with wp_ mrmist 21:29, 20 January 2009 (UTC)

Moving wp-content - more relevant constants.

I had a heck of a time pinning down how to change the uploads directory specifically, which I needed to do because of the fact that our custom wp-content location is being shared across multiple instances of WordPress.

Its simple, its currently hard to find and theres a gotcha.

Its important to note this needs to be a relative path. The value of UPLOADS is combined with ABSPATH - this also means that the uploads directory can't be moved outside WordPress root directory.

define( 'UPLOADS', 'wp-content/uploads' );

Please correct me if this is wrong, or if it should be in a different location.

Comment

I can't tell when the above was added, and this comment is just to suggest a correction on the page to make this clearer.

It doesn't seem to matter if there is a leading slash or not when naming the alternate directory. For example both

• define ( 'UPLOADS', '/files' );
• define ( 'UPLOADS', 'files' );

put uploaded files into the "files" subdirectory of ABSPATH. (By default, wp-content/ is also a subdirectory of ABSPATH, so files and wp-content would be at the same level.)

So the current example,

• define( 'UPLOADS', '/blog/wp-content/uploads' );

seems odd. It seems to me that the convention has been to use "/blog" for the subdirectory where WordPress is installed, i.e. "/blog" is the last component of ABSPATH. Defining uploads as above would mean creating a directory

ABSPATH/blog/wp-content/uploads

which would seem confusing in the default case when there is another directory wp-content which is a child of ABSPATH

I'd suggest changing the example to something like

• define ( 'UPLOADS', 'uploads' ); -- to make the directory a sibling of wp-content

or

• define ( 'UPLOADS', 'wp-content/uploads.example' ); -- to leave it in the same location but change its name

Converting2wp 00:58, 17 January 2014 (UTC)

User Unfriendly

There has been discussion about this codex page being "instantly scary" for users. See: https://core.trac.wordpress.org/ticket/26879

I understand the reason for the big red warning messages at the top of the page, and I hope the problem of people attempting to add their confidential database credentials into this page is no longer a serious issue. My edits keeps the warning in place but makes it a little less scary.

Formatting of Notes

This is likely a "known issue", but the NOTES seriously break the formatting of the page.