• Took wordpress RC1 for a test drive, and have to say I’m very impressed – awesome job guys!!!
    I also found three bugs:
    1. Setting the number of posts on the front page (via “options”) only works when there is no category specified, as soon as you use “category_name” in the URL this setting is ignored.
    2. Changing the post’s timestamp only works when you hit “publish” – if you hit “save” instead, the change is ignored (and yes, I have the “edit timestamp” box checked).
    3. I can’t logout! Clicking on “logout” returns me directly to the “new post” screen, but I’m still logged in. (This last issue might be due to me changing the installation directory, but after I undid that change I still had the same problem.)
    Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter Anonymous

    Seems like this post got lost. 😉

    1) I think that’s how archives work. When you go to a category’s archive, it lists all the posts in that category. The alternative would be to implement pagination.

    Thread Starter Anonymous

    1) Junesix, don’t forget that everybody is using wordpress for something else. You might be using the category funtion as an archive, to me it’s an archive when I list all posts of 2002 – if I define several categories, it makes a lot of sense to have the same amount of control over the page as with the general index where everything is lumped together.
    4) Another tiny issue which seems to be a bug rather than a feature: two or more empty lines are always regarded as one. No biggie, an extra line can be inserted by using   – just thought I’d point this out. 😉
    Thanks guys!

    I apologize if I sounded criticizing, I didn’t mean it that way. I just wanted to point out that by default most blogs organize categories the same as date-based archives, that is, by listing all the posts in that category/month. The option in the admin panel for restricting the number of posts affects the index page only. Granted, it would be nice if there was an option to set the max posts value in the admin panel to affect just the index or to all archives but that hasn’t been implemented. But in that respect, it’s more of a feature/plugin/hack, rather than a bug, IMHO.
    If you want to limit the number of posts, I suggest creating a separate template for category archives, and using the recent posts hack posted here:
    http://wordpress.org/support/3/5662

    Thread Starter Anonymous

    You didn’t sound criticizing, hope I didn’t either. 😉 In fact, you may be right, after I looked at the code I realized that it probably is an intentional feature, and it wasn’t difficult to change it the way I wanted.
    #2 though seems to be like a real bug (makes no sense that in order to publish a post in the future, it has to go live first so you can alter the timestamp). I’m also concerned about #3 – anybody else having the same problem?

    Looks like someone figured out a way to apply the posts per page setting to all pages, including archives.
    http://wordpress.org/support/6/5670
    Anon, you might want to check this out.

    Thread Starter Anonymous

    Hehe, looks like I beat you by 2 (!) seconds! 😉

    Thread Starter Anonymous

    Sorry guys, I break your sweet talking, but how correct thise bugs, from the first posting?

    Re: bug #3
    I had the same problem – after setting everything up and logging in as admin for the first time, I couldn’t logout! If I clicked the button, I would be taken to the “Write” screen.
    I finally deleted my cookies and then logged in again and now it seems to be working fine – I can log in and log out as different users.
    Anyone else have this problem?

    Thread Starter Anonymous

    #1 Open wp-blog-header.php, look for the following section:
    elseif (($m) || ($p) || ($w) || ($s) || ($whichcat) || ($author) || $monthnum || $year || $day) {
    $limits = ”;
    }
    Replace it with:
    elseif (($p) || ($w) || ($s) || ($whichcat) || ($author) || $monthnum || $year || $day) {
    $limits = ‘ LIMIT ‘.$posts_per_page;
    }
    elseif ( ($m) ) {
    $limits = ”;
    }
    At least that worked for my purposes.
    #2 Still unresolved to me, but I’m still using RC2 so no clue if this has been addressed in later versions.
    #3 Same as #2. I specifically deleted the wordpress cookie, that worked for logging out, but after logging in again, the problem was the same as before.

    Thread Starter Anonymous

    =still using RC1

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Timestamp, logout and category bugs in RC1’ is closed to new replies.