[wp-trac] [WordPress Trac] #21951: Twenty Twelve: add post_type_archive_title to archive.php
WordPress Trac
wp-trac at lists.automattic.com
Sat Sep 22 08:23:39 UTC 2012
#21951: Twenty Twelve: add post_type_archive_title to archive.php
---------------------------+------------------
Reporter: thomask | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 3.5
Component: Bundled Theme | Version:
Severity: normal | Resolution:
Keywords: has-patch |
---------------------------+------------------
Comment (by dd32):
Replying to [comment:12 obenland]:
>Replying to [comment:11 lancewillett]:
> > Replying to [comment:9 nacin]:
> > > I guess the question is, which is simpler?
> >
> > Fewer template files.
>I agree with Lance on the template issue.
The problem with those answers, is that it's coming from a Theme
Developer; a PHP Developer; someone who knows their stuff - look at it
from the other side of the fence, someone newer to theme development and
potentially not very PHP smart, multiple files may be simpler, and as a
boost, it also enforces the concepts of template hierarchy.
It goes to the notion that different parts of the Theme are different
files - as that's the notion that most people are used to, they're not
thinking of an Archive of posts categorized by random things, they're
thinking that they want to customise their Category page (and then being
confused why the year view was changed too).[[BR]]
Of course.. the thing is, having it as one larger file doesn't prevent
people from using category.php in their child themes, it's only those who
copy the theme verbatim which benefits from separate files - potentially
the people who would benefit from multiple files the most.
If it's not obvious enough, I like the separate files, and am surprised
that more people don't release themes that way - there's a reason most
frameworks come with every template file under the sun documented and
loaded.. not just for the extra bloat factor, but because it makes it
easier for some.
> especially a few days before freeze.
In this case, since there's no imminent deadline (tied to a major
!WordPress release for example) and it doesn't significantly alter how the
theme operates, I don't see that as a good reason to not consider the
merits.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/21951#comment:13>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list