Erreur de pagination de catégorie de type d'article personnalisée WordPress 404

Question

Erreur de pagination de catégorie de type d'article personnalisée WordPress 404

1

1828 2013-08-06

Ceproblèmeme donnemal à latêteet jeme demandais si quelqu'un savait comment le résoudre.

J'ai untype demessagepersonnalisé appelé Examen. Voici commentilest défini:

 function codex_custom_init() {
    $args = array( 'rewrite' => array('slug' => 'review'), 
                    'public' => true, 
                    'has_archive' => true, 
                    'show_ui' => true,
                    'label' => 'Review', 
                    'publicly_queryable' => true,
                    'taxonomies' => array('category', 'post_tag'), 
                    'supports' => array( 'title', 'editor', 'comments', 'excerpt', 'custom-fields', 'thumbnail', 'author')
                  );
    register_post_type( 'review', $args );
}

add_action( 'init', 'codex_custom_init' );

Mapage d'archive,géréepar archive-review.php,fonctionnebien pour despages comme celle-ci

 http://www.acme.com/review/page/3/

Cependant,lorsque des catégories sontimpliquées,wordpressn'affichepas lapage "suivante". Au lieu de cela,il va à un 404. Parexemple,lorsquej'essaye d'accéder à ceci:

 http://www.acme.com/category/random/page/2/

Pourquoi cela donne-t-il un 404? Deplus,iln'estplus alimentépar archive-review.php,mais archive.php (ce qui a du sensje suppose)

trucs de requête archive.php:

 $paged = (get_query_var('paged')) ? get_query_var('paged') : 1;
        $cat = get_category(get_query_var('cat'));
        $catID = $cat->term_id;
        $args = (array('post_type' => array('post', 'review'), 'cat' => $catID, 'paged' => $paged));
        query_posts($args);

Veuillez aider !! Je suistrèsfrustré!

This problem is giving me a headache and I was wondering if anyone knew how to fix it.

I have a custom post type called Review. Here is how it is defined:

function codex_custom_init() {
    $args = array( 'rewrite' => array('slug' => 'review'), 
                    'public' => true, 
                    'has_archive' => true, 
                    'show_ui' => true,
                    'label' => 'Review', 
                    'publicly_queryable' => true,
                    'taxonomies' => array('category', 'post_tag'), 
                    'supports' => array( 'title', 'editor', 'comments', 'excerpt', 'custom-fields', 'thumbnail', 'author')
                  );
    register_post_type( 'review', $args );
}

add_action( 'init', 'codex_custom_init' );

My archive page, handled by archive-review.php, works fine for pages like this

http://www.acme.com/review/page/3/

However, when categories are involved, wordpress does not display the "next" page. Instead, it goes to a 404. For example, when I try to access this:

http://www.acme.com/category/random/page/2/

Why does that give a 404? Also, it no longer is powered by archive-review.php, but archive.php (which makes sense I guess)

archive.php query stuff:

$paged = (get_query_var('paged')) ? get_query_var('paged') : 1;
        $cat = get_category(get_query_var('cat'));
        $catID = $cat->term_id;
        $args = (array('post_type' => array('post', 'review'), 'cat' => $catID, 'paged' => $paged));
        query_posts($args);

Please help!! I am very frustrated!

- `http://www.acme.com/category/random/page/2/`est-ce que le hasardest unefaute defrappe?
  
  `http://www.acme.com/category/random/page/2/` is random a typo?
  - 0
  - 2013-08-06
  - vancoder
- Avez-vous vu http://wordpress.stackexchange.com/questions/4696/pagination-not-working-with-custom-loopet http://wordpress.stackexchange.com/questions/1753/when-should-you-use-wp-query-vs-query-posts-vs-get-posts?
  
  Have you seen http://wordpress.stackexchange.com/questions/4696/pagination-not-working-with-custom-loop and http://wordpress.stackexchange.com/questions/1753/when-should-you-use-wp-query-vs-query-posts-vs-get-posts?
  - 0
  - 2013-08-06
  - fuxia
