Make WordPress Core

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#12075 closed defect (bug) (wontfix)

query_posts behavior, is this how it's supposed to be? bug maybe or something to look at?

Reported by: Frumph Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:


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.

Change History (3)

#1 @Frumph
8 years ago

just to make it clear, the *other* loops are doing their own query pointers that do not effect the wp_query.

#2 @Frumph
8 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Taking this to the forums instead.

#3 @nacin
8 years ago

  • Milestone Unassigned deleted
Note: See TracTickets for help on using tickets.