You don’t need the type variable and other bits of custom search query code, or custom functions like the other answers. In your searchbox, instead of submitting the form to / submit it to /my_post_type/ instead! WordPress will handle all the rest for you automagically, with no effort involved. What’s more this means all the … Read more
You set offset param, so paged param is ignored 😉 From Codex: offset (int) – number of post to displace or pass over. Warning: Setting the offset parameter overrides/ignores the paged If you want to ignore most recent post in this query, you can achieve it in two ways. 1. Custom pagination. $ppp = get_option(‘posts_per_page’); … Read more
Alright, I’ve solved the problem. Turns out that you should never use action=”” for searchform.php. It will work perfectly fine in terms of search results, but it will break the pagination, when using 3.1. Instead, you should use for the form action.
Ok this was really tricky. I have so far managed to work around it by lying to the WordPress global $wp_query. Here is how. In your theme’s functions.php you can add these functions to show 7 posts on first page, and 9 posts on any other page. Okay, that code works so far but you’ll … Read more
The rewrite API won’t redirect – it just “maps” URL structures to query strings – you’ll need to do this yourself. First things first, fix that rewrite rule: ‘episode/([^/]+)/transcript’; // Matches anything that follows transcript, not what we want! ‘episode/([^/]+)/transcript/?$’; // Matches only “episode/name/transcript”, optionally with a trailing slash Now bring in a helper function: … Read more
The solution is to not alter the main query in the template. The default query happens before the template is loaded, so querying in the template overwrites that original query, which is a waste of resources. See the example in codex under pre_get_posts for the correct way to alter the default query without pagination issues.
I found the solution. I was looking for: $wp_query->post_count And some of my assumptions were not correct. This is the actual output: Total posts from the loop 22. Posts per page 10. 1 sticky post. Page 1 gives 10 (9 + 1 sticky). Page 2 gives 10. Page 3 gives 2.
should it be.. $paged = (get_query_var(‘page’)) ? get_query_var(‘page’) : 1; WP_Query in codex: Pagination Note: You should set get_query_var( ‘page’ ); if you want your query to work with pagination. Since WordPress 3.0.2, you do get_query_var( ‘page’ ) instead of get_query_var( ‘paged’ ). The pagination parameter ‘paged’ for WP_Query() remains the same.
I hope you understand what query variables is. If not, here is it in short. The main query uses WP_Query to set itself up. In the main query, WP_Query uses public query variables to construct the main query according to the page being requested, and paged and page are two of them. To see all … Read more
twentyeleven_content_nav() uses the main query object, $wp_query. You’ll need to use the $wp_query variable, rather than $unfiltered_query, then wp_reset_query() to restore the original $wp_query (which it’ll find in $wp_the_query, something you should probably avoid touching directly). As long as you’re careful to restore the original query, you’re in good shape. I would submit a patch … Read more