Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter BSPBrent

    (@bspbrent)

    This is my current wp-config.php for the site and blog IDs.

    define( ‘SITE_ID_CURRENT_SITE’, 2 );
    define( ‘BLOG_ID_CURRENT_SITE’, 1 );

    I had tried setting the site_id in all the tables to 1, along with the blog_id, but I still got the database connection error. I dropped all the tables and started over, setting the SITE_ID_CURRENT_SITE to 2. Now everything seems to be working. So the SITE_ID_CURRENT_SITE may need to be changed to what is in the database in addition to the blog_id change.

    Everything seems to be working now. Thanks for everyone’s help!

    Thread Starter BSPBrent

    (@bspbrent)

    I got the network blog install to work by changing the blog_id in the de_blogs table to 2. However, I also needed to change the SITE_ID_CURRENT_SITE constant in wp-config.php to 2, since that is the starting ID.

    Would changing the BLOG_ID_CURRENT_SITE constant to 2 have worked also instead of updating the database? That seems more of a straightforward solution to work around this “feature”. Not that it’s hard to update the database.

    Thread Starter BSPBrent

    (@bspbrent)

    Yes, the “id” in de_site is 2. For the database server it is on, the auto_increment_offset is set to 2, so that would be the starting increment id.

    Thread Starter BSPBrent

    (@bspbrent)

    oh no. so does that mean I’m stuck!? Does anyone know where in the code I can check for this?

    Thread Starter BSPBrent

    (@bspbrent)

    I started over with a clean code download. I did not have the WP_ALLOW_REPAIR setting in place and still had the same issue. I tried creating the tables manually, but still got the database connection error.

    My databases are set to have an auto increment increment of 3 for replication, but WordPress is looking for de_2… tables. But that is an interesting suggestion. I would certainly hope WordPress doesn’t have issues with increment values.

    I enabled the repair option and tried to “repair” the tables, but everything came back ok.

    The de_users table is okay.
    The de_usermeta table is okay.
    The de_2_posts table is okay.
    The de_2_comments table is okay.
    The de_2_links table is okay.
    The de_2_options table is okay.
    The de_2_postmeta table is okay.
    The de_2_terms table is okay.
    The de_2_term_taxonomy table is okay.
    The de_2_term_relationships table is okay.
    The de_2_commentmeta table is okay.
    The de_blogs table is okay.
    The de_signups table is okay.
    The de_site table is okay.
    The de_sitemeta table is okay.
    The de_registration_log table is okay.
    The de_blog_versions table is okay.

    Thread Starter BSPBrent

    (@bspbrent)

    These are the tables that get created:

    de_blog_versions
    de_blogs
    de_commentmeta
    de_comments
    de_links
    de_options
    de_postmeta
    de_posts
    de_registration_log
    de_signups
    de_site
    de_sitemeta
    de_term_relationships
    de_term_taxonomy
    de_terms
    de_usermeta
    de_users

    Thread Starter BSPBrent

    (@bspbrent)

    I did not turn off plugins, I emptied the plugins directory. To double check, I turned off multisite and login into the admin area. Switching to plugins shows “No plugins to show”.
    For the record, I did create the blogs.dir directory and it is writeable by apache.

    It seems to be failing to create the initial network blog tables (i.e. de_2_*).

    Thread Starter BSPBrent

    (@bspbrent)

    All the proper configs are there. This is my current config, with the domain changed to be generic. I’m not providing the database login info. That is not where the problem is, otherwise I wouldn’t be able to get past the initial setup to enable network blog via the admin interface.

    /** Database Charset to use in creating database tables. */
    define(‘DB_CHARSET’, ‘utf8’);

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ‘utf8_general_ci’);
    $table_prefix = ‘de_’;

    define(‘WP_DEBUG’, false);
    define(‘WP_ALLOW_MULTISITE’, true);

    define( ‘MULTISITE’, true);
    define( ‘SUBDOMAIN_INSTALL’, false );
    $base = ‘/blog/de/’;
    define( ‘DOMAIN_CURRENT_SITE’, ‘www.mydomain.com’ );
    define( ‘PATH_CURRENT_SITE’, ‘/blog/de/’ );
    define( ‘SITE_ID_CURRENT_SITE’, 1 );
    define( ‘BLOG_ID_CURRENT_SITE’, 1 );
    define(‘WP_ALLOW_REPAIR’, true);

    Thread Starter BSPBrent

    (@bspbrent)

    All the base tables are there. As I mentioned, single blog setup works just fine. This is not a problem with access to the database. But yes, the db user does have ALL permissions.
    I’m not on any host, I’m managing my own servers. Four load balanced web servers. WordPress is on NFS to be available on all web servers and ease of configuration changes.

    DOMAIN_CURRENT_SITE is set to my domain with ‘www’.
    $base = ‘/blog/de/’;
    define(‘PATH_CURRENT_SITE’, ‘/blog/de/’);

    Since those values do not change when enabling multisite setup, I doubt the issue is with those declarations.
    I have setup WordPress v2 many times, including the blogs used by wired.com. I’m not new at this by any means, just new to the multisite feature.

    Thread Starter BSPBrent

    (@bspbrent)

    Yes, I saw that in your first response. If you click on the link “Giving WordPress its own directory”, it explains a special case which I am not trying to implement:
    “WordPress allows you to install the WordPress files to a subdirectory, but have your blog exist in the site root.”

    I appreciate your help, but reposting the manual is not helping. I’ve read it multiple times and followed all the directions. I just managed to set it up as a localhost install without a problem, with the subdirectory setup I posted.

    There may be something with my server environment that is different. Perhaps the fact I’m load balancing 4 web servers and have WordPress on NFS.

    Thread Starter BSPBrent

    (@bspbrent)

    I’m not trying to have any of my blogs accessible as root. I want the blog addresses to be blog/de/blog1, blog/de/blog2, etc. I want WordPress to function under the blog/de/ directory and all network blogs off of that.

    Clearly the database error is not the correct error being generate. The base tables are created just fine. I’m going through the WordPress code now to figure out what is actually going on.

    Thread Starter BSPBrent

    (@bspbrent)

    Yes, multiple times. I just posted the relevant “defines”. As I mentioned, the single blog setup I can get working fine. Everything works if I change MULTISITE to false.

Viewing 12 replies - 1 through 12 (of 12 total)