[wp-trac] [WordPress Trac] #13040: author.php doesn't recognize custom_post_type posts written by user

[WordPress Trac]

#13040: author.php doesn't recognize custom_post_type posts written by user
--------------------------+-------------------------------------------------
 Reporter:  10sexyapples  |       Owner:                               
     Type:  defect (bug)  |      Status:  new                          
 Priority:  normal        |   Milestone:  Unassigned                   
Component:  General       |     Version:                               
 Severity:  normal        |    Keywords:  author.php, custom post_types
--------------------------+-------------------------------------------------

Comment(by 10sexyapples):

 I hear what you are saying, but, I believe that the semantic direction
 that things are going in would be better served by keeping things as
 semantically close to what they are as possible, for example, one would
 expect the core author template behavior to include all things authored.
 One would also expect it to share the same behavior as the rest of the
 template hierarchy and funnel in the same direction. If an author
 -"something-specific" template doesn't exist, then use author.php, which
 includes all things authored and is a catch all. I read all of the
 discussions regarding the naming issue with the custom post type, and was
 in total agreement with the concept of "post" being a "type" of post-type.
 I won't quote the whole of that discussion, or in particular one person's
 very long and incredibly well written explanation ( can't remember who
 wrote it at the moment ), but, for me it was the clear direction of
 thought. I think this subject hits on the same topic, in that we have to
 break away from thinking of "post" as anything more than just another type
 of "post-type". And I really feel that we would heading in the wrong
 direction to give the "post" post-type templates like this that belong
 only to it. I feel pretty strongly  that it shouldn't have any templates
 that belong specifically to it ( outside of index.php ... and I have some
 opinions on that as well of course ;-) )unless implicitly specified by a
 plugin, or theme developer. At the moment, I am developing a site for
 bringing arts into education where artists and teachers will be
 creating/authoring lesson plans. The lessons are a custom post type, which
 is only logical if using WP as a CMS. The lessons need to be
 searchable/filterable/related with how tos ( another custom post type )
 and workshops ( yet another ). We won't be using the "post" post-type for
 anything other than news, and if I could go back and redo every site I've
 built, it would be the same scenario. The "post" post type is basically
 blog or news content for the most part. I hope you can see how if "post"
 post type is looked at with this "unique" factor, then, all of the
 "automatic" functions that would improve WP as a CMS sort of fly out the
 window. It becomes necessary to rewrite the whole template hierarchy to do
 anything with them. I've noticed that you're writing a framework that
 creates a new template hierarchy, how would you suggest having ( in my
 scenario for instance where I am building around three custom post types
 only ) an archive for all lessons, all howtos, and all workshops, and an
 author page which lists all of the content ordered by date created by one
 specific teacher? Just curious.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13040#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software