$ GLOBALS ['wp_the_query'] frente a $ wp_query global

Te hasperdido uno,$GLOBALS['wp_query']. Atodos losefectos,$GLOBALS['wp_query'] === $wp_query. $GLOBALS['wp_query']es,sinembargo,mejorpara la legibilidad y debe usarseen lugar de $wp_query,PERO,eso sigue siendo unapreferenciapersonal

Ahora,en unmundoperfecto donde los unicorniosgobiernanelmundo,$GLOBALS['wp_the_query'] === $GLOBALS['wp_query'] === $wp_query. Por defecto,esto debería ser cierto. Simiramos dónde seestablecenestosglobales ( wp-settings.php ),verá queel objeto de consultaprincipalestá almacenadoen $GLOBALS['wp_the_query'] y $GLOBALS['wp_query']es solo una copia duplicada de $GLOBALS['wp_the_query']

 /**
 * WordPress Query object
 * @global WP_Query $wp_the_query
 * @since 2.0.0
 */
$GLOBALS['wp_the_query'] = new WP_Query();
/**
 * Holds the reference to @see $wp_the_query
 * Use this global for WordPress queries
 * @global WP_Query $wp_query
 * @since 1.5.0
 */
$GLOBALS['wp_query'] = $GLOBALS['wp_the_query'];
 

La razónpara hacerlo deestamaneraesporque WordPress vio la llegada de query_posts en la versión 1.5.

 function query_posts($query) {
    $GLOBALS['wp_query'] = new WP_Query();
    return $GLOBALS['wp_query']->query($query);
}
 

Comopuede ver,query_postsestableceel objeto de consultaprincipalen la consultapersonalizada actual que seestáejecutando. Esto rompe laintegridad del objeto de consultaprincipal,lo que leproporciona datosincorrectos,por lo que cualquier cosa que sebaseen el objeto de consultaprincipal se rompe debido a datosincorrectos.

Unaforma de contrarrestarestofue crear otroglobalpara almacenarel objeto de consultaprincipal,$GLOBALS['wp_the_query'] que seintrodujoen la versión 2.0.0. Estenuevoglobal contieneel objeto de consultaprincipal y $GLOBALS['wp_query'] solo una copia. Através de wp_reset_query(),ahorapodríamos restablecer $GLOBALS['wp_query'] al objeto de consultaprincipal originalpara restaurar suintegridad.

Peroestenoes unmundoperfecto,y query_posts sonelmismo diablo. Aunque haymiles de advertencias,lagente todavía usa query_posts. Además de romper la consultaprincipal,vuelve aejecutar la consultaprincipal,haciéndolamuchomás lenta que una consultapersonalizadanormal con WP_Query. Muchagente tampoco restablece la consulta query_posts con wp_reset_query() cuandotermina,lo que hace que query_posts sea aúnmásmaligno.

Porquenopodemos hacernada al respecto,ynopodemosevitar que los complementos ytemas usen query_posts ynuncapodremos saber si una consulta de query_posts se restableció con wp_reset_query(),necesitamos una copiamás confiable del objeto de consultaprincipal que sabemos quenos dará un 99,99999% de datos correctos yfiables. Ahíes donde $GLOBALS['wp_the_query']es útil ya queningún código relacionado con WordPresspuede cambiar su valor (excepto através de losfiltros y acciones dentro de WP_Querymismo ).

Prueba rápida,ejecute lo siguiente

 var_dump( $GLOBALS['wp_the_query'] );
var_dump( $GLOBALS['wp_query'] );

query_posts( 's=crap' );


var_dump( $GLOBALS['wp_the_query'] );
var_dump( $GLOBALS['wp_query'] );
 

y verifique los resultados. $GLOBALS['wp_the_query']no cambió,y $GLOBALS['wp_query'] sí. Entonces,¿cuálesmás confiable?

Notafinal,$GLOBALS['wp_the_query'] NO es un reemplazo de wp_reset_query(). wp_reset_query() debe siempre usarse con query_posts,y query_posts nunca debe usarse usado.

PARA CONCLUIR

Sinecesita un código confiable que casi siemprefallará,use $GLOBALS['wp_the_query'],si confía y creeen los complementos yel código deltema y cree quenadie usa query_posts o loestá usando correctamente,use $GLOBALS['wp_query'] o $wp_query

EDICIÓN IMPORTANTE

Alestar respondiendopreguntasen este sitio durante unpar de años,vi amuchos usuarios usar $wp_query como variable local,que a su veztambién rompeel objeto de consultaprincipal. Esto aumenta aúnmás la vulnerabilidad del $wp_query.

Comoejemplo,algunaspersonas aesto

 $wp_query = new WP_Query( $args );
 

queen esenciaesexactamente lomismo que query_postsestán haciendo

You have missed one, $GLOBALS['wp_query']. For all purposes, $GLOBALS['wp_query'] === $wp_query. $GLOBALS['wp_query'] is however better for readability and should be used instead of $wp_query, BUT, that remains personal preference

