WordPress.org

Ready to get started?Download WordPress

Forums

Recent problemo in posts_nav_link (8 posts)

  1. Beel
    Member
    Posted 10 years ago #

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

  2. mrwok
    Member
    Posted 10 years ago #

    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.

  3. Ryan Boren
    WordPress Dev
    Posted 10 years ago #

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

  4. unixman
    Member
    Posted 10 years ago #

    I am running the latest from the cvs --continously updated-- and I have never ran into the problem that Beel described (look at http://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

  5. Beel
    Member
    Posted 10 years ago #

    Thanks, working correctly again.

  6. Ryan Boren
    WordPress Dev
    Posted 10 years ago #

    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.

  7. unixman
    Member
    Posted 10 years ago #

    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...

  8. michelv
    Member
    Posted 10 years ago #

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

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.