Custom post type queries in Wordpress - Step-by-Step Execution

Concept Flow - Custom post type queries

Define query args

↓

Call WP_Query with args

↓

Check if posts found?

No→Show no posts message

Yes↓

Loop through posts

↓

Display post data

↓

End loop

↓

Reset post data

This flow shows how WordPress runs a custom post type query: set arguments, run query, check results, loop posts, display, then reset.

Execution Sample

Wordpress

<?php
$args = ['post_type' => 'book', 'posts_per_page' => 2];
$query = new WP_Query($args);
if ($query->have_posts()) {
  while ($query->have_posts()) {
    $query->the_post();
    the_title();
  }
}
wp_reset_postdata();

This code queries 2 posts of type 'book' and shows their titles.

Execution Table

Step	Action	Evaluation/Condition	Result/Output
1	Define query args	post_type = 'book', posts_per_page = 2	Args ready for query
2	Create WP_Query object	Run query with args	Query object with posts found = true
3	Check have_posts()	Are there posts? Yes	Enter loop
4	Loop iteration 1	the_post() sets current post	Post 1 title displayed
5	Loop iteration 2	the_post() sets current post	Post 2 title displayed
6	Loop iteration 3	have_posts() false	Exit loop
7	Reset post data	wp_reset_postdata()	Global post restored

💡 No more posts found after 2 iterations, loop ends

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	Final
$args	empty	{post_type:'book', posts_per_page:2}	{post_type:'book', posts_per_page:2}	{post_type:'book', posts_per_page:2}	{post_type:'book', posts_per_page:2}
$query->current_post	null	-1	0 (first post)	1 (second post)	1
$query->found_posts	null	>=2	>=2	>=2	>=2

Key Moments - 2 Insights

Why do we need to call wp_reset_postdata() after the loop?

Because inside the loop the_post() changes global post data. wp_reset_postdata() restores it to avoid side effects, as shown in step 7 of the execution_table.

What happens if have_posts() returns false at the start?

The loop is skipped and no posts are displayed. This is shown in step 3 where the condition controls entering the loop.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of $query->current_post after step 5?

A 1 (second post)

B 2 (third post)

C 0 (first post)

D null (no post)

💡 Hint

Check the variable_tracker row for $query->current_post after step 5

At which step does the loop exit because no more posts are found?

A Step 4

B Step 6

C Step 3

D Step 7

💡 Hint

Look at the execution_table row where have_posts() returns false

If posts_per_page was set to 1, how would the execution table change?

A Loop would run 2 iterations as before

B No posts would be found

C Loop would run only 1 iteration before exiting

D Reset post data would be skipped

💡 Hint

posts_per_page limits posts returned, affecting loop iterations in execution_table

Concept Snapshot

Custom post type queries use WP_Query with 'post_type' in args.
Check have_posts() before looping.
Inside loop, call the_post() to set current post.
Display post data (e.g., the_title()).
After loop, call wp_reset_postdata() to restore globals.

Full Transcript

This visual execution trace shows how WordPress handles custom post type queries. First, you define query arguments including the post type and number of posts. Then, WP_Query runs the query and returns posts if found. The code checks if posts exist with have_posts(). If yes, it loops through each post, setting the current post with the_post() and displaying its title. After all posts are processed, the loop ends when have_posts() returns false. Finally, wp_reset_postdata() is called to restore the global post data to avoid side effects. Variables like current_post and found_posts update during the loop. This step-by-step helps beginners see how the query runs and why each function call matters.