4 | | 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. |
| 4 | Actually, #23669 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. |