Viewing 15 replies - 1 through 15 (of 18 total)
  • WpPaginate is getting this from the get_pagenum_link() function in WordPress. To *fix* it, you’ll have to do a tiny edit to the WP source.

    Open wp-includes/template-functions-links.php in a text editor. Around line 375, you, you’ll see

    function get_pagenum_link($pagenum = 1){

    Several lines down look for this:

    $index = 'index.php';

    Change it to:

    $index = $qstr;

    That’s it.

    Note: Always backup source files before editing, and comment your changes for future reference.

    Thread Starter francesca

    (@francesca)

    Thanx a lot

    Hi. I’ve got a problem with this plugin, too. The pagination doesn’t work for me. I was searching hours for a fix, but didn’t find any solution to the problem.

    For example my Standards Section. It shows four pages. But navigating doesn’t work. Klicking on the link displays “Sorry, no results…”

    Hey, BS-Markup —- I went to your site and it seems you fixed your pagination problem. How’s about posting the fix here?

    Thread Starter francesca

    (@francesca)

    Hello πŸ™‚
    I’m using WP Paginate but I don’t like the fact that the pagination results this way (for example in the first page):

    1 | … | 4 | 5 | 6

    What if I need to have always all the page numbers?

    Thanx a lot πŸ™‚

    I would imagine on this line of the code:

    function wpPaginate($paginateAfterNposts = '', $pageNavDivider = ' | ', $paginateHome = FALSE, $briefnavigation = TRUE, $navpad = 6) {

    You would change the $navpad = 6 to whatever number you see fit, perhaps 999 if you want to show a list of all your page numbers.

    I have not tested this theory but it might work πŸ™‚

    You might want to know that the wp-paginate plugin – as it is written now – is apparently causing a large number of database queries. While this does not seem to add much to page rendering time, it does add to load, and that is not a good thing.
    Reading this could be useful:
    http://wordpress.org/support/topic/35279?page=1#post-200196

    I’m not saying it’s a bad plugin or that you should not use it – only that there are some concerns and should your site slow, it could well be the culprit.

    Thread Starter francesca

    (@francesca)

    In the meanwhile I solved turning FALSE the $briefnavigation in any case:


    if ($num_of_pages > $turnOnBriefNavWhenOver) {
    $briefnavigation = FALSE;
    } else {
    $briefnavigation = FALSE;

    Before it was


    if ($num_of_pages > $turnOnBriefNavWhenOver) {
    $briefnavigation = TRUE;
    } else {
    $briefnavigation = FALSE;

    Thread Starter francesca

    (@francesca)

    Thanx Podz for the informations, I’m reading

    “Hey, BS-Markup —- I went to your site and it seems you fixed your pagination problem. How’s about posting the fix here?”

    Shame over me. It was the .htaccess. I still used the old one. I changed it and fixed.

    This is a nice plugin, but I can’t get it to work with pages on which posts are listed in alphabetical order.

    I couldn’t get the pagination to work when browsing within a category. It looks normal on the front page, but only on the front page. Any suggestions?

    is this plugin where you can navigate between posts?

    Is it somethind like this:
    Pages (163) : [1] 2 3 » … Last »

    WordPress 1.5 Plugin: WP-PageNavi 1.00 – Download
    Adds a page navigation with paging elements to your WordPress.

    Example: <A href=”http://www.lesterchan.net/”>here. Right at the bottom of the page.

    Could it be, you copied the wrong link? I get WP-Polls-Plugin if i download…

    This seems to be the correct page Download Plugin… or visit this page:
    http://www.lesterchan.net/others/downloads.php?id=11 or for a overview this one:

    http://www.lesterchan.net/others/downloads.php

    By the way: I used the WP-Paginate of Jennifer, but it produces some problems with large Categories… the WP-Pagenavi is blazing fast. πŸ™‚
    Great Plugin!

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘wpPaginate’ is closed to new replies.