The MU forums have moved to WordPress.org

only snapblogger.com/b/ works. www.snapblogger.com/b/ fails. (10 posts)

  1. dgwade
    Member
    Posted 17 years ago #

    Links inside MU default to the http://www.snapblogger.com/b/ format but always fail while if I remove the www to simply snapblogger.com/b/ the links work.

    How do I fix this? I'm installed into the subdirectory b of course.

  2. amnesiak
    Member
    Posted 17 years ago #

    are you with dreamhost?

    If so, change your set up to always remove it (remove the www).

    I had that issue with an old host (Hostgator), I moved hosts.

  3. drmike
    Member
    Posted 17 years ago #

    Might help us help you if you told us what yout .htaccess file looks like, what changes you're done to your DNS, etc.

    You have some serious issues though.

    http://www.snapblogger.com/b/ actually reloads to http://snapblogger.com

    When you click the 'b' subdirectory, we do get the WPMU install but it appears your themes are broken since no CSS loads.

    edit: Something must be wrong with your install since I can't even get http://www.snapblogger.com/b/wp-content/themes/home/images/kubrickheader.jpg to load.

  4. dgwade
    Member
    Posted 17 years ago #

    I've done NO changes to dns.
    Files outside of wordpress resolve with or without the www. Only wordpress files fail to work with the www. format.

    .htaccess is as follows
    -----------------------
    RewriteEngine On
    RewriteBase /b/

    # Rewrite http://www.domain.com to domain.com
    RewriteCond %{HTTP_HOST} ^www\.(.*)
    RewriteRule ^(.*) http://%1/$1 [R,L]

    #uploaded files
    RewriteRule ^(.*)?/?files/(.*) wp-content/blogs.php?file=$2 [L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

  5. dgwade
    Member
    Posted 17 years ago #

    I deleted the .htaccess file and it seems to work now. Does anyone know why my installation at snapblogger.com would work without the .htaccess file whereas normally this file is apparently required (created during the installation)?

  6. dgwade
    Member
    Posted 17 years ago #

    Wrong! When the .htaccess file is deleted then the admin/main login, page, theme, and everything works normal. However, user pages can't even be found.

    I have 2 ordinary users defined which are dgwade and pappaw. With the .htaccess file as installed these weblogs work successfully. But the admin user works strangely if at all (only with snapblogger.com, never with http://www.snapblogger.com).

    With the .htaccess file removed, the admin user works fine BUT the ordinary users don't work at all (not found, and can't login).

    Still need help here!

  7. dgwade
    Member
    Posted 17 years ago #

    If it helps, I got the following in the error.log when installing:

    [25-Aug-2006 15:16:08] install_blog - ID: 1 URL: http://com/b/snapblogger/ Title: Your WebLog Community

    Notice the http://com/b/snapblogger/ where com should be snapblogger.com and snapblogger was never intentionally specified as a subdirectory or path beyoud /b/ . The installation was intended to be http://snapblogger.com/b/ and using that url works whereas using http://www.snapblogger.com/b/ does not work.

  8. dgwade
    Member
    Posted 17 years ago #

    Not really resolved BUT after deleting the existing install and installing under a single subdomain as in my.domain.tld it seems to work successfully now. I did this because simple domain.tld/b/ worked but http://www.domain.tld/b/ did not work. Installed as my.domain.tld there is only one domain which removed the complication.

  9. mogloo
    Member
    Posted 17 years ago #

    I'm having a similar problem as dgwade. Everything works if I go to http://domain.com/wpmu/user , but if I include the www and go to http://www.domain.com/wpmu/user it forwards to http://domain.com/user (which doesn't exist). The automatically created .htaccess file must have some problem...

  10. thatposhgirl
    Member
    Posted 17 years ago #

    I wanted to add that I had to delete the htaccess file, as well. My situation is that I have mydomain2.com aliased to mydomain1.com/sub and when someone would enter http://www.mydomain2.com the htaccess file was causing them to go to mydomain2.com/sub and that was causing an internal server error.

About this Topic

  • Started 17 years ago by dgwade
  • Latest reply from thatposhgirl