Now, in a perfect world where unicorns rule the world, $GLOBALS['wp_the_query'] === $GLOBALS['wp_query'] === $wp_query. By default, this should be true. If we look at where these globals are set (wp-settings.php), you will see the main query object is stored in $GLOBALS['wp_the_query'] and $GLOBALS['wp_query'] is just a duplicate copy of $GLOBALS['wp_the_query']

/**
 * WordPress Query object
 * @global WP_Query $wp_the_query
 * @since 2.0.0
 */
$GLOBALS['wp_the_query'] = new WP_Query();
/**
 * Holds the reference to @see $wp_the_query
 * Use this global for WordPress queries
 * @global WP_Query $wp_query
 * @since 1.5.0
 */
$GLOBALS['wp_query'] = $GLOBALS['wp_the_query'];

The reason for doing it this way, is because WordPress saw the arrival of query_posts in version 1.5.

function query_posts($query) {
    $GLOBALS['wp_query'] = new WP_Query();
    return $GLOBALS['wp_query']->query($query);
}

As you can see, query_posts sets the main query object to the current custom query beign run. This breaks the integrity of the main query object, which gives you incorrect data, so anything that relies on the main query object is broken due to wrong data.

A way to counter this was to create another global to store the main query object, $GLOBALS['wp_the_query'] which was introduced in version 2.0.0. This new global hold the main query object and $GLOBALS['wp_query'] just a copy. Through wp_reset_query(), we could now reset $GLOBALS['wp_query'] back to the original main query object to restore its integrity.

But this is not a perfect world, and query_posts are the devil himself. Although thousands of warnings, people still use query_posts. Apart from breaking the main query, it reruns the main query, making it much slower as a normal custom query with WP_Query. Many people also do not reset the query_posts query with wp_reset_query() when done, which makes query_posts even more evil.

Because we cannot do anything about that, and cannot stop plugins and themes from using query_posts and we can never know if a query_posts query was reset with wp_reset_query(), we need a more reliable copy of the main query object which we know will give us 99.99999% reliable, correct data. That is where $GLOBALS['wp_the_query'] is useful as no WordPress related code can change it's value (except through the filters and actions inside WP_Query itself).

Quick proof, run the following

var_dump( $GLOBALS['wp_the_query'] );
var_dump( $GLOBALS['wp_query'] );

query_posts( 's=crap' );


var_dump( $GLOBALS['wp_the_query'] );
var_dump( $GLOBALS['wp_query'] );

and check the results. $GLOBALS['wp_the_query'] did not change, and $GLOBALS['wp_query'] has. So which is more reliable?

Final note, $GLOBALS['wp_the_query'] is NOT a replacement for wp_reset_query(). wp_reset_query() should always be used with query_posts, and query_posts should never be used.

TO CONCLUDE

If you need reliable code which will almost always never fail, use $GLOBALS['wp_the_query'], if you trust and believe plugins and theme code and believe no one uses query_posts or is using it correctly, use $GLOBALS['wp_query'] or $wp_query

IMPORTANT EDIT

Being answering questions on this site now for a couple of years, I saw many users using $wp_query as a local variable, which in turn also breaks the main query object. This further increases the vulnerabilty of the $wp_query.

As example, some people to this

$wp_query = new WP_Query( $args );

which is in essence the exactly the same as what query_posts are doing

Lapalabra claveglobalimporta la variable al ámbito local,mientras que $ GLOBALS solo le otorga acceso a la variable.

Para ampliar,si usa global $wp_the_query; puede usar $wp_the_query dentro del ámbito local sin usar lapalabraglobalnuevamente.Entonces,básicamente,global $wp_the_query sepuede comparar con $wp_the_query = $GLOBALS['wp_the_query']

<×EDIT

Leímal wp_querypara wp_the_query,por lo quemi respuestanoes una respuesta completa a lapregunta,pero aúnproporcionainformacióngeneral sobre la diferenciaentre global $variable y $GLOBALS['variable']

The global keyword imports the variable into the local scope, while $GLOBALS just grants you access to the variable.

To elaborate, if you use global $wp_the_query; you can use $wp_the_query inside the local scope without using the word global again. So basically global $wp_the_query can be compared to $wp_the_query = $GLOBALS['wp_the_query']

EDIT

I misread wp_query for wp_the_query so my answer isn't a complete answer to the question but still provides general information about the difference between global $variable and $GLOBALS['variable']

Básicamente,unoes copia del otro.Consulte wp-settings.php ,líneas 292-305:

 $GLOBALS['wp_the_query'] = new WP_Query();

$GLOBALS['wp_query'] = $GLOBALS['wp_the_query'];
 

Basically one is copy of the other. Check out wp-settings.php, lines 292-305:

$GLOBALS['wp_the_query'] = new WP_Query();

$GLOBALS['wp_query'] = $GLOBALS['wp_the_query'];