Ready to get started?Download WordPress


[resolved] Revert Muti-site back to single site (13 posts)

  1. rsgrone
    Posted 2 years ago #

    Has anyone come up with a workable plugin to reverse engineer the site along with the database to revert a multisite back to a single site yet?

  2. rsgrone
    Posted 2 years ago #

    Thanks I had one issue though...

    User admin had privilieges set to: 'wp_capabilities', 'a:1:a:1:{s:10:"subscriber";s:1:"1";}' which I needed to change to: 'a:1:{s:13:"administrator";s:1:"1";}' less I obviously had only subsriber privileges...

    Next, although I never created any additional "blogs" (which is one reason I wanted to revert back) I still have a plethora of tables marked as: wp_1_

    Can I delete these as well?

    All seems okay so far however, I will need to change my Google Sitemap plugin I think since I was using the multisite flavor...

    Any ideas on what I can do with the additional wp_1_ tables? I believe they are carry overs from the MU days...

    wp_1_term (group of 3) to save time tax, relation, terms

  3. rsgrone
    Posted 2 years ago #

    WEll I backed up the database and dropped the wp_1_ stuff and the numer of posts/coments did not change although, I honestly forgot to check how many there were prior to reverting back as your instructions indicated.... so, the bottom line here is, I think the only major issue I had was having to go into MySQL Query Browser and and execute two changes:

    admin had to be assigned to blog "0" in usermeta
    admin privileges had to be changed to "admin" from subscriber however, with multisite running I never had a problem with "admin" being a "subsriber"

    If you feel I may have caused damage, please let me know...

    Thanks Andrea

  4. Um, those wp_1_tables are where your blog posts live. Unless you have wp_posts as well?

  5. rsgrone
    Posted 2 years ago #


    That is correct, I had the identical tables wp_ and just posted two new articles... all seems well...

    I think the transition from MU to 3.o wasn't as seemless for me as I had thought... I guess I will really know with the exception of looking at the original database I kept but, it appeared the posts were duplicated as, the posts in wp_1_tables stopped updating back in I think, 2010...

  6. rsgrone
    Posted 2 years ago #

    I just checked using the archives widget.... it appears everything is there since opening in 10/09...

    Maybe that is why the "admin" was assigned to blog "1" instead of "0" like everyone else... [dramatic pause] and maybe, that is what caused my site to begin loading slowly... I have no idea... you?

  7. As I stated in a previous thread.. there is no blog 0.

  8. rsgrone
    Posted 2 years ago #

    As I replied to your repeated comment in the other thread...

    In the wp-usermeta table there is the following entry
    19, 1, 'primary_blog', '0'

    Now, when mine failed after the rollback, I had to change

    19, 1, 'primary_blog', '1'

    to the above hence, the reference to "blog 0" whereas, my lack of technical expertise would lead me to restate that, "primay_blog" maybe set to "something other than 0 (zero)

    If you would like, I will post the entire entries for a single given user within the wp_usermeta table....

    Maybe I could get an explanation as to how, when I created the multi-site using some plugin my "primary-blog" (excuse the blog "0" reference as it is referenced that way in the table) was set to something other than "0" like all the other registered users...

    Complicating matters, my user level within the same table for admin, was set for "subscriber"

    Now, I know I did not intentionally go into my DB and make those changes to make my life difficult....

  9. when I created the multi-site using some plugin

    This is the culprit - you used a plugin to set up the network. You don't need to.

  10. rsgrone
    Posted 2 years ago #

    I never relaized that the "Enable Multi-site" made changes to the database.... I thought it had something to do with the upgrade from MU (which was extremely painful) that caused the bulk of my problems...

  11. You didn't need to enable multisite to upgrade from MU either. That would have screed up quite a bit.

    The devs tried to make it as easy as possible to just... upgrade... when the time came. A few people still thought they had to enable the network. you were on MU. You already *had* a network.

  12. rsgrone
    Posted 2 years ago #

    I never did any of the above... I simply extrapolated what I need from the database, did a clean install of 3.0 converted to multisite, and reinserted the necessary via Import as, no matter what I tried, at the time, WP was still having issues with sites running on a real web server, Windows IIS 7.5 which seems to have cleared itself up with Microsoft migrating their users to WP from their former "blog"...

    As it stands now, the url rewrites needed are being properly being applied to web.config along with .htaccess for a seamless install... I would like to thank Microsoft for their commitment to their customers to once again, insure their customers were/are free to provide a plethora of services via a extremely wide range of platforms... (Quite frankly, Movabltype needs to get onboard with all this as well to stay competitive as, WP has certainly taken the lead)

    So, the bottom-line was; being unable to perform the suggested upgrade from MU to 3.0 as stated, a fresh install and import was accomplished... looking historically o the web, you will find there were plenty of other forums operating with users working to resolve this issue...

    Thanks for the help, I simply needed to establish why on the single install, wp_ was created and files loaded to same while, the multisite seemed to "mash" the two together and continue to operate

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.