Make WordPress Core

Opened 16 years ago

Closed 16 years ago

#7169 closed defect (bug) (invalid)

Pluggable.php Issue

Reported by: melspencer's profile melspencer Owned by:
Milestone: Priority: normal
Severity: trivial Version: 2.5.1
Component: General Keywords:
Focuses: Cc:

Description

Hello,

I'm new on here and already got a question.

Me and my online buddy run fansites, using wordpress on the index.php files. But recently, we discovered something.

When we type our fansites with www infront, this appears: Warning: Cannot modify header information - headers already sent by (output started at /home/xxx/public_html/index.php:2) in /home/xxx/public_html/wordpress/wp-includes/pluggable.php on line 694

But if we type our sites without www everything works fine.

I've already tried any solution help available on the WP support forums, but nothing helped. You are my last chance...

Hope you can help.

Thanks a A LOT in advance

Change History (6)

#1 @melspencer
16 years ago

  • Severity changed from normal to major
  • Version set to 2.5.1

#2 follow-up: @jacobsantos
16 years ago

  • Priority changed from highest omg bbq to normal
  • Severity changed from major to trivial

Look for new lines in index.php.

Lowering priority and severity until further evidence of non-user error is established.

#3 in reply to: ↑ 2 @melspencer
16 years ago

Replying to jacobsantos:

Look for new lines in index.php.

there aren't any new lines. i haven't touched index.php since i copied the php include for wordpress into it.

#4 @DD32
16 years ago

there aren't any new lines. i haven't touched index.php since i copied the php include for wordpress into it.

That may be the issue: There shouldnt be *anything* before the first <?php, If there still isnt, I suggest copying the contents, deleting the time, and pasting it into a new file. There could be an invisible marks beforehand.

This is more suited to the Support Forums: http://wordpress.org/support/ as it is not a Core WordPress issue(Its output being created by a non-wordpress file) - for that reason, This should probably be closed as invalid.

#5 @jacobsantos
16 years ago

It will be closed as invalid. I'm just interested in the outcome of where the issue is. Might be boring, since the issue isn't as cut and dry as "Hey, there is white space before or after your files."

I'm finding I really don't have time to explain this issue more than 5 times.

#6 @santosj
16 years ago

  • Milestone 2.7 deleted
  • Resolution set to invalid
  • Status changed from new to closed

Suspect new line after closing PHP tag. Recommend checking files for possible new lines after the files. If none are found, then reopen.

Note: See TracTickets for help on using tickets.