[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:  Themes        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  template
--------------------------+------------------------------

Comment (by chipbennett):

 Replying to [comment:7 Frumph]:
 > Chip, I read your other request in the trac; #23669 that ticket concerns
 a similar interest however different by making the front-page.php a
 standard.

 Actually, #23699 is a completely separate issue, dealing with the way the
 Template Hierarchy (template loader) handles `get_option( 'show_on_front'
 )` when fetching template files. If implemented, it would allow Theme
 developers to treat `front-page.php` as specifically a custom, static-page
 template for the site front page, because WordPress would automatically
 use `get_home_template()` if `'posts' == get_option( 'show_on_front' )`.
 As it is currently, Theme developers have to build-in support in `front-
 page.php` for both `'posts'` and `'page'` as `get_option( 'show_on_front'
 )`. It really has nothing to do with how WordPress handles
 incorrect/incomplete configuration of the static front page settings.

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