Never use new WP_Query for the main query of an archive template. WordPress has already queried the correct posts and things like pagination are based on that query. If you want to modify that query you should use the pre_get_posts to modify the main query before it is run. The hook runs on every query … Read more
The issue I’m having is with the pagination on category pages, e.g. /release-notes/category/upgrades/, where pages 2 and beyond return a 404. That’s because your custom rewrite rule does not support paged requests, i.e. it’s missing the RegEx ( regular expression pattern ) and query for the paged parameter. So you can either add another rewrite … Read more
It looks like you’ve attempted to replace the default WP_Query object for your search page by instantiating a new WP_Query object. This has two main effects: firstly you’re hitting the database twice completely unnecessarily, slowing down the page execution; and secondly default template functionality like pagination depends on the default query for the page rather … Read more
By default paginate_links() gives you several ways to target the current page: It will replace the a element with a span element, because there’s no point in a page linking to itself It adds the class current to the span It adds the aria-current attribute to the span Any one of these can be used … Read more
Okay, so why doesn’t this work: The Filter you are using is the posts_results, which is a filter that is applied AFTER the Results are retrieved from the database. Which has the problem that you are describing: Ordering happens on a page-per-page basis. What you want to do is add an order TO the SQL-Query, … Read more
The numberposts argument is not supported by WP_Query, the solution to the above question was to use instead posts_per_page.
You registered your post type correctly, the problem is a common pitfall many new WordPress developers fall into, you created a second new query to change the posts WP displays, rather than modifying the original. Why It’s Broken A lot of people don’t understand the main query and think that if they want to change … Read more
The root of the problem is that you’re using s, the post query search parameter, but the code is for a user query. This means if your user query has 5 pages, but only 2 pages of posts are found, page 3 will 404. Instead, use a dedicated parameter with $_GET that isn’t a reserved … Read more
Zeroise custom pagination to have leading 0
Why Does It Happen? It’s because the number of pages in your second WP_Query is large the number of pages in the main query. So if there are 8 jobs, that’s 4 pages in your custom query, and 1 page in the main query. So when you go to page 2 there is no page … Read more