• Resolved mrkingid

    (@mrkingid)


    Calling all guru’s…

    This might be long so bare with me.

    Site: https://design-studio.com

    I started development of a new site piggy backed off a server hosted on godaddy. the install was to https://www.mysite.com/new-site-dev

    There I placed a fresh install of WP and started my thing. Editing the CSS, adding images and posts, etc.

    The time came to move it to its own domain but I decided not to go with godaddy.

    On the new host (netnation) i created what I needed, same DB name, etc. On the godaddy site I backed up DB, changed URL and Blog address to the new host. Installed a fresh WP and uploaded saved DB. And all was brought over and working. No pages missing, no text missing, all works well. except

    I wanted to change the permalink structure from the default to the second choice avaialable. I do that and ‘boom’, no pages can be accessed.

    Is the end I had to choose /index.php/%postname%/ to get semi pretty permalinks working but I would much prefer to not have the /index.php/ in the address.

    So, anyone know why I can’t use the permalink structure I want too?

    I have read the codex over and over but I cannot get it to work the way I would prefer.

    Mike

    PS. Note that a fresh install and DB build (not migrating) on a netnation account allows for permalink to work the way I want.

Viewing 9 replies - 16 through 24 (of 24 total)
  • Thread Starter mrkingid

    (@mrkingid)

    Just removed php and did a fresh install thinking that was it… nope

    Any other ideas?

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    Hmmm… Okay, so Apache has mod_rewrite enabled, but how about the AllowOverride setting for your web directory? It must have at least the “FileInfo” level, or “All”.

    Hmmm… Okay, so Apache has mod_rewrite enabled, but how about the AllowOverride setting for your web directory? It must have at least the “FileInfo” level, or “All”.

    The thing is he says that the permalinks work if he just has an empty, fresh, install. Only when he migrates does he get the problem.

    If it were an Apache config issue then it would always be broken.

    Bit confusing though, I don’t see why migrating in posts would stop stuff working.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    Hmm.. is this a database dump being imported? Or a WordPress export being imported?

    Thread Starter mrkingid

    (@mrkingid)

    it was a DB dump that I imported from where it was created. All WP directories and files were copied over, config changed, etc.

    I followed all the directions to the ‘T’ as per the worpdress guide to moving a blog to another domain.

    The blog was developed at https://mysite.com/new_site_dev where the permalinks were working correctly and then was placed at https://www.design-studio.com and permalinks never worked properly again

    Thread Starter mrkingid

    (@mrkingid)

    Host says AllowOverride is set to all for the server.

    So, back to square one.

    Thread Starter mrkingid

    (@mrkingid)

    Posting solution for posterity sake:

    ————————————

    HOLY SH*** I FOUND IT!!!!!!!!!!!!!!!!!!!

    Wooohoooooo!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    For those two servers I have to add ‘Options FollowSymLinks
    ‘ to the .htaccess file.

    So it would look like…

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

    # END WordPress

    Damn…. over three months it has taken me to find the solution!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    Sweet

    **HAPPY DANCE**HAPPY DANCE**HAPPY DANCE***
    ————————————–

    Just on the side, you were lucky to find your solution this way. Just for the sake of clarity…
    When enabling FollowSymLinks, it has to be defined in two places:

    First, FollowSymLinks needs to be enabled in httpd.conf. Here is an example what you might want to have in your httpd.conf.

    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    Satisfy all
    </Directory>

    Second, FollowSymLinks may need to be mentioned in .htaccess too. Here is an example
    Options +FollowSymLinks

    Third, know that FollowSymLinks improves the performance slightly. The effect is almost negligible, but just so you know. Whenever you can, use FollowSymLinks.

    Fourth, FollowSymLinks is good for security. You can hide your true location of your files and folders through it.

    Here is a good page on FollowSymLinks
    FollowSymLinks

    Thanks so much Michael – I was having the very same issue with netnation and wordpress.

    My situation was that pretty urls would work if the wp install was in a sub directory but not in the root https://www.mydomain.com/about would fail and https://www.mydomain.com/wordpress/about would work.

    Thanks so much for the solution, thankfully, I didn’t have to spend 3 months.

    Great art by the way!

    Jonathan
    https://www.crowdpeople.com

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Permalink issue after site migration to different host’ is closed to new replies.