Support » Fixing WordPress » clean urls after moving blog from subdirectory to root

  • Resolved Matthew Willse


    I’m having a problem with clean urls, but only after moving my blog from from a sub-directory. I’ve read a dozen helpful threads, but my problem seems a little bit different.

    At first, WP 2.6.1 was installed in .org/wordpress/ and was viewable at .org/wordpress/. Everything worked great. The clean permalinks worked fine.

    I’m done with development and now want the blog visible at the domain’s root. I used the relevant directions on giving wp its own directory.

    Now, everything works if I use default permalinks. But I can’t switch to month and name as I had it before. I’ve chmod .htaccess and confirmed that it’s updating properly. The links to Pages and Posts appear proper, but lead to a not found page (hosting, not wp).

    In the directions linked above, it’s not clear if you I should leave index.php and .htaccess in /wordpress/ when I update and copy them in the root. Should I leave or delete them there?

    My friend’s crappy host godaddy say they don’t allow mod_rewrite. But everything worked in the sub-directory just fine. So I don’t think that’s the problem. But maybe it is.

    I do have access to php.ini, so I’m going to try to update cgi.fix_pathinfo = 0. But we’re on Linux, so I’m not sure if this is relevant.

    Any suggestions??

    .htaccess contains:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    # END WordPress

Viewing 5 replies - 1 through 5 (of 5 total)
  • As I’ve learned many times before, if you think you’ve done everything right, and you’ve double-checked for typos, and it still doesn’t work… it’s probably your host’s fault.

    I’ve wasted so many hours because godaddy techs wouldn’t do their job.

    mod_rewrite was disable. I had a test redirect from /test1 to google that suddenly worked after my third phone call with support. They never admitted that something was wrong, but suddenly that works?

    First, they tried to upsell me, and said mod_rewrite was only available on virtual and private hosting. What? That’s ridiculous.

    Tonight, they admitted it was included with all linux hosting. But they refused to either look at my simple test or try one of their own to demonstrate whether it worked.

    Then they hung up on me. And presto! Suddenly everything works just fine.


    So if you’re having trouble after you move your blog to the root directory when it’s installed in a sub directory:

    1. chmod your .htaccess to 777 and confirm it updated correctly
    2. get your friend to change their crappy host


    I’m sorry to hear about your situation. If you email with the domain name, I would be happy to review the account to ensure this does not happen in the future.

    Currently our servers use a caching technique for .htaccess files only. This is to avoid, as much as possible, the penalty of traversing your directory structure with each request. This cache is invalidated periodically so that new files are found. This was probably why the changes weren’t working initially, but took effect after a period of time.

    As a side note, this only affects the discovery of new .htaccess files. Once an .htaccess file is in place there is no delay in making any changes to it.

    Alicia R.
    Go Daddy Hosting


    You should mention somewhere in your FAQ or whatever you have for your customers about this “delayed effect” of .htaccess file since we already have had many desperate posts here wondering why the rewrite rules don’t kick in right from the beginning…
    We have learned to advise them “patience” because some users figured out that for some mysterious reasons they would work after a while.
    Good to know, still you should make it clear for your clients, don’t you think?

    I’m glad you brought this up. We do discuss this in the following help article, however, we are looking at creating an article that is more specific.

    It might also be helpful to add to the WordPress docs and something I would be happy to help with.

    Alicia R.
    Go Daddy Hosting

    Thanks Moshu,

    Alicia, I’m surprised that your tech support wasn’t aware of this delay. It seems like it would affect quite a few customers. They reacted as if I was speaking in gibberish and tried to sell me virtual private hosting!

    I would add a note about the delay to your articles about mod_rewrite. The article you pointed to is titled “How do I use htaccess to manage my PHP file extensions?” Switching from php4 to 5 has absolutely nothing to do with this issue.

    Also, more and more people will be installing WP in a subdirectory for a site displayed in the root. They will experience this problem whether or not they use your WP installer or not.

    WordPress is thoroughly well documented. The developers shouldn’t be bothered with documenting the quirks and backwards practices of every other hosting company.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘clean urls after moving blog from subdirectory to root’ is closed to new replies.