The View From Here

I am about to embark upon the task of con­vert­ing my var­i­ous, sep­a­rate Word­Press instal­la­tions into one cen­tral Word­Press Mul­ti­site.  So, same sep­a­rate blogs with their same sep­a­rate domains, themes, cus­tomiza­tions, plug-ins, and (most impor­tantly) con­tent … into one uni­fied back end.  This was pre­vi­ously pos­si­ble using Word­Press MU, a sort of break-out from the pri­mary Word­Press project.  While I played around with MU a bit, I ulti­mately decided to go with sep­a­rate installs as too many plug-in’s were incom­pat­i­ble with Word­Press MU. For­tu­nately, the Word­Press 3.0 upgrade adds what MU did, but into the offi­cial Word­Press project.  Plug-in’s can be re-written to take advan­tage of global vari­ables, but all plug-in’s and themes are un-effected by the tran­si­tion as they still oper­ate inde­pen­dently among the var­i­ous blogs.  This is what I have been wait­ing for.  Finally, I can have what MU did, but can have it the way I always wanted it — prac­ti­cally seam­less and cer­tainly allow­ing for less work by me (as the admin) on sep­a­rate back-ends. There­fore, this post shall doc­u­ment the tran­si­tion from my mul­ti­ple Word­Press blogs into a Word­Press 3.0 Mul­ti­site. First thing’s first — the Word­Press Codex: Migrat­ing Mul­ti­ple Blogs into Word­Press 3.0 Multisite Word­Press 3.0 includes new [ ... ]