Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#27680 closed defect (bug) (invalid)

2014 Wordpress will not show in Safari (Mac)

Reported by: rachel-udin's profile Rachel Udin Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.8.1
Component: General Keywords:
Focuses: Cc:

Description

The file works fine in Firefox with absolutely no errors. However in Safari it freaks out and gives me the error:
Warning: Cannot modify header information - headers already sent by (output started at /home/goldsheep/racheludin.com/index.php:39) in /home/goldsheep/racheludin.com/wordpress/wp-includes/pluggable.php on line 896

Things I tried:

  • Redownloading wordpress and upping it to the website.
  • updating the plugins
  • turning off all the plugins
  • Changing the theme.
  • backtracking the error using debug_print_backtrace(); before the line in pluggable.php
  • making sure there was no spaces in pluggable.php (per the help file)
  • going over every file the backtrace said to look for white space: there was none.
  • stripping back the shell that called for the wordpress file. (error persists.)

Other files that depend on pluggable.php also produce similar errors for the line.

Note: that it's only reproducable in Safari and it only happened when I updated the website to 2014 version of wordpress, the latest version.

I consulted a programmer who is clueless... so given it's not themes or plugins, it's the wordpress core. (I did not meddle with any of the files, beyond the usual customization.)

Thanks for looking at this issue.

Attachments (2)

Screen Shot Safari 2014-04-04 at 3.09.38 PM.jpg (107.6 KB) - added by Rachel Udin 10 years ago.
A screenshot in Safari. Works fine in F irefox.
Screen Shot Firefox 2014-04-04 at 3.09.15 PM.jpg (418.6 KB) - added by Rachel Udin 10 years ago.
Screenshot in Firefox, works fine.

Download all attachments as: .zip

Change History (6)

@Rachel Udin
10 years ago

A screenshot in Safari. Works fine in F irefox.

@Rachel Udin
10 years ago

Screenshot in Firefox, works fine.

#1 @dd32
10 years ago

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

racheludin.com/index.php:39

The WordPress core index.php file is only 18 lines long, this is suggesting your file is at least 39 lines long.
I suspect you've got extra data in that file which is causing your problems, I'd suggest you re-install WordPress (Either by FTP, or, by going to your WordPress Dashboard -> Updates page and hit the reinstall button).

This doesn't appear to be a bug in WordPress, so please use the Support Forums if you need further assistance.

#2 follow-up: @Rachel Udin
10 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

I dispute this assessment on the grounds that you fail to recognize that I used an insert. I referred to wordpress by calling an includes into a shell. When I removed that shell, as I said, the problem persisted, which means it's a wordpress problem. A mere include should not produce the problem.

The WORDPRESS index page is on a subfile in a wordpress folder. One refers to the other through PHP.

and the wordpress index.php reads in the folder:
<?php
/

  • Front to the WordPress application. This file doesn't do anything, but loads
  • wp-blog-header.php which does and tells WordPress to load the theme. *
  • @package WordPress */

/

  • Tells WordPress to load the WordPress theme and output it. *
  • @var bool */

define('WP_USE_THEMES', true);

/ Loads the WordPress Environment and Template */
require( dirname( FILE ) . '/wp-blog-header.php' );

As this problem persists across various websites I've had, I know it's a wordpress problem.

The problem persists on pluggable.php, which is a faulty file. When I login to wordpress, which is NOT dependent on the shell it comes up. When other files call to it, it produces the SAME error. There is something wrong with pluggable.php and thus whatever it's calling to needs to be fixed.

You also failed to recognize that it only happened when I updated wordpress.

It seems you failed to actually read the entire comment as you didn't acknowledge any of it and even admit you only looked at the length of the file rather than either READING the file or asking questions for clarification or taking 2 seconds to assess that it might be a deeper problem.

As this persists across many websites and ONLY with the 2014 update, I'm fairly sure it's wordpress. Doesn't matter on plugins, or theme. There is a bug. And I did NO mods to wordpress, which is in a SUB folder that the main index.php calls to.

Version 0, edited 10 years ago by Rachel Udin (next)

#3 @SergeyBiryukov
10 years ago

  • Resolution set to invalid
  • Status changed from reopened to closed

Replying to Rachel Udin:

The problem persists on pluggable.php, which is a faulty file.

No, that line just sends an HTTP header: tags/3.8.1/src/wp-includes/pluggable.php#L896.

Warning: Cannot modify header information - headers already sent by (output started at /home/goldsheep/racheludin.com/index.php:39) in /home/goldsheep/racheludin.com/wordpress/wp-includes/pluggable.php on line 896

The issue clearly comes from line 39 of the index.php file one level above your WordPress install. The file produces some unexpected output, consequently preventing any HTTP headers from being set.

Please don't reopen the ticket, as there's nothing we can do to "fix" this. Please try the support forums.

Last edited 10 years ago by SergeyBiryukov (previous) (diff)

#4 in reply to: ↑ 2 @SergeyBiryukov
10 years ago

Replying to Rachel Udin:

A mere include should not produce the problem.

If you're including wp-load.php manually, you need to do that before any output has been sent to the browser.

Note: See TracTickets for help on using tickets.