This system now has its own page, rather than being a simple blog entry. As such, comments are closed here. Please leave new comments on the new page.

The new version has _significantly_ improved ease-of-setup, plus working domains and subdomains, new functions for your themes, and a VUSER constant that you can use to specify the current blog (great for customizing themes!)

Check it out!

Well, okay. New and improved for me. I can’t give you guys _all_ the goodies.

Version 2.0 should be up tomorrow. Just some final touches, packaging, and upload.

Your code is _very_ similar to what I was trying to make work.

It appears that the wp_cache_set() function is what I was missing. I would change the prefix and the $wpdb elements I needed, but returned the first blog’s data twice. I’ll definitely check this out. Thanks!

In my I need to display the most recent post from one blog, and then the last 5 posts from two other blogs, and this code seems to do the trick. I do this for each blog I am pulling from:

//map the wpdb table names with the new prefix

$blog_prefix = 'bob_';
global $wpdb;
$wpdb->prefix = $blog_prefix;
$wpdb->posts = $wpdb->prefix . 'posts';
$wpdb->users = $wpdb->prefix . 'users';
$wpdb->categories = $wpdb->prefix . 'categories';
$wpdb->post2cat = $wpdb->prefix . 'post2cat';
$wpdb->comments = $wpdb->prefix . 'comments';
$wpdb->link2cat = $wpdb->prefix . 'link2cat';
$wpdb->links = $wpdb->prefix . 'links';
$wpdb->options = $wpdb->prefix . 'options';
$wpdb->postmeta = $wpdb->prefix . 'postmeta';
$wpdb->usermeta = $wpdb->prefix . 'usermeta';


//reload the query object with posts from new tables
query_posts('showposts=5');

//Permalinks and other post-related URLs are prepended with the value of the ‘home’ option
//so we need to override this with the new proper value for the blog we’re pulling from
$old_option = get_option('home');
wp_cache_set('home', 'http://www.mysite.com/bob/', 'options');

loop over posts…

//Restore the original ‘home’ option so any remaining links render correctly
wp_cache_set('home', $old_option, 'options');

In synch with your advice, I pursued the symlink scenario with HostGator and the great guys there worked overtime to figure out that Allen Gurrea’s symlink instruction wasn’t quite right, at least on their server.

I was on target with the thought that something minor such as a missing space or something-or-other could make all the difference in the world. For my situation, it was a missing forward slash.

Allen’s pHp symlink script “home/user/public_html/cat” didn’t work for me until we added a forward slash upfront to make it “/home/user/public_html/cat”.

Something just that simple ripped more time out of my hide than I want to think about, but it appears to have resolved the issue. So everything looks good and I’m moving forward.

Thanks for your innovative work and the opportunity to post here.

I haven’t quite figured out the details, but am experimenting with rewriting the $wpdb table names with the correct prefix for the blog I am trying to query at that moment, retrieving the original query string, and then re-calling query_posts with it. I was wondering if you were doing something similar or found a more elegant solution?

Thanks, looking forward to your next release!