• Resolved thowden

    (@thowden)


    Hi All

    I’ve read a heap of links and searched but I cannot figure this out.

    I’ve got a fresh clean 3.1 install and no matter how I follow or not the instructions for setting up a Network / MU style WP it does not work.

    The underlying issue is that the tables that are apparently expected are not created. I can see that some people have observed that the resolution was after they manually created the tables but I should not need to do manual db edits. This should just work.

    Error is: One or more database tables are unavailable. The database may need to be repaired.

    Results of the repair are:
    tb_1_posts: Table ‘test.tb_1_posts’ doesn’t exist
    tb_1_comments: Table ‘test.tb_1_comments’ doesn’t exist
    tb_1_links: Table ‘test.tb_1_links’ doesn’t exist
    tb_1_options: Table ‘test.tb_1_options’ doesn’t exist
    tb_1_postmeta: Table ‘test.tb_1_postmeta’ doesn’t exist
    tb_1_terms: Table ‘test.tb_1_terms’ doesn’t exist
    tb_1_term_taxonomy: Table ‘test.tb_1_term_taxonomy’ doesn’t exist
    tb_1_term_relationships: Table ‘test.tb_1_term_relationships’ doesn’t exist
    tb_1_commentmeta: Table ‘test.tb_1_commentmeta’ doesn’t exist

    looking at the database these tables do not exist.

    Which suggests there is an issue with the installer for Network but I don’t know what is really expected to happen.

    I do know that there are
    11 tables created as a single site (default)
    17 (6 added) after Network Install process
    9 apparently missing are the site specific tables
    i.e. these would be ones listed above.

    I have followed all the correct steps several times according to the instructions. What am I missing ?

    cheers
    Tony

Viewing 14 replies - 1 through 14 (of 14 total)
  • Tim Moore

    (@tmoorewp)

    Have you checked the database user account you’ve assigned to WordPress? It needs to have ALL database permissions for the WordPress database.

    The only time I have seen this not working as expected is if your db server or mYsql is set to increment db tables by something other than 1.

    Can you find out if that is the case on your server?

    Thread Starter thowden

    (@thowden)

    Thanks for the comments.

    The db user account is set with all permissions and if it can create 6 tables then why not the other 9?

    The increment is set as 1 and I would expect that this would impact all tables not just some.

    I’ve turned on debug but that is giving me nothing and I am guessing that is because there is no error to report, i.e it is working as designed.

    More thoughts appreciated πŸ™‚

    cheers
    Tony

    On a brand fresh new install of multisite, under no circumstance should it be searching for wp_1_anything.

    Those tables were for WPMU. they are not used in multisite. that’s how WP tells the difference.

    Are you following the actual instructions in the codex? Or my ebook? Or just some random blog post somewhere? Or are you using the plugin (which doesn’t help)?

    Thread Starter thowden

    (@thowden)

    Hi

    My references are as follows:

    http://codex.wordpress.org/Create_A_Network
    http://codex.wordpress.org/Debugging_a_WordPress_Network

    and following the prompts in the wordpress install / admin pages

    cheers
    Tony

    Thread Starter thowden

    (@thowden)

    Hi again

    Thanks Andrea_r!!

    Given that it was not a WP issue (and I should have checked this before) I went looking a little deeper.

    Apache error log showed the following:
    Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden:

    I reviewed the httpd.conf of my server and apparently
    AllowOverride All
    does not accept All permissions from the .htaccess file.

    I had to add
    Options +FollowSymLinks

    within the directives for the test site that I was using.

    cheers
    Tony

    Thread Starter thowden

    (@thowden)

    Now the only question remains is that WP was looking for tables that are prefixed wp_1_tablename on a fresh install and now that I have the rewrite rules working and can create site(s), the first site created is wp_2_tablename rather than wp_1_ (noting that the 2nd site I created is prefixed wp_3_tablename which highlights the increment by 1
    is correct).

    I may be confusing the concept of sites and blogs.

    The blogs table has 3 blogs identified including the #1 default single site blog and each entry is within the #1. So 1 site with 3 blogs.

    Yet the admin area refers to creating new Sites within the Network Admin area. So is a Site a Site or a Blog. Probably this is a whole new question.

    cheers
    Tony

    Thread Starter thowden

    (@thowden)

    Oh bother !

    I have just tried to do another fresh install of 3.1 to confirm in my own mind that it does work correctly and I am back where I started – see the first post in this thread.

    I have followed the codex details and have ensured that I am not getting errors from Apache or anything else.

    I have repeated this process on another server and it worked first time. So it is server / apache / something local. But I cannot figure it out.

    Giving up at this stage.

    Thanks for the help to date.

    Yet the admin area refers to creating new Sites within the Network Admin area. So is a Site a Site or a Blog. Probably this is a whole new question.

    they are called sites in the admin area, but the blog tables are what corresponds to that.

    The fact that it makes wp_1_tables off the bat is what concerns me. It shouldn’t do that at *all*.

    Thread Starter thowden

    (@thowden)

    Hi Andrea

    The issue is that it is not creating the wp_1 tables and then looking for them. So if MU is not meant to create them, it’s not, but then why is it looking for them and failing.

    I thought I had it yesterday with the FollowSymLinks issue but I have tried to replicate it and it is not working again.

    I have it all working in production (my hosted server) but not on my local dev system which I do need. It must be an Apache setting or possibly php (at a stretch) but its not permissions as i have 777’d everything as a test and it still fails.

    just another thought: It is the Repair Database utility that says they are missing and not necessarily the cause of the error. I had tried debugging etc but there were no errors reported so it seems that it is working as designed within WP which just highlights that it is an issue with server / supporting system configuration. (I think)

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    It shouldn’t be looking for WP_1_* anything, though. In WPMU it looks for that, but not MultiSite, which treats WP_ as Blog #1

    Thread Starter thowden

    (@thowden)

    Which sounds to me like it is failing for some reason (probably not the missing tables but thats the default error message) and asking for the repair, and the repair utility is not ‘thinking clearly’.

    File a trac ticket.

    I encountered this as well. It was because I was missing “define(‘MULTISITE’, true);” in wp-config.php.

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

The topic ‘Network Creation not creating tables’ is closed to new replies.