Opened 17 years ago
Closed 17 years ago
#7221 closed defect (bug) (fixed)
PHP notice "WP_CONTENT_DIR undefined" occurs when creating wp-config.php
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.6 | Priority: | high |
Severity: | critical | Version: | 2.6 |
Component: | General | Keywords: | has-patch, installer |
Focuses: | Cc: |
Description
The first step of installing: wordpress can create a wp-config.php file with setup-config.php.
In this step, WP_CONTENT_DIR is not defined. But wp-includes/functions.php does not cosider the situation.
So, a PHP notice occures:
Use of undefined constant WP_CONTENT_DIR - assumed 'WP_CONTENT_DIR' in /home/*/public_html/wp-includes/functions.php on line 1988
To solve the problem: change line 1988 of wp-includes/fuctions.php below:
if (defined('WP_CONTENT_DIR') && file_exists( WP_CONTENT_DIR . '/db.php' ) )
Attachments (1)
Change History (5)
#2
@
17 years ago
- Owner changed from anonymous to sambauers
DD32 is probably right about defining a best guess at that early stage, either that or skip that part during install. I'll look into it.
Note: See
TracTickets for help on using
tickets.
Only problem with that, Is that to install, it means the user *must* use mysql/default database.
A better solution would be for the install script to define the new definitions at a best-guess i think.