• I’m trying to setup network blog support so I can host multiples blogs in one install. Every seems to go smoothly, right up to the point when I enable network blog support and have to re-login in. Instead of a getting a login page, I get a page “Error establishing a database connection”.
    Obviously there is not issue connecting to the database, since the initial install went fine. If I try to go to the wp-admin directory, then I get an error “One or more database tables are unavailable”. I enabled repair and tried repairing, but that fails with error that the tables don’t exist (i.e. de_2_posts, de_2_comments, de_2_links).
    I’m tempted to create those tables manually to see what happens, but I shouldn’t have to.

    I can turn multisite support off and everything works fine as a single instance, so this is not a database connection issue. I do have control over the server, but I am not installing in the root directory. The install URL is blog/de/

Viewing 4 replies - 1 through 4 (of 4 total)
  • If you read requirements on codex

    WordPress Settings Requirements

    * Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. It interferes with the member blog lookup.
    * You cannot create a network in the following cases:
    o “WordPress address (URL)” is different from “Site address (URL)”.
    o “WordPress address (URL)” uses a port number other than ‘:80’, ‘:443’.
    * You cannot choose Sub-domain Install in the following cases:
    o WordPress install is in a directory (not in document root).
    o “WordPress address (URL)” is localhost.
    o “WordPress address (URL)” is IP address such as 127.0.0.1.
    * You cannot choose Sub-directory Install in the following cases:
    o If your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. (This problem will be fixed in a future version. See Switching between subdomains and subfolders for more information.)

    You cannot install wordpres in folder and have network it needs to be in root.

    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.

    * Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. It interferes with the member blog lookup.

    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.

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

The topic ‘Trouble enabling up Network Blog support’ is closed to new replies.