Firstly, in the for there is missing a ‘$’. It should read: for ( $i = 1; $i <= $im; $i++ ). Secondly, in order to use the page link(s), you need to call the function wp_link_pages(). $im = stripslashes( get_option( ‘tm_alim’ ) ); for ( $i = 1; $i <= $im; $i++ ) echo … Read more
You have all the necessary variables already at hand: $page is the current page number, and $portfolio->found_posts the total number of posts. Both should be integers, but to be sure and to keep the code translatable I would use something like this: $current = sprintf( _x( ‘Page %1$d of %2$d.’, // default string ‘1 = … Read more
You are doing a few different things wrong– or at least convoluted and suspect– in that code and I am sure that that is resulting in your query results getting out of sync with the pagination. You’ve got a couple of queries in there, including one made by query_posts which you should really never be … Read more
You aren’t setting the $paged variable, at least not in the code posted. Per the Codex, you need to do something like this: $paged = (get_query_var(‘paged’)) ? get_query_var(‘paged’) : 1; … before trying to use the $paged variable. That is, it needs to come before this line: $wp_query->query(array(‘post_type’=>’post’,’post_status’=>’publish’,’showposts’>3,’paged’=>$paged)); Also, side note, what is this– php … Read more
This does not have anything to do with cookies, this is what happends: 1. Visitor goes to page 4/6 wich shows products 40-50 (10 per page) 2. When visitor changes products per page from 10 to 30, he will still be at page 4, when there are only 2 pages (60 products / 30 = … Read more
There’s no reason to use multiple loops to get this effect: The look you want comes from the jQuery Masonry script, which is included in recent versions of WordPress. Your post list as you describe it is just the standard post index, so use a single standard loop — that is, a WordPress loop, as … Read more
Perhaps you can take a look at this question and the answers and check if you really want to use query_posts() as it is not recommended while dealing with posts pagination. Why not use pre_get_posts action instead? Or you can try something like this: <?php $custom_query = new WP_Query(array( ‘post_status’ => ‘publish’, ‘post_type’ => ‘products’, … Read more
They’re not the same. Your news page is the posts page, and your recipes page is a page post type where you’ve used a custom query to load the posts. I can see that by looking at the classes being added to the body tag. I presume that your custom query has no pagination parameters … Read more
I was going to create my own question and answer it, but this looks as good a place as any. The way I solved this, is by using $_SESSION. Keep in mind I am using infinite-scroll, so I can tell when the page is being fetched via ajax as opposed to being actually navigated to … Read more
If you use <!–nextpage–> tag, then you could use wp_link_pages function. Just put it in your single.php template.