[wp-trac] [WordPress Trac] #27680: 2014 Wordpress will not show in Safari (Mac)

[WordPress Trac]

#27680: 2014 Wordpress will not show in Safari (Mac)
--------------------------+-----------------------
 Reporter:  Rachel Udin   |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  3.8.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by Rachel Udin):

 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 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.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27680#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform