ok, i still don’t love the idea of a second query, but you’re right it is hard to add content to the archives pages. there were 3 problems that i found: next_posts_link and previous_posts_link both echo, you need their get_ equivalents. when you look up get_next_posts_link, you find that it relies on the global $wp_query… … Read more
Thanks to s_ha_dum for the tip. I managed to solve it by setting the offset parameter in the special case of 2nd page onwards for the front page as follows: function limit_posts_per_home_page() { $paged = (get_query_var(‘paged’)) ? get_query_var(‘paged’) : 1; $first_page_limit = 5; $limit = get_option(‘posts_per_page’); if (is_front_page()) { if ($paged == 1) { $limit … Read more
You’re running into a conflict between your replacement query and the default search query that’s running behind the scenes. Instead of running a new WP_Query, try modifying the default query by hooking to pre_get_posts: function wpse276396_search_filter($query) { if ( !is_admin() && $query->is_main_query() ) { if ($query->is_search) { $text = urldecode( get_query_var(‘search_text’) ); $my_products = aws_search_byozan($text); … Read more
This is a local/global variable problem. It can be solved either by changing the pagination function to work with local variable, or by promoting the local variable into global scope. As you are using wp_reset_postdata(), i guess you want to keep the original query. Change the pagination function to accept arguments – if ( ! … Read more
If it can help anyone, here is the full answer with the issues that might happen when you want to add WordPress pagination with anchors to a template page. STEP 1 Follow the example on the Codex so that the paginate_links() function applies to your custom query and not to the main query. STEP 2 … Read more
EDIT I have played around with a possible solution to your issue. We can try the following Add our own action to template_redirect where we do the following Check that the current request is a paged single post page and that we do not have the <!–nextpage–> tag in the post content. If everything checks … Read more
The problem is that WordPress is executing the main query before your custom query (and the main query is based on the default post type only). You can intercept the main query, modify it, and then use it like so function add_blog_post_to_query( $query ) { if ( $query->is_home() && $query->is_main_query() ) { $query->set( ‘post_type’, array(‘post’, … Read more
The functions accept an $in_same_cat argument, the default value of which is false. Just set that to true. previous_post_link($format, $link, true); next_post_link($format, $link, true);
You can find this info in the global vars $multipage, $numpages, and $page global $multipage, $numpages, $page; if( $multipage && $page == $numpages ) echo ‘last page’;
This is working for me on a single page using a template. Just be sure to set next_posts_link( ‘Older Entries »’, $the_query->max_num_pages );. // set the “paged” parameter (use ‘page’ if the query is on a static front page) $paged = ( get_query_var( ‘paged’ ) ) ? get_query_var( ‘paged’ ) : ‘1’; $args = array … Read more