[wp-trac] [WordPress Trac] #44273: page routing problems (was: ability to delete tickets)

WordPress Trac noreply at wordpress.org
Wed May 30 07:50:45 UTC 2018


#44273: page routing problems
--------------------------+----------------------
 Reporter:  musicforte    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  4.9.6
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by SergeyBiryukov):

 * severity:  trivial => normal
 * type:  feature request => defect (bug)
 * milestone:  Awaiting Review =>


Old description:

> With the 4.9.6 update I have pages that are routing to blank pages with
> HTTP/1.1 200 OK
>
> [local at KnownHost ~]$ curl -IL https://www.felixandfingers.com/blog-
> projects/
> HTTP/1.1 200 OK
> Date: Tue, 29 May 2018 20:45:37 GMT
> Server: Apache
> X-Powered-By: PHP/5.6.31
> Cache-Control: max-age=0
> Expires: Tue, 29 May 2018 20:45:37 GMT
> Vary: Accept-Encoding
> Content-Type: text/html; charset=UTF-8
>
> [local at KnownHost ~]$ curl https://www.felixandfingers.com/blog-projects/
> [local at KnownHost ~]$
> -----
>
> That would lead me to suspect that something's wrong within WordPress's
> page router, and it's not routing to the correct page. No errors are
> generated, as I monitored all error_log files in the document root as
> well as the primary Apache error log, and no errors were triggered. It
> seems to be entirely a WordPress malfunction at this point.
>
> I have other examples of pages if needed.

New description:

 With the 4.9.6 update I have pages that are routing to blank pages with
 HTTP/1.1 200 OK
 {{{
 [local at KnownHost ~]$ curl -IL https://www.felixandfingers.com/blog-
 projects/
 HTTP/1.1 200 OK
 Date: Tue, 29 May 2018 20:45:37 GMT
 Server: Apache
 X-Powered-By: PHP/5.6.31
 Cache-Control: max-age=0
 Expires: Tue, 29 May 2018 20:45:37 GMT
 Vary: Accept-Encoding
 Content-Type: text/html; charset=UTF-8

 [local at KnownHost ~]$ curl https://www.felixandfingers.com/blog-projects/
 [local at KnownHost ~]$
 -----
 }}}
 That would lead me to suspect that something's wrong within WordPress's
 page router, and it's not routing to the correct page. No errors are
 generated, as I monitored all error_log files in the document root as well
 as the primary Apache error log, and no errors were triggered. It seems to
 be entirely a WordPress malfunction at this point.

 I have other examples of pages if needed.

--

Comment:

 Hi @musicforte, welcome to Trac!

 We don't generally delete tickets unless it's spam. If it turned out to be
 a plugin or theme issue rather than WordPress core, the ticket can be
 closed as `invalid`, or `worksforme` if the issue is unclear but can no
 longer be reproduced:
 https://make.wordpress.org/core/handbook/contribute/trac/.

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


More information about the wp-trac mailing list