问题描述
我对 pre_get_posts 在真实页面和静态首页上的使用做了相当广泛的研究，似乎没有愚蠢的方法。
我发现的最好的选择是从 post done by @birgire on Stackoverflow 。我已经将其重写成一个演示类，并使代码更有活力
class PreGeTPostsForPages
{
/**
* @var string|int $pageID
* @access protected
* @since 1.0.0
*/
protected $pageID;
/**
* @var bool $injectPageIntoLoop
* @access protected
* @since 1.0.0
*/
protected $injectPageIntoLoop;
/**
* @var array $args
* @access protected
* @since 1.0.0
*/
protected $args;
/**
* @var int $validatedPageID
* @access protected
* @since 1.0.0
*/
protected $validatedPageID = 0;
/**
* Constructor
*
* @param string|int $pageID = NULL
* @param bool $injectPageIntoLoop = false
* @param array| $args = []
* @since 1.0.0
*/
public function __construct(
$pageID = NULL,
$injectPageIntoLoop = true,
$args = []
) {
$this->pageID = $pageID;
$this->injectPageIntoLoop = $injectPageIntoLoop;
$this->args = $args;
}
/**
* Private method validatePageID()
*
* Validates the page ID passed
*
* @since 1.0.0
*/
private function validatePageID()
{
$validatedPageID = filter_var( $this->pageID, FILTER_VALIDATE_INT );
$this->validatedPageID = $validatedPageID;
}
/**
* Public method init()
*
* This method is used to initialize our pre_get_posts action
*
* @since 1.0.0
*/
public function init()
{
// Load the correct actions according to the value of $this->keepPageIntegrity
add_action( 'pre_get_posts', [$this, 'preGetPosts'] );
}
/**
* Protected method pageObject()
*
* Gets the queried object to use that as page object
*
* @since 1.0.0
*/
protected function pageObject()
{
global $wp_the_query;
return $wp_the_query->get_queried_object();
}
/**
* Public method preGetPosts()
*
* This is our call back method for the pre_get_posts action.
*
* The pre_get_posts action will only be used if the page integrity is
* not an issue, which means that the page will be altered to work like a
* normal archive page. Here you have the option to inject the page object as
* first post through the_posts filter when $this->injectPageIntoLoop === true
*
* @since 1.0.0
*/
public function preGetPosts( WP_Query $q )
{
// Make sure that we are on the main query and the desired page
if ( is_admin() // Only run this on the front end
|| !$q->is_main_query() // Only target the main query
|| !is_page( $this->validatedPageID ) // Run this only on the page specified
)
return;
// Remove the filter to avoid infinte loops
remove_filter( current_filter(), [$this, __METHOD__] );
// METHODS:
$this->validatePageID();
$this->pageObject();
$queryArgs = $this->args;
// Set default arguments which cannot be changed
$queryArgs['pagename'] = NULL;
// We have reached this point, lets do what we need to do
foreach ( $queryArgs as $key=>$value )
$q->set(
filter_var( $key, FILTER_SANITIZE_STRING ),
$value // Let WP_Query handle the sanitation of the values accordingly
);
// Set $q->is_singular to 0 to get pagination to work
$q->is_singular = false;
// FILTERS:
add_filter( 'the_posts', [$this, 'addPageAsPost'], PHP_INT_MAX );
add_filter( 'template_include', [$this, 'templateInclude'], PHP_INT_MAX );
}
/**
* Public callback method hooked to 'the_posts' filter
* This will inject the queried object into the array of posts
* if $this->injectPageIntoLoop === true
*
* @since 1.0.0
*/
public function addPageAsPost( $posts )
{
// Inject the page object as a post if $this->injectPageIntoLoop == true
if ( true === $this->injectPageIntoLoop )
return array_merge( [$this->pageObject()], $posts );
return $posts;
}
/**
* Public call back method templateInclude() for the template_include filter
*
* @since 1.0.0
*/
public function templateInclude( $template )
{
// Remove the filter to avoid infinte loops
remove_filter( current_filter(), [$this, __METHOD__] );
// Get the page template saved in db
$pageTemplate = get_post_meta(
$this->validatedPageID,
'_wp_page_template',
true
);
// Make sure the template exists before we load it, but only if $template is not 'default'
if ( 'default' !== $pageTemplate ) {
$locateTemplate = locate_template( $pageTemplate );
if ( $locateTemplate )
return $template = $locateTemplate;
}
/**
* If $template returned 'default', or the template is not located for some reason,
* we need to get and load the template according to template hierarchy
*
* @uses get_page_template()
*/
return $template = get_page_template();
}
}
$init = new PreGeTPostsForPages(
251, // Page ID
false,
[
'posts_per_page' => 3,
'post_type' => 'post'
]
);
$init->init();
通过使用 my own pagination function，这样可以很好地预览页面。
问题：
由于功能，我松散页面完整性其他功能依赖于存储在 $post 中的页面对象。 $post 在循环之前设置为循环中的第一个后，$post 设置为循环后的最后一个循环，这是预期的。我需要的是将 $post 设置为当前页面对象，即查询对象。
此外，$wp_the_query->post 和 $wp_query->post 保存循环中的第一个帖子，而不是正常页面上的查询对象
我使用以下 (我的课外) 来检查循环之前和之后的全局变量
add_action( 'wp_head', 'printGlobals' );
add_action( 'wp_footer', 'printGlobals' );
function printGlobals()
{
$global_test = 'QUERIED OBJECT: ' . $GLOBALS['wp_the_query']->queried_object_id . '</br>';
$global_test .= 'WP_THE_QUERY: ' . $GLOBALS['wp_the_query']->post->ID . '</br>';
$global_test .= 'WP_QUERY: ' . $GLOBALS['wp_query']->post->ID . '</br>';
$global_test .= 'POST: ' . $GLOBALS['post']->ID . '</br>';
$global_test .= 'FOUND_POSTS: ' . $GLOBALS['wp_query']->found_posts . '</br>';
$global_test .= 'MAX_NUM_PAGES: ' . $GLOBALS['wp_query']->max_num_pages . '</br>';
?><pre><?php var_dump( $global_test ); ?></pre><?php
}
在循环之前：
在循环之前，通过将 $injectPageIntoLoop 设置为 true 来部分解决问题，将页面对象注入循环中的第一页。如果您需要在所请求的帖子之前显示页面信息，那么这是非常有用的，但如果您不想要的话，您将被拧紧。
我可以通过直接黑客全局变量在循环之前解决问题，我不太喜欢。我将以下方法钩在我的 preGetPosts 方法中
public function wp()
{
$page = get_post( $this->pageID );
$GLOBALS['wp_the_query']->post = $page;
$GLOBALS['wp_query'] = $GLOBALS['wp_the_query'];
$GLOBALS['post'] = $page;
}
并在 preGetPosts 方法内
add_action( 'wp', [$this, 'wp'] );
从此，$wp_the_query->post，$wp_query->post 和 $post 都保存页面对象。
循环后
这是我的大问题，循环之后。通过 wp 钩子和方法对全局变量进行攻击后，
-
$wp_the_query->post和$wp_query->post设置回循环中的第一个帖子，如预期 -
$post设置为循环中的最后一个帖子。
我需要的是所有三个都被设置回查询对象/当前页面对象。
我尝试将 wp 方法挂接到 loop_end 操作，这不行。将 wp 方法挂接到 get_sidebar 操作中，但是为时已晚。
add_action( 'get_sidebar', [$this, 'wp'] );
在模板循环后直接运行 printGlobals()确认为 $wp_the_query->post 和 $wp_query->post 仍然设置为第一个帖子，$post 为最后一个帖子。
在 wp 方法之后，我可以在模板中的循环之后手动添加代码，但这个想法不是直接改变模板文件，因为类应该可以在主题之间的插件中传输。
有没有正确的方法来解决这个问题，一个在真正的页面和静态首页上运行 pre_get_posts，并且在循环之前和之后仍然保持 $wp_the_query->post，$wp_query->post 和 $post(将它们设置为被查询对象) 的完整性。
EDIT
似乎有一些混乱，我需要什么，为什么我需要它
我需要的
我需要在模板中保留 $wp_the_query->post，$wp_query->post 和 $post 的值，而不管该值是查询对象。在这个阶段，使用我发布的代码，这三个变量的值不会保留页面对象，而是在循环中发布帖子的对象。我希望这是很清楚的。
我已经发布了可以用来测试这些变量的代码
为什么我需要它
我需要一种可靠的方式，通过 pre_get_posts 添加帖子到页面模板和静态前端页面，而不会改变整页功能。在这个阶段，正如所讨论的代码所示，由于 $post 拥有”wrong” 后期对象，因此在循环后会破坏我的导航特征和相关页面功能。
最重要的是，我不想直接改变页面模板。我想要能够向页面模板添加帖子，而不会对模板进行任何修改
最佳解决方案
我终于得到它的工作，但不是在我的问题的代码。我完全废弃了整个想法，重新开始向新的方向前进。
注意：
如果任何人有能力解决我的问题的问题，请随时发布答案。此外，如果您有任何其他解决方案，也可以随时发布答案。
工作类和解决方案：
我试图在这里做的是使用后期注入，而不是完全改变主查询，并遇到上述所有问题，比如直接更改全局变量，全局值问题和重新分配页面模板。
通过使用后期注入，我可以保持完整的完整性，所以 $wp_the_query->post，$wp_query->post，$posts 和 $post 在整个模板中保持不变，它们只保存当前页面对象，如真正的页面一样。这样，像面包屑这样的功能仍然认为当前页面是真实的页面，而不是某种存档
我不得不稍微改变主要查询 (通过过滤器和操作) 来调整分页，但是我们会来。
后注射查询
为了完成后期注入，我使用自定义查询返回注入所需的帖子。我还使用自定义查询的 $found_pages 属性来调整主查询的属性，以便从主查询获取分页。帖子通过 loop_end 动作注入主查询。
为了使定制查询在课外可访问和可用，我介绍了一些动作。
-
分页钩为了分页功能：
-
pregetgostsforgages_before_loop_pagination -
pregetgostsforgages_after_loop_pagination
-
-
自定义计数器，用于计算循环中的帖子。这些动作可以用来根据帖子号来改变帖子在循环内的显示方式
-
pregetgostsforgages_counter_before_template_part -
pregetgostsforgages_counter_after_template_part
-
-
一般钩子访问查询对象和当前的 post 对象
-
pregetgostsforgages_current_post_and_object
-
这些钩子为您提供了一个完整的 hands-off 体验，因为您不需要更改页面模板本身中的任何内容，这是我从一开始我的初衷。一个页面可以完全从一个插件或功能文件改变，这使得这个非常动态
我也使用 get_template_part()加载一个模板部分，用于显示帖子。今天的大多数主题都使用模板部分，这使得这在课堂上非常有用。如果您的主题使用 content.php，您可以简单地将 content 传递给 $templatePart 来加载 content.php 。
如果您需要模板部件的后期格式支持，那么很简单，您仍然可以将 content 传递给 $templatePart，并将 $postFormatSupport 设置为 true，并为 video 的后期格式加载一个模板零件 content-video.php 。
主要查询
通过相应的过滤器和操作对主查询进行了以下更改
-
为了分页主要查询：
-
注射器查询的
$found_posts属性值通过found_posts过滤器传递给主查询对象的属性值 -
通过
pre_get_posts将用户传递参数posts_per_page的值设置为主查询 -
$max_num_pages使用$found_posts和posts_per_page中的员额数量计算。因为is_singular在页面上是正确的，它禁止设置LIMIT子句。简单地将is_singular设置为 false 会导致一些问题，所以我决定通过post_limits过滤器设置LIMIT子句。我将LIMIT子句的offset设置为0，以避免页面上的 404 页面
-
这样做可以照顾分页和从后期注入可能产生的任何问题
页面对象
当前页面对象可以通过使用页面上的默认循环显示为帖子，分离和注入帖子顶部。如果不需要，可以将 $removePageFromLoop 设置为 true，这样可以隐藏页面内容的显示。
在这个阶段，我使用 CSS 通过 loop_start 和 loop_end 操作来隐藏页面对象，因为我找不到另一种方法。这种方法的缺点是，如果隐藏页面对象，任何挂钩到主查询中的 the_post 动作钩子的内容也将被隐藏。
班上
PreGetPostsForPages 类可以改进，并且应该具有适当的命名空间尽管您可以简单地将其放在主题的函数文件中，但最好将其放入自定义插件中。
使用，修改和滥用，你认为合适。代码很好评论，所以应该很容易跟进和调整
class PreGetPostsForPages
{
/**
* @var string|int $pageID
* @access protected
* @since 1.0.0
*/
protected $pageID;
/**
* @var string $templatePart
* @access protected
* @since 1.0.0
*/
protected $templatePart;
/**
* @var bool $postFormatSupport
* @access protected
* @since 1.0.0
*/
protected $postFormatSupport;
/**
* @var bool $removePageFromLoop
* @access protected
* @since 1.0.0
*/
protected $removePageFromLoop;
/**
* @var array $args
* @access protected
* @since 1.0.0
*/
protected $args;
/**
* @var array $mergedArgs
* @access protected
* @since 1.0.0
*/
protected $mergedArgs = [];
/**
* @var NULL|stdClass $injectorQuery
* @access protected
* @since 1.0.0
*/
protected $injectorQuery = NULL;
/**
* @var int $validatedPageID
* @access protected
* @since 1.0.0
*/
protected $validatedPageID = 0;
/**
* Constructor method
*
* @param string|int $pageID The ID of the page we would like to target
* @param string $templatePart The template part which should be used to display posts
* @param string $postFormatSupport Should get_template_part support post format specific template parts
* @param bool $removePageFromLoop Should the page content be displayed or not
* @param array $args An array of valid arguments compatible with WP_Query
*
* @since 1.0.0
*/
public function __construct(
$pageID = NULL,
$templatePart = NULL,
$postFormatSupport = false,
$removePageFromLoop = false,
$args = []
) {
$this->pageID = $pageID;
$this->templatePart = $templatePart;
$this->postFormatSupport = $postFormatSupport;
$this->removePageFromLoop = $removePageFromLoop;
$this->args = $args;
}
/**
* Public method init()
*
* The init method will be use to initialize our pre_get_posts action
*
* @since 1.0.0
*/
public function init()
{
// Initialise our pre_get_posts action
add_action( 'pre_get_posts', [$this, 'preGetPosts'] );
}
/**
* Private method validatePageID()
*
* Validates the page ID passed
*
* @since 1.0.0
*/
private function validatePageID()
{
$validatedPageID = filter_var( $this->pageID, FILTER_VALIDATE_INT );
$this->validatedPageID = $validatedPageID;
}
/**
* Private method mergedArgs()
*
* Merge the default args with the user passed args
*
* @since 1.0.0
*/
private function mergedArgs()
{
// Set default arguments
if ( get_query_var( 'paged' ) ) {
$currentPage = get_query_var( 'paged' );
} elseif ( get_query_var( 'page' ) ) {
$currentPage = get_query_var( 'page' );
} else {
$currentPage = 1;
}
$default = [
'suppress_filters' => true,
'ignore_sticky_posts' => 1,
'paged' => $currentPage,
'posts_per_page' => get_option( 'posts_per_page' ), // Set posts per page here to set the LIMIT clause etc
'nopaging' => false
];
$mergedArgs = wp_parse_args( (array) $this->args, $default );
$this->mergedArgs = $mergedArgs;
}
/**
* Public method preGetPosts()
*
* This is the callback method which will be hooked to the
* pre_get_posts action hook. This method will be used to alter
* the main query on the page specified by ID.
*
* @param stdClass WP_Query The query object passed by reference
* @since 1.0.0
*/
public function preGetPosts( WP_Query $q )
{
if ( !is_admin() // Only target the front end
&& $q->is_main_query() // Only target the main query
&& $q->is_page( filter_var( $this->validatedPageID, FILTER_VALIDATE_INT ) ) // Only target our specified page
) {
// Remove the pre_get_posts action to avoid unexpected issues
remove_action( current_action(), [$this, __METHOD__] );
// METHODS:
// Initialize our method which will return the validated page ID
$this->validatePageID();
// Initiale our mergedArgs() method
$this->mergedArgs();
// Initiale our custom query method
$this->injectorQuery();
/**
* We need to alter a couple of things here in order for this to work
* - Set posts_per_page to the user set value in order for the query to
* to properly calculate the $max_num_pages property for pagination
* - Set the $found_posts property of the main query to the $found_posts
* property of our custom query we will be using to inject posts
* - Set the LIMIT clause to the SQL query. By default, on pages, `is_singular`
* returns true on pages which removes the LIMIT clause from the SQL query.
* We need the LIMIT clause because an empty limit clause inhibits the calculation
* of the $max_num_pages property which we need for pagination
*/
if ( $this->mergedArgs['posts_per_page']
&& true !== $this->mergedArgs['nopaging']
) {
$q->set( 'posts_per_page', $this->mergedArgs['posts_per_page'] );
} elseif ( true === $this->mergedArgs['nopaging'] ) {
$q->set( 'posts_per_page', -1 );
}
// FILTERS:
add_filter( 'found_posts', [$this, 'foundPosts'], PHP_INT_MAX, 2 );
add_filter( 'post_limits', [$this, 'postLimits']);
// ACTIONS:
/**
* We can now add all our actions that we will be using to inject our custom
* posts into the main query. We will not be altering the main query or the
* main query's $posts property as we would like to keep full integrity of the
* $post, $posts globals as well as $wp_query->post. For this reason we will use
* post injection
*/
add_action( 'loop_start', [$this, 'loopStart'], 1 );
add_action( 'loop_end', [$this, 'loopEnd'], 1 );
}
}
/**
* Public method injectorQuery
*
* This will be the method which will handle our custom
* query which will be used to
* - return the posts that should be injected into the main
* query according to the arguments passed
* - alter the $found_posts property of the main query to make
* pagination work
*
* @link https://codex.wordpress.org/Class_Reference/WP_Query
* @since 1.0.0
* @return stdClass $this->injectorQuery
*/
public function injectorQuery()
{
//Define our custom query
$injectorQuery = new WP_Query( $this->mergedArgs );
// Update the thumbnail cache
update_post_thumbnail_cache( $injectorQuery );
$this->injectorQuery = $injectorQuery;
return $this->injectorQuery;
}
/**
* Public callback method foundPosts()
*
* We need to set found_posts in the main query to the $found_posts
* property of the custom query in order for the main query to correctly
* calculate $max_num_pages for pagination
*
* @param string $found_posts Passed by reference by the filter
* @param stdClass WP_Query Sq The current query object passed by refence
* @since 1.0.0
* @return $found_posts
*/
public function foundPosts( $found_posts, WP_Query $q )
{
if ( !$q->is_main_query() )
return $found_posts;
remove_filter( current_filter(), [$this, __METHOD__] );
// Make sure that $this->injectorQuery actually have a value and is not NULL
if ( $this->injectorQuery instanceof WP_Query
&& 0 != $this->injectorQuery->found_posts
)
return $found_posts = $this->injectorQuery->found_posts;
return $found_posts;
}
/**
* Public callback method postLimits()
*
* We need to set the LIMIT clause as it it is removed on pages due to
* is_singular returning true. Witout the limit clause, $max_num_pages stays
* set 0 which avoids pagination.
*
* We will also leave the offset part of the LIMIT cluase to 0 to avoid paged
* pages returning 404's
*
* @param string $limits Passed by reference in the filter
* @since 1.0.0
* @return $limits
*/
public function postLimits( $limits )
{
$posts_per_page = (int) $this->mergedArgs['posts_per_page'];
if ( $posts_per_page
&& -1 != $posts_per_page // Make sure that posts_per_page is not set to return all posts
&& true !== $this->mergedArgs['nopaging'] // Make sure that nopaging is not set to true
) {
$limits = "LIMIT 0, $posts_per_page"; // Leave offset at 0 to avoid 404 on paged pages
}
return $limits;
}
/**
* Public callback method loopStart()
*
* Callback function which will be hooked to the loop_start action hook
*
* @param stdClass WP_Query $q Query object passed by reference
* @since 1.0.0
*/
public function loopStart( WP_Query $q )
{
/**
* Although we run this action inside our preGetPosts methods and
* and inside a main query check, we need to redo the check here aswell
* because failing to do so sets our div in the custom query output as well
*/
if ( !$q->is_main_query() )
return;
/**
* Add inline style to hide the page content from the loop
* whenever $removePageFromLoop is set to true. You can
* alternatively alter the page template in a child theme by removing
* everything inside the loop, but keeping the loop
* Example of how your loop should look like:
* while ( have_posts() ) {
* the_post();
* // Add nothing here
* }
*/
if ( true === $this->removePageFromLoop )
echo '<div style="display:none">';
}
/**
* Public callback method loopEnd()
*
* Callback function which will be hooked to the loop_end action hook
*
* @param stdClass WP_Query $q Query object passed by reference
* @since 1.0.0
*/
public function loopEnd( WP_Query $q )
{
/**
* Although we run this action inside our preGetPosts methods and
* and inside a main query check, we need to redo the check here as well
* because failing to do so sets our custom query into an infinite loop
*/
if ( !$q->is_main_query() )
return;
// See the note in the loopStart method
if ( true === $this->removePageFromLoop )
echo '</div>';
//Make sure that $this->injectorQuery actually have a value and is not NULL
if ( !$this->injectorQuery instanceof WP_Query )
return;
// Setup a counter as wee need to run the custom query only once
static $count = 0;
/**
* Only run the custom query on the first run of the loop. Any consecutive
* runs (like if the user runs the loop again), the custom posts won't show.
*/
if ( 0 === (int) $count ) {
// We will now add our custom posts on loop_end
$this->injectorQuery->rewind_posts();
// Create our loop
if ( $this->injectorQuery->have_posts() ) {
/**
* Fires before the loop to add pagination.
*
* @since 1.0.0
*
* @param stdClass $this->injectorQuery Current object (passed by reference).
*/
do_action( 'pregetgostsforgages_before_loop_pagination', $this->injectorQuery );
// Add a static counter for those who need it
static $counter = 0;
while ( $this->injectorQuery->have_posts() ) {
$this->injectorQuery->the_post();
/**
* Fires before get_template_part.
*
* @since 1.0.0
*
* @param int $counter (passed by reference).
*/
do_action( 'pregetgostsforgages_counter_before_template_part', $counter );
/**
* Fires before get_template_part.
*
* @since 1.0.0
*
* @param stdClass $this->injectorQuery-post Current post object (passed by reference).
* @param stdClass $this->injectorQuery Current object (passed by reference).
*/
do_action( 'pregetgostsforgages_current_post_and_object', $this->injectorQuery->post, $this->injectorQuery );
/**
* Load our custom template part as set by the user
*
* We will also add template support for post formats. If $this->postFormatSupport
* is set to true, get_post_format() will be automatically added in get_template part
*
* If you have a template called content-video.php, you only need to pass 'content'
* to $template part and then set $this->postFormatSupport to true in order to load
* content-video.php for video post format posts
*/
$part = '';
if ( true === $this->postFormatSupport )
$part = get_post_format( $this->injectorQuery->post->ID );
get_template_part(
filter_var( $this->templatePart, FILTER_SANITIZE_STRING ),
$part
);
/**
* Fires after get_template_part.
*
* @since 1.0.0
*
* @param int $counter (passed by reference).
*/
do_action( 'pregetgostsforgages_counter_after_template_part', $counter );
$counter++; //Update the counter
}
wp_reset_postdata();
/**
* Fires after the loop to add pagination.
*
* @since 1.0.0
*
* @param stdClass $this->injectorQuery Current object (passed by reference).
*/
do_action( 'pregetgostsforgages_after_loop_pagination', $this->injectorQuery );
}
}
// Update our static counter
$count++;
}
}
USAGE
您现在可以启动课程 (也可以在您的插件或函数文件中) 按照以下步骤定位页面，其中我们将从 post 帖子类型显示每页 2 个帖子
$query = new PreGetPostsForPages(
251, // Page ID we will target
'content', //Template part which will be used to display posts, name should be without .php extension
true, // Should get_template_part support post formats
false, // Should the page object be excluded from the loop
[ // Array of valid arguments that will be passed to WP_Query/pre_get_posts
'post_type' => 'post',
'posts_per_page' => 2
]
);
$query->init();
添加分类和自定义
正如我所说，为了添加分页或自定义样式，进样器查询中有一些操作。这里我用 my own pagination function from the linked answer 循环后添加了分页。另外，使用内置的计数器，我添加了一个 div 来显示我的帖子在两个列。
这是我使用的动作
add_action( 'pregetgostsforgages_counter_before_template_part', function ( $counter )
{
$class = $counter%2 ? ' right' : ' left';
echo '<div class="entry-column' . $class . '">';
});
add_action( 'pregetgostsforgages_counter_after_template_part', function ( $counter )
{
echo '</div>';
});
add_action( 'pregetgostsforgages_after_loop_pagination', function ( WP_Query $q )
{
paginated_numbers();
});
注意，分页是由主查询设置的，而不是进样器查询，所以 build-in 的功能如 the_posts_pagination()也应该有效。
这是最终的结果
静态页面
一切都按照预期在静态前端页面和我的分页功能一起工作，而无需做任何修改
CONCLUSION
这似乎是一个非常多的间接费用，可能是，但是，该公司的优势超过了公司的大时间
大哥
-
您不需要以任何方式更改特定页面的页面模板。这使得一切都是动态的，并且可以容易地在主题之间传递，而无需对代码进行任何修改，如果一切都在插件中完成。
-
您最多只需要在主题中创建一个
content.php模板部分，如果您的主题还没有 -
对主查询工作的任何分页都可以在页面上进行，而无需任何类型的更改或任何额外的查询被传递给函数。
有更多的亲我现在不能想到，但这些都是重要的
参考文献
注：本文内容整合自 Google/Baidu/Bing 辅助翻译的英文资料结果。如果您对结果不满意，可以加入我们改善翻译效果：薇晓朵技术论坛。