[resolved] db name gets prepended to every new sub-site name (6 posts)

  1. xorred
    Posted 5 years ago #

    Here is my wp config:

    define ('WPLANG', '');
    define('WP_ALLOW_MULTISITE', true);
    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/';
    define( 'DOMAIN_CURRENT_SITE', 'winetrailers.com' );
    define( 'PATH_CURRENT_SITE', '/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );

    Every time I try to create a new site, say, "testwinery", it creates a site with a name of "winetrailers_com_3testwinery/"

    Now... I know this is extremely weird and have absolutely no idea where it came from (brand new install) or how to solve it... any ideas?

  2. xorred
    Posted 5 years ago #

    oh, and when I click on "dashboard" for that site, it takes me to "http://winetrailers.comwinetrailers_com_3testwinery/wp-admin/"



    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
    RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]

    Oh... when going to winetrailers.com/testwinery/wp-admin (testwinery is (was) supposed to be the sub-sit ename) and changing a theme, it changes the main site theme...

  3. Check the rest of your WP-config file for another entry of BASE.

  4. xorred
    Posted 5 years ago #

    You were right!

    Reason: the Dreamhost f**ktards who did not understand that their one-clickinstalls were so screwed up they had 2 $base variables...

  5. Bingo :) DreamHost does that, alas, and it screws up a lot of people :/ this is why auto installers are bad.

  6. And yes, I told them when 3.0 came out, they said they'd look into it and it is still not fixed.

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.