Support » Fixing WordPress » Possible bugs?

  • skeen


    Hello all;
    I just downloaded and installed the recent WordPress CVS. Just a couple of things Ive found that arent working.
    My CVS blog:
    NOTE: I am using the example.htaccess file (changed to .htaccess) and I have edited it to include the mod_rewrite rules that WP provided me with.

    1. On the index.php page, the “login” link returns my WP page containing this: “Sorry, no posts matched your criteria.” (the link links to b2login.php)
    2. The calendar links to the root directory, for example: — instead of
    3. In /wp-moderation.php, when I click to submit one of the actions, I get errors. I also get an error when approving a comment in the edit.php.
    4. Under the archives header on the right, when I click on a month, it sends me to this: %day%/11/
    5. Comments cant be accessed when there are two postings with the same subject title.

    Last edited: 18:09 27/11/2003

Viewing 3 replies - 1 through 3 (of 3 total)
  • Laughinglizard


    Note to community members using modified index.php or any other hacks in their WP: Please be careful of CVS upgrades/crawls. Make sure you backup EVERYTHING (including your database) before attempting an upgrade. Bleeding edge is exactly that. 🙂
    BTW: if you have run the upgrade scripts on your database, but want to back down from actually upgrading the WP folder, there are some ways of getting around to using the upgraded database with older php scripts. It is very messy, but still saves losing all your posts/data or worse. It is always a good idea to have 2 seperate blogs, a live and a test, with different databases.


    I’d like to chime in after LL:
    – Run Apache and MySQL locally whenever possible when ‘testing’ things. Testing could mean new CSS, html, 3rd party scripts, or upgraded versions.
    – This also means you will(can) keep a live backup of your site. Note there is a danger there…
    – Back-up your live backup before doing major changes, upgrades, etc. Then it is really easy to do a restore if something goes bad.
    – DON’T grab CVS live down into your active directory if you’ve made anything more than minor index.php mods. Grab it down to a primary cvsroot directory, then use any old code-merge program to look at differences and merge carefully to keep your changes.
    I NAILED myself today doing the 0.80 update. Having backed up both saved my ass (if I had REALLY screwed up), and turned out to help me debug what the problem was.
    Also, is there a was for people to get changes back into the main branch? I for one have a number of tweaks across many files, and I >think< many of them are good, and useful (hah!), to be had by the community. I’m not necessarily looking for CVS-write access (though I’ve got it on some other projects), and don’t want to be generating diff-submissions… And need a better way to deal with plugins and templates myself! 🙂
    Anyway, discussion for another thread. 😉

    Moderator Matt Mullenweg


    Skeen, part of the problem may be that because of their nature and setup custom, permalink formats must remain hierarchical. IE, year must be above month, which must be above day, etc. If the structure doesn’t drill down, funky stuff will happen.
    1 and 3 are fixed in the latest CVS.
    For 5, if you have multiple posts on the same day regularly I would add %post_id% to your permalink structure to distinguish posts.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Possible bugs?’ is closed to new replies.