[wp-trac] Re: [WordPress Trac] #9425: The various $is_* variables in $WP_Query should only be set on the very first query call.

[WordPress Trac]

#9425: The various $is_* variables in $WP_Query should only be set on the very
first query call.
--------------------------------------+-------------------------------------
 Reporter:  mtg169                    |        Owner:  anonymous
     Type:  defect (bug)              |       Status:  reopened 
 Priority:  high                      |    Milestone:  2.8      
Component:  General                   |      Version:  2.7.1    
 Severity:  major                     |   Resolution:           
 Keywords:  needs-patch dev-feedback  |  
--------------------------------------+-------------------------------------

Comment(by hakre):

 Denis, I understand your disappointment and I do understand the problems
 you run into very well. But those are WordPress related. wp_query is one
 of the most central functions in wordpress data processing.

 Because the querying and displaying of data in WordPress is absolutely
 connected (in opposite to seperated, many WP devs call that 'lighweight
 design') you can not say A without saying B.

 That means: wp_query manipulates basic global variables that other parts
 of wordpress is affected of.

 that is the principle of a global variable.

 you can not go around it unless central parts of wordpress will be
 modularized apart from each other.

 for example having a query class (multiple instances), and having _one_
 frontend query (the main query instance) which then is check against in
 is_home() (just an example).

 anyway, I do not want to argument against your concerns, because I
 strongly feel with you. The question is where to draw the line.

 Maybe this bug should be tagged "architectural-changes"?

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