Opened 19 years ago
Closed 19 years ago
#2544 closed defect (bug) (fixed)
Running setup-config.php?step=2 (no wp-config.php) produces a 'Headers already sent' error
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 2.1 | Priority: | normal |
| Severity: | normal | Version: | 2.0.1 |
| Component: | General | Keywords: | wp-db.php bg|has-patch bg|commit |
| Focuses: | Cc: |
Description
Running the install script with wp-config.php not present, setup-config.php properly detects the missing file, and offers to create one. After filling in the necessary entries for hostname, user, password, database, and "submit"ing the data, setup-config.php fails at step 2 with this error.
Warning: Cannot modify header information - headers already sent by (output started at /storage/Debian/wordpress/wp-admin/setup-config.php:22) in /storage/Debian/wordpress/wp-includes/wp-db.php on line 308
This error is present in a 'clean' install of 2.0.1 and has been 'worked around' by commenting the following lines:
header( 'Content-Type: text/html; charset=utf-8');
<h1 id="logo"><img alt="WordPress" src="http://static.wordpress.org/logo.png" /></h1>
More in this thread: http://wordpress.org/support/topic/64003
Attachments (1)
Change History (14)
#2
@
19 years ago
Yes, it's normal to both send an HTTP header and have said header in an HTML meta tag.
#5
@
19 years ago
- Resolution set to worksforme
- Status changed from assigned to closed
Fixed for me. Patch worked fine.
#6
@
19 years ago
- Resolution worksforme deleted
- Status changed from closed to reopened
Thanks for your eagerness, but "worksforme" is for closing tickets that don't appear to be valid, i.e. no-one can replicate them. People tend to write patches then upload them onto bugs, which then eventually filter through into the core. When that is done (once the proposed code moves into the core), we then close the bug.
Sorry about the confusion.
#7
@
19 years ago
- Keywords bg|commit added
On the other hand, now we've got verification, I'll push it for commit.
#8
@
19 years ago
Not to worry at all, it does seem to work.
Afraid I'm pretty new to SVN so still finding my feet. I'll see if the codex has any info I can read up on the process on here. Thanks for the help.
#9
@
19 years ago
Allow me to explain the bug process.
1) User finds a bug
2) User asks around to make sure it's actually a bug, perhaps posts to the testers list
3) User makes a ticket on trac (this site, trac.wordpress.org)
4) Various code monkeys find the ticket, test it does actually exist
5) Someone writes a patch
6) That person uploads the patch using the 'Attach file' button
7) Someone else verifies the patch works
8) A committor (one of Matt Mullenweg or Ryan Boren) comes along and 'commits' the patch: changes the core code in our svn repository to include the patch that someone coded back in stage 5.
9) Bug is closed with 'fixed'.
#10
@
19 years ago
That was horribly formatted, let me try again.
- User finds a bug
- User asks around to make sure it's actually a bug, perhaps posts to the testers list
- User makes a ticket on trac (this site, trac.wordpress.org)
- Various code monkeys find the ticket, test it does actually exist
- Someone writes a patch
- That person uploads the patch using the 'Attach file' button
- Someone else verifies the patch works
- A committor (one of Matt Mullenweg or Ryan Boren) comes along and 'commits' the patch: changes the core code in our svn repository to include the patch that someone coded back in stage 5.
- Bug is closed with 'fixed'.
Just looking again and see the header is declared twice: