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
I did more research and found a plugin that corrects the pagination issues with multiple categories. To summarize, I am using using a plugin called WordPress Category Archive – www.wordpress.org/extend/plugins/wp-category-archive/ to display my category specific archive. There were some issues with pagination due to the year/month being included in the url. The Solution: A plugin … Read more
I believe this problem is less to do with the rewrite rule, which on the face of it looks like it should work, and more to do with WordPress’ canonical redirect. Basically when WordPress receives an url – it interprets it as a query. It then looks again at the url to check that the … Read more
Adjacent post fetching relies on quite a bit of custom SQL inside. One of the assumptions it makes in that SQL is that you are only looking for published post. You can use filter in get_adjacent_post() (that is used internally by those next/previous functions) to alter the query and get rid of published only limitation.
I’ve solved this for myself with rewrite rule. The story: I have “piece” custom post type, taxonomy “media_tag” with “m_audio” term and taxonomy “genre_tag” with “g_sacred”, “g_folk” etc. And I want to have an URL like /piece/audio/<genre> to access archives. So, now I have in my functions.php: add_filter( ‘rewrite_rules_array’, ‘my_insert_rewrite_rules’ ); function my_insert_rewrite_rules( $rules ) … Read more
I’ve not tested this, but adding an action after parse_query or wp which checks if the current request is_category(), and then setting the is_404 property of the global $wp_query to false might set you off in the right direction.