$args = array( ‘cat’=>7, ‘offset’=>4,’paged’ => $paged); in this array use posts_per_page insted of offset $args = array( ‘cat’ => 7, ‘posts_per_page’ => 4,’paged’ => $paged);
I did what Rarst told me to do. First I searched around in the Pods Framework documentation. This solved my problem. Here’s what the code looks like right now. <?php $params = array( ‘orderby’ => ‘publish_date.meta_value DESC’, ‘limit’ => 10 ); $fltNewsPods = pods( ‘fltnews’, $params ); while ($fltNewsPods->fetch()) { echo “<li class=”content-list-item”>”; $podsForNewsItem = … Read more
WordPress already adds classes to the body for you to handle this, as long as your theme correctly uses the body_class template tag. On the 2nd page of Page, your body will have these additional classes: paged, paged-2 & page-paged-2, so you can see that you can make changes to styles to suit: body.page { … Read more
Here’s a working example of a secondary loop with pagination that can be used on singular posts. WP_Query is typically a better way to go than query_posts(). Your permalink settings shouldn’t be a factor here. <?php $my_query = new WP_Query( [ ‘posts_per_page’ => 3, ‘paged’ => ( get_query_var( ‘paged’ ) ) ? get_query_var( ‘paged’ ) … Read more
So, it turns out my hunch was correct and the solution is to add some rewrite rules. Here’s what I added: function owr_blog_rewrite( $rules ) { return [ ‘notes/topic/([^/]+)/?$’ => ‘topic=$matches[1]’, ‘notes/topic/([^/]+)/page/([0-9]+)/?$’ => ‘topic=$matches[1]&paged=$matches[2]’, ] + $rules; } add_filter( ‘rewrite_rules_array’, ‘owr_blog_rewrite’ ); Everything works as expected now
Overall CODE issues: Your CODE is so wrong in so many ways that I shouldn’t even attempt to address them here. I suggest you study Official WordPress Theme Handbook properly before doing these sort of customizations. For the sake of the context, I’m ignoring other issues within your CODE and touching only the issues below: … Read more
“Posts per pages” limit from “Settings -> Reading” does not apply here (post list in the dashboard) and default size of list is 20. Your pagination does not work properly because you use pre_get_posts action hook to change the per_page limit, which is not the right way. The per_page limit overwritten by pre_get_posts filter will … Read more
I use the following code to Displays Next/Previous link in same posts category and work correctly for me. <?php get_template_part( ‘content’, get_post_format() ); // Previous/next post navigation. previous_post_link(‘%link”https://wordpress.stackexchange.com/questions/344307/,”Before’, true ); next_post_link( ‘%link”https://wordpress.stackexchange.com/questions/344307/,”Next’, true ); ?> And For CSS Styling the “%link” Element I use this code in my functions.php file. /////Next/Prev post style add_filter(‘next_post_link”https://wordpress.stackexchange.com/questions/344307/,”next_post_link_attributes’); add_filter(‘previous_post_link”https://wordpress.stackexchange.com/questions/344307/,”previous_post_link_attributes’); … Read more
You can do a simple str_replace( ‘/page/1/’, “https://wordpress.stackexchange.com/”, $string ) on the results generated by paginate_links() to get rid of /page/1/ which appears on the first page link as well as the Prev link (when it points to the first page). Here’s a full (tested) example: /** * Numeric pagination via WP core function paginate_links(). … Read more
I’d like to redirect in ht.access To clarify, it’s .htaccess, not ht.access. You can do something like the following at the top of the .htaccess file, before the existing WordPress directvies: RewriteRule (.*/)page/\d+/?$ /$1 [R=302,L] The above issues a 302 (temporary) redirect for any URL of the form /<something>/page/<number>/ (trailing slash optional) to /<something>/. The … Read more