Recent problemo in posts_nav_link

  • I believe this was working a few days ago but the new fix created a new “bug”. The link now is:
    site/wordpress/wordpress/page/2 instead of site/wordpress/page/2
    since the front page doesn’t give the forum title, perhaps I should have put “1.3-pre-alpha” in the post title ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter Beel

    (@beel)

    Anybody else running 1.3-pre-alpha run into this?

    Another navigation issue
    /index.php/200405
    or rather /index.php/yyyymm
    Doesn’t seem to work also for the permalinks, it produces no search results.

    Beel, fixed.
    mrwok, what’s your permalink structure?

    I am running the latest from the cvs –continously updated– and I have never ran into the problem that Beel described (look at https://www.collantes.us/).
    Ryan, does the change on the CVS you just commited eliminates the trailing slash on $qstr? Reason I am asking because I like it /page/2/ instead is /page/2

    Thread Starter Beel

    (@beel)

    Thanks, working correctly again.

    unixman, it does eliminate the slash. It’ll be back. That code was also putting slashes after the “&paged=1” style queries as well. “&paged=1/” looks rather weird. The bug Beel found would only be tripped if your index was in a subdirectory. If you’re running from root, you wouldn’t have seen the problem. I think I have both root and non-root fixed now.

    Yes, I am not running on a directory, I have everything on root. The CVS seems to be going slow, unless emails are sent before a commit is happening or SF CVS takes a very long time to propagate…

    Emails are sent right after a commit has been made.
    Sourceforge’s public CVS takes up to several hours to synch to developers’ CVS.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Recent problemo in posts_nav_link’ is closed to new replies.