[wp-trac] [WordPress Trac] #12075: query_posts behavior, is this how it's supposed to be? bug maybe or something to look at?

[WordPress Trac]

#12075: query_posts behavior, is this how it's supposed to be? bug maybe or
something to look at?
--------------------------+-------------------------------------------------
 Reporter:  Frumph        |       Owner:            
     Type:  defect (bug)  |      Status:  new       
 Priority:  normal        |   Milestone:  Unassigned
Component:  General       |     Version:            
 Severity:  normal        |    Keywords:            
--------------------------+-------------------------------------------------
 1) Setting the is_archive to true if using query_posts with certain
 options inside of the query, if used on the index page setting the
 is_archive has later effects down the post displaying logic if trying to
 utilize is_archive() for determination of what page not to or to display
 on if using a central display_post routine, since is_archive() is true on
 the index page after a query_post is_archive() being flagged true because
 of the query_posts it then can't be used as an actual determination

 2) if you do multiple loops on the index page and set showposts = # in a
 loop you want to be the one paged. it ignores the showposts in the backend
 for the urlrewrite for paged and will utilize the 'posts_per_page' ?
 'posts_per_archive_page' ? instead of the showposts = that's in the actual
 query  So when doing previous page or next page those become oblivious to
 the actual posts per pages its really supposed to be.


 Are those behaviors supposed to be that way?  If they are it's kind of
 interesting and the logic seems wrong to me.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12075>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software