jwvanderbeck

Amazing.

Well I have no idea WHY that works, since all that param is supposed to do is supress the addition of the “more” link, but it does. Thank you very much. I never would have thought ot try that *boggle*

Yeah I tried that and even $localcontent is empty.

Heh figures.. no sooner do I post then Ifind the function get_the_content() while browsing through the WP code. Exactly what I needed :p

Ok apparently this is either a bug in WP or a limitation. What is happening is the posts_nav_link function is getting confused. It is placing the previous/next page links based on what would appear according to the blog’s global posts per pag settings.

In other words if your blog is set to say 10 posts per page, and you don’t mess with anything at all in the querys, and say you have 18 posts on your blog. You would receive ONE link for “next page” before you ran out of posts. If you had it set to 1 post per page you would receive 18 links to “next page”.

Now if you have it set to 10 posts per page, but you mess with the query on a certain page to only display 1 post per page, then use the above referenced code to page properly, you will only see 1 link for “next page” because the posts_nav_link function still thinks you are seeing 10 per page and therefore it thinks there are no more pages.

If this is intentional, then it seems pretty wierd. Seems like a nasty bug in WP to me.

Hmm ok well that code seems to like, ALMOST work. Its a tease. It appears to work fine at first, as you can click and go to the next page just wonderfully, but there it breaks. It somehow prevents WP from showing a link to the following page. Just shows one back to the first page.

Is there any documentation on get_query_var and the ‘paged’ parameter? I couldn’t find any in the codex.

Interesting. Thanks for the link!