- @vancoder randomest le slug de catégorie dans cetexemple
  
  @vancoder random is the category slug in this example
  - 0
  - 2013-08-06
  - 21zna9
- @toscho Je vais l'essayeren créant unnouveau wp_query comme l'exemple quej'ai vu sur CSS Tricks,maisje ne saispaspourquoi celaferait une différence caril s'agit de laboucle de requête "principale"et donc query_posts () devrait êtreen vigueur...
  
  @toscho I will try it with creating a new wp_query as the example i've seen on CSS Tricks, but I'm not sure why that would make a difference as this is the "main" query loop and therefore query_posts() should be applicable...
  - 0
  - 2013-08-06
  - 21zna9
- Simplemaisimportant,avez-vous vidé vospermaliens?
  
  Simple but important, did you flush your permalinks?
  - 0
  - 2013-08-06
  - Nathan Powell
- Voir [cette réponse] (https://wordpress.stackexchange.com/a/250944/9579)pour une autre solutionpossiblepour lapaginationnumérique avec des requêtespersonnalisées utilisant `WP_Query ();`.
  
  See [this answer](https://wordpress.stackexchange.com/a/250944/9579) for another possible solution for Numerical Pagination with custom queries using `WP_Query();`.
  - 0
  - 2017-04-18
  - Michael Ecklund

1 réponses

votes

s_ha_dum · Answer 1 · 2013-08-06

4

2013-08-06

La création d'une requête secondaire ou l'écrasement de la requêteprincipale dans unmodèle depageest lemoyen leplus rapideet leplus simple queje connaissepourinterrompre lapagination.

La requêteprincipale,qui détermine quellepage charger s'exécute avant votremodèle ainsi les résultats sur lapageet la requête qui charge lapage deviennent désynchronisés. La requêteprincipalene connaîtpas vosmodifications dans lemodèle de la requête. Peuimporte que votre requête dans lemodèlemodifie la requête "principale". Les changements arriventtroptard.

Ce que vous devezfaire,c'est utiliser unfiltre sur pre_get_posts. Sauferreur de lecture,tout ce que vous avez àfaireest de définir le post_status.

 function set_post_type_for_archive_wpse_109213($qry) {
  if ($qry->is_archive()) {
    $post_type = $qry->get('post_type');
    if (empty($post_type)) {
      $post_type = array('post');
    }
    $post_type[] = 'review';
    $qry->set('post_type',  $post_type);
  }
}
add_action('pre_get_posts','set_post_type_for_archive_wpse_109213');

Àmoins que vousne soyez lenoyau de WordPress,et que vousne l'êtespas,query_postsn'estjamais applicable. Ne l'utilisezpas.

Creating a secondary query or overwriting the main query inside a page template is the quickest and easiest way I know to break pagination.

The main query, which determines which page to load runs before your template thus the results on the page and the query that loads the page become out of sync. The main query does not know about your in-template modifications to the query. It doesn't matter that your in-template query modifies the "main" query. The changes come too late.

What you need to be doing is use a filter on pre_get_posts. Unless I am reading it wrong, all you need to do is set the post_status.

function set_post_type_for_archive_wpse_109213($qry) {
  if ($qry->is_archive()) {
    $post_type = $qry->get('post_type');
    if (empty($post_type)) {
      $post_type = array('post');
    }
    $post_type[] = 'review';
    $qry->set('post_type',  $post_type);
  }
}
add_action('pre_get_posts','set_post_type_for_archive_wpse_109213');

Unless you are the WordPress Core, and you aren't, query_posts is never applicable. Just don't use it.

Jene saispaspourquoi @ 21zna9n'apas accepté cette réponse.Cette réponsem'a aidé.+1pour s_ha_dum

Don't know why @21zna9 didn't accept this answer. This answer helped me. +1 for s_ha_dum
- 0
- 2014-01-14
- IFightCode