It appears that you want to create a custom page template to display a custom post type? If so, you don’t really need to mess with pre_get_posts at all. First, create your custom page template. I assume you’ve already done this. Second, you need to create a custom query, using WP_Query(): global $post; $types = … Read more
This should work, but I haven’t tested it: global $wp_query; $page = ( get_query_var(‘paged’) ) ? get_query_var(‘paged’) : 1; $ppp = get_query_var(‘posts_per_page’); $end = $ppp * $page; $start = $end – $ppp + 1; $total = $wp_query->found_posts; echo “Showing posts $start through $end of $total total.”;
In line 51: query_posts(“s=”$s”&cat=177”); change to this: $paged = (get_query_var(‘paged’)) ? get_query_var(‘paged’) : 1; query_posts(“s=”$s”&cat=177&paged=$paged”);
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.
You’re overwriting the main query with a new query where you don’t specify any tag parameters, which is why you’re seeing all posts and not those specific to the tag you’re viewing. The answer- Do not modify the main query in the template. There’s almost never a legitimate reason to have to modify the main … Read more
Static pages doesn’t work with paged query variable, they need the page variable. This is the reason why your second code block makes the query work: it uses the page var when available. However, your paginated links code always use paged: … ‘format’ => ‘?paged=%#%’, … So you are sending paged query var but looking … Read more
You have a few issues here The following piece of code is wrong and unnecessary $category = get_post(); $category = $category->post_title; The current page object is saved in get_queried_object(), so you can use this function to get your post title. Also, post_title is not the correct property to use here. You want to look at … Read more
You can try to use the the_post filter, to override the content pagination, that takes place within the setup_postdata() function ( PHP 5.4+ ): /** * Ignore the <!–nextpage–> for content pagination. * * @see http://wordpress.stackexchange.com/a/183587/26350 */ add_action( ‘the_post’, function( $post ) { if ( false !== strpos( $post->post_content, ‘<!–nextpage–>’ ) ) { // Reset … Read more
Don’t use query_posts. This is a classic example of what happens when you do 🙂 Basically, when WordPress receives an url, it interprets this as a query – it then queries the database to find the results (if any) and serves up an appropriate template (such as 404.php in the case of no results). If … Read more
Try changing the page’s slug to something else and changing your post type registration to this: $args = array( ‘labels’ => $labels, ‘public’ => true, ‘publicly_queryable’ => true, ‘has_archive’ => true, ‘show_ui’ => true, ‘rewrite’ => array(‘slug’ => ‘properties’, ‘with_front’ => false), ‘query_var’ => true, ‘capability_type’ => ‘post’, ‘hierarchical’ => false, ‘show_in_nav_menus’ => false, ‘menu_position’ … Read more