• Hi ! I maintain a quite big WordPress+Buddypress install, that was originally built on a wp2.8.6 release. WordPress core had been patched, and maintenance was almost abandoned during 2 years because the update would have replaced patches : no update, nothing.

    While installing a local development server, I noticed the database does not contain a wp_options table. The same database is used without a problem on the production server, and AFAIK it works perfectly.

    Is it normal? Any idea about what could have caused this? and about what I should do?

    Thanks a lot…

Viewing 3 replies - 1 through 3 (of 3 total)
  • Is there any *_options table at all? I find it hard to believe that the installation works without one. Very key information is kept there, and it is accessed all the time.

    Thread Starter buzug

    (@buzug)

    Yes, there are a lot of wp_NUMBER_options tables, one for each blog of the multisite install, but no simple wp_options table. It seems the wp_1_options is used as the repository for network-related options.

    In fact my aim is to know whether it’s abnormal (= I shall perform some maintenance actions in order to fix the database) or not (= I can work on something more useful ! 🙂 )

    Ok. You have multisite.

    That might be normal. I have never used WPMU or enabled multisite so I can’t make any promises, but it matches my limited understanding of how multisite works.

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

The topic ‘No wp_options table : normal or not’ is closed to new replies.