我已经对如何在真实页面和静态首页上使用pre_get_posts进行了广泛的研究,似乎没有傻瓜方法。

到目前为止,我发现最好的选择来自@birgire在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();


这很好,并且可以使用我自己的分页功能进行页面调用。

问题:

由于该函数,我失去了页面完整性,这使其他函数依赖于$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来部分解决问题,该问题会将页面对象作为循环的第一页注入。如果您需要在请求的帖子之前显示页面信息,这将非常有用,但是如果您不希望这么做,那将很麻烦。

我可以通过直接修改全局变量来解决循环前的问题,这是我不太喜欢的。我将以下方法挂接到wp方法内的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(已将其设置为查询对象)的完整性循环之后。

编辑

似乎对我需要什么以及为什么需要它感到困惑

我需要什么

无论如何,我都需要在模板上保留$wp_the_query->post$wp_query->post$post的值,并且该值应该是查询的对象。在此阶段,使用我发布的代码,这三个变量的值不保存页面对象,而是保存循环中post的post对象。我希望这已经足够清楚了。

我已经发布了可以用来测试这些变量的代码

为什么需要它

我需要一个通过pre_get_posts将帖子添加到页面模板和静态首页的可靠方法,而无需更改整个页面的功能。在此阶段,如所讨论的代码所示,由于$post持有“错误的”发布对象,因此循环后它破坏了面包屑功能和相关页面功能。

最重要的是,我不想直接更改页面模板。我希望能够在不对模板进行任何修改的情况下将帖子添加到页面模板中

评论

您想做什么,您的目标或功能要求?据我所知,您没有在任何地方声明它。

#1 楼

我终于使它工作了,但是没有解决我的问题中的代码。我完全放弃了整个构想,重新开始了新的发展方向。

注意:

如果有人能够解决我所提出的问题,请随时发表答案。另外,如果您有其他解决方案,请随时发布答案。

重做的类和解决方案:

我在这里尝试使用的是后期注入,而不是而不是完全更改主查询并陷入上述所有问题,包括(a)直接更改全局变量,(b)遇到全局值问题以及(c)重新分配页面模板。

通过后注入,我可以保持完整的帖子完整性,因此$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



用于访问查询对象和当前发布对象的常规挂钩


pregetgostsforgages_current_post_and_object



这些挂钩为您提供了全面的使用体验,因为您不需要更改页面模板本身的任何内容,这是我一开始的初衷。可以从插件或功能文件中完全更改页面,这使该解决方案非常动态。

我还使用get_template_part()来加载模板部分,该模板部分将用于显示帖子。如今,大多数主题都使用模板部分,这在课堂上非常有用。如果您的主题使用content.php,则可以简单地将content传递给$templatePart来加载content.php

如果您需要模板部分的后格式支持,这很容易–您可以简单地将content传递给$templatePart并将$postFormatSupport设置为true。结果,模板部分content-video.php将被加载为帖子格式为video的帖子。

主查询

通过以下方式对主查询进行了以下更改相应的过滤器和操作:



为了对主查询进行分页:


传递了喷射器查询的$found_posts属性值通过found_posts过滤器将其设置为主要查询对象的值。
通过posts_per_page将用户传递的参数pre_get_posts的值设置为主查询。
$max_num_pages是使用$found_postsposts_per_page中的帖子数量来计算的。因为is_singular在页面上为true,所以它禁止设置LIMIT子句。简单地将is_singular设置为false会引起一些问题,因此我决定通过LIMIT过滤器设置post_limits子句。我将offset子句的LIMIT设置为0,以避免在打开了分页的页面上出现404。



这可以解决分页以及可能由于分页而引起的任何问题。后注入。

页面对象

通过使用页面上的默认循环(在已插入帖子的顶部和顶部),可以将当前页面对象显示为帖子。如果不需要此功能,只需将$removePageFromLoop设置为true,即可隐藏页面内容,使其不被显示。

在此阶段,我正在使用CSS通过以下方式隐藏页面对象: loop_startloop_end操作,因为我找不到另一种方法。这种方法的缺点是,主查询中与the_post动作挂钩相关的所有内容也将被隐藏。

CLASS

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

您现在可以启动该类(也可以在您的插件或函数文件),以定位ID为251的页面为目标,在该页面上,我们将从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(); 


添加分页和自定义样式

如前所述,在注入器查询中有一些操作可以添加分页和/或自定义样式。

在下面的示例中,我在循环后使用链接答案中我自己的分页功能添加了分页。另外,使用我的自定义计数器,我添加了一个<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();    
});


请注意,分页是由主查询而不是进样器查询设置的,因此是内置的诸如the_posts_pagination()之类的功能也应该起作用。

这是最终结果



静态前页

一切正常符合静态首页上的预期以及我的分页功能,而无需任何进一步的修改。

结论

这似乎是很多开销,也许是,但专业人士的花费却超过了缺点。

BIG PRO'S


您无需以任何方式更改特定页面的页面模板。只要一切都在插件中完成,这就能使所有内容变得动态,并且可以轻松地在主题之间进行转移,而无需对代码进行任何修改。
最多,您只需要在主题中创建一个content.php模板部件即可。主题还没有。
对主查询有效的任何分页都可以在页面上运行,而无需进行任何类型的更改或将查询中的任何其他内容传递给函数。

有我现在想不出更多的专业人士,但这是重要的。

评论


i.imgur.com/LTfLK.gif

–TheDeadMedic
16年5月16日在20:33