<div dir="ltr">I believe that users and developers would prefer the scenario I propose.<div><br></div><div style>Of course, if I'm wrong, so be it. Hopefully input on the Trac ticket will provide a good indication.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 2, 2013 at 9:25 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Your case essentially says that front-page.php should not always be<br>
"the front page", which just makes no sense to me.<br>
<br>
What you're arguing for is a return to the way it was before the<br>
front-page.php file even existed. If the front-page template isn't<br>
*actually* going to be the front page, then why have it at all?<br>
<br>
If the theme wants to give the user the decision in the way you're<br>
describing, then they should not be creating the front-page.php and<br>
loading the home.php for the blog-on-front option. Instead, they<br>
should be creating a normal page.php and then loading a special-case<br>
for the page-on-front option instead. Or using a Page Template, to<br>
give the user additional options.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Otto<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On Sat, Mar 2, 2013 at 7:54 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> I disagree completely. (Ahh, just like old times!)<br>
><br>
> Just because a Theme has an awesome static front-page template doesn't mean<br>
> that the user should be forced to use it. Presumably, the rest of the Theme<br>
> is just as awesome as the static front-page template. So, while some users<br>
> may opt to use the Theme with a static front page, other users very well may<br>
> want to use the Theme while displaying the blog posts index as the site<br>
> front page.<br>
><br>
> There's simply no reason for the Theme to trump user choice here, and in<br>
> this regard, the discussion very closely resembles the "WordPress-as-CMS"<br>
> Themes discussion held some time ago. The logical conclusion of that<br>
> discussion was that there was a trivial difference between supporting blog<br>
> posts and not supporting blog posts (the so-called "CMS" use of WordPress),<br>
> and that "WordPress as CMS" was therefore not a valid special-use/niche<br>
> case. I believe the same is true for static-page-as-front-page. Just because<br>
> a Theme provides the option doesn't mean that it should be able to force<br>
> users into using that option.<br>
><br>
> It makes even less sense to force a Theme to use "template-front-page.php",<br>
> and instruct the user to jump through an extra hoop (apply template via Page<br>
> Attributes) beyond the normal static-front-page configuration steps, just to<br>
> make the static front page option truly *optional*. But that's essentially<br>
> what you're arguing for.<br>
><br>
> IMHO, it makes infinitely more sense for WordPress simply to fall back<br>
> automatically to the home template when the user has specified to display<br>
> the blog posts index on the site front page.<br>
><br>
><br>
> On Sat, Mar 2, 2013 at 8:22 PM, Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>> wrote:<br>
>><br>
>> On Sat, Mar 2, 2013 at 3:36 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
>> > I've just submitted a core patch that should facilitate Theme display of<br>
>> > the<br>
>> > blog posts index as the site front page for Themes that define custom<br>
>> > static<br>
>> > front page content using front-page.php:<br>
>> > <a href="http://core.trac.wordpress.org/ticket/23669" target="_blank">http://core.trac.wordpress.org/ticket/23669</a><br>
>> ><br>
>> > Essentially, if approved, this patch would modify the template hierarchy<br>
>> > slightly, such that the site front page would use home.php if 'posts' ==<br>
>> > get_option( 'show_on_front' ), and would only use front-page.php if<br>
>> > 'page'<br>
>> > == get_option( 'show_on_front' ).<br>
>> ><br>
>> > Comments/criticism/other feedback welcome!<br>
>><br>
>><br>
>> No, I agree with Michael Fields on that one. The front-page.php file<br>
>> should be used as the "front page" regardless of what the user has set<br>
>> to be on the front-page. If this is not desired, then the<br>
>> front-page.php file should be removed entirely.<br>
>><br>
>> There's basically two use cases here:<br>
>><br>
>> 1. Theme wants to always have the front page look the same way,<br>
>> regardless of user choice. Solution: Use front-page.php. Done and<br>
>> done. User choice then only affects the content of that front-page, by<br>
>> choosing whether to use the blog posts or the content from a static<br>
>> Page.<br>
>><br>
>> 2. Theme wants user choice to change the look of the front page.<br>
>> Solution: Don't use front-page.php at all. Use home.php, which will<br>
>> always be used for the blog posts regardless of location, then provide<br>
>> a special Page Template (named something other than front-page.php) if<br>
>> the theme wants to provide a special look for the static-page case.<br>
>> The user can then choose to use that Page Template or not, as they<br>
>> desire. Alternatively, you could just use page.php if the pages across<br>
>> the site are all supposed to look special.<br>
>><br>
>> There's no real good reason I can think of to have front-page.php<br>
>> check for the blog-on-front case and load home.php instead. If that is<br>
>> the desired use case, then front-page.php should simply not be<br>
>> included at all.<br>
>><br>
>> -Otto<br>
>> _______________________________________________<br>
>> theme-reviewers mailing list<br>
>> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
>> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>