Support » Fixing WordPress » Nice permalinks not working

  • jonthejester


    I’m trying to get nice permalinks, like /archives/jon/my-love-article working for 1.3, but for some reason it’s not outputting htaccess rules like it should. I’m right now using the structure /index.php/archives/%author%/%postname%/, but it’d be nice to do just /archives/%author%/%postname%/ with htaccess.
    The htaccess rules have been outputted for nice permalinks for 1.2, in the past.
    Any idea why that’s happening?

Viewing 15 replies - 1 through 15 (of 24 total)
  • Ryan Boren


    WordPress Dev

    1.3 doesn’t display the rules if your .htaccess is writable. Instead, it writes them for you.

    Tried to make a new, empty file, named it .htaccess. Set it to read/write/execute for all/world. The directory is also 777 (same as file). Apparently that didn’t work. It should work, but I don’t know why it’s not doing it.

    Mark (podz)


    Support Maven

    Did you set no permalinks, then upload and chmod the .htacess, then set the permalinks ? (Sort of undo then redo ?)

    I thought WP will automatically create .htaccess if does not exist? I’m not sure as I wasn’t paying attention. But I remember that I put WP in a new folder so .htaccess was not there before. So I went to permalink page to set it up and I got nothing to copy-paste. Hmm? I went to manage my files, click on .htaccess link and HOLY CRAP!? This is TOO good to be true. So am I wrong or right that WP will create .htaccess if it does not exist already?
    I know I could always look up the code, but, yeah…?

    1.3a will create the file if it can write to the directory.

    Neither suggestion worked, oddly… Why me, why now?
    It could also be I need to upgrade my CVS version to the more recent revisions. I’ll post back if there’s anything on that.

    Yeah, updated to the more recent CVS version last night, and oddly that didn’t work also. If the thing’s working for everyone else (there must be something wrong with me or my server then), is there like a debug mode or something so I can diagnose what’s not kicking? This is such a weird phantom problem… Death to phantoms…
    And yeah, so far I’m sticking with /index.php/* until I have a solution. Otherwise WP is working out well, for the most part.

    Btw, does anyone know where the file-writing code is, like which file it’s in? I’m curious to see how it works for .htaccess.

    Just to make sure, is anyone else having this problem or is this a remote case and my server could have a random bug?
    Btw, I’m going to test WP 1.3 on my comp (it’s apache2+mysql+linux), and I’m going to move to a new host. I guess this means I have a remote case, darn it… :-\

    Interesting…I never had a .htaccess file in my blog directory before. Sounds like I should though. However, I’m a little unclear as to how to create one.

    Earlier it was mentioned to create an empty file, call it .htaccess, and chmod it (to what? 777?). So in the codex it says, “If you leave whitespace at the end of your .htaccess file…”. So it’s not going to freak out about an empty file, I take it.

    And do I understand correctly that once that is created and properly placed in my blog directory, I am to go to the Options > Permalinks and copy-paste from the choices listed there? And that’s it? Does it work for previous posts as well or just the ones going forward?

    Thanks for your patience with my many questions. 🙂

    See this post regarding creating an .htacess file with 1.5:

    Does it work the same for WP v1.2.2, which I’m using? It doesn’t specify versions in the post you refer to.

    Sorry, it doesn’t work the same in 1.2.2. You can create a text file, and call it whatever you like, say htaccess.txt and then copy/paste the rewrite rules into it. Then, upload that file to your WP directory, and then change the name to .htaccess. Note that some FTP programs will not show .htaccess files because they are “hidden.” You may have to get on to your server itself via cPanel or equivalent and rename the file there.


    Thanks very much for the information! I just got my RSS, Comments, etc. working as intended.

    Portland, Oregon

    “When the going gets weird the weird turn pro” – Hunter S. Thompson

    Okay, I followed your instructions, but now I’m getting the following error:

    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator at and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    I chmod it to 777 and cleared my browser’s cache to be sure I was viewing the newest stuff.


Viewing 15 replies - 1 through 15 (of 24 total)
  • The topic ‘Nice permalinks not working’ is closed to new replies.