Support » Networking WordPress » htaccess issue for converted multisite site

Viewing 1 replies (of 1 total)
  • forcing a non-WWW to WWW means that http://new.example.com stops being recognized

    that shouldn’t be true. at all. Your .htaccess for forcing non-www should only include the “WWW.” clause, not any sub-domains like “NEW.”

    when removing “www” there’s many things you have to check to prevent frustration, adding in your converting to a multi site (at the same time?) you’ll want to investigate:

    • Check Your Web Host (control panel, plesk), some hosts let you choose if you don’t want “www”
    • In wordpress make sure the main SITE URL and HOME URL are both non-www
    • in wp-config.php make sure the DOMAIN_CURRENT_SITE is non-www
    • in wp_blogs and wp_site make sure everything’s non-www
    • in wp_options and all wp_*_options make sure home and site_url are non-www

    As I said, your .htaccess rewrite for taking “www” to non-www should be JUST for “www” not it shouldn’t be written to remove any sub domain like “new”

    RewriteEngine On
    RewriteCond %{HTTP_HOST} ^www.example.com$ [NC]
    RewriteRule ^(.*)$ http://example.com/$1 [R=301,L]

    new.example.com would still be recognized w/ the above. (I imagine you have something like ^.example.com$, to remove the www instead of ^www.example.com)

Viewing 1 replies (of 1 total)
  • The topic ‘htaccess issue for converted multisite site’ is closed to new replies.