[wp-trac] [WordPress Trac] #28763: Behavior of template heirarchy in settings -> reading when posts page is set but not front page displays

[WordPress Trac]

#28763: Behavior of template heirarchy in settings -> reading when posts page is
set but not front page displays
--------------------------+-----------------------------
 Reporter:  Frumph        |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 similar ticket #22131 closed as fixed

 Setting a post page but not a front page displays (in settings ->
 reading), makes both the landing page and the page set to posts use the
 home.php template (i.e. both are is_home()), should the landing page (root
 page) be default to front-page.php instead (if) posts page is used?

 No option set on the front page display also makes both locations the blog
 loop and the landing page register as is_home(), while at this point they
 are indeed different.

 Otto on the TRT threads say it's a bug that you can set one and leave the
 other not set; but having it default to making the landing page
 is_front_page() with nothing selected would (imo) alleviate this bug -
 forcing the system to consider the posts page is_home() and the landing
 page is_front_page() regardless if a page is specifically selected

 Take note I'm bad at articulating what I mean so bear with me; if you need
 me to further clarify.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/28763>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform