rcwatson

Ok, well, that answers that question. Quite literally, I didn’t change a thing in wp-config.php, other than the prefix setting (which should have been fine the way it was) so as to be able to get back to seeing the site again.

All the more reason to start with a fresh 3.2.1 install, which is what I’m doing now. Thanks for the clarifications.

I didn’t rename the tables to wp_1. WordPress did that for me way back when I set up the first blog in the network. I’m just trying to get back to where wp-config.php recognizes this…back when $table_prefix was, correctly, ‘wp_’.

Andrea, sorry about that. I honestly didn’t know about pastebin until you mentioned it. Brilliant! wish I’d known about it before. by pasting the entirety, I was trying to show (prove) just how ridiculously similar the wp-config.php files were, but with two entirely different outcomes.

I honestly don’t remember if I upgraded or installed WP 3.0 merge outright. We (my network admin and I) had to do a number of installs to get to this point (learning curve), so I’d like to think it was a 3.0 setup to begin with. Then again, there might have been a point where we dumped a pre-3.0 database and then imported it into a post-3.0 database. Would that have had a negative effect? (Probably, duh… ?? )

Ipstenu, what I meant was wp_posts, not having a site number designation in its name, is for the “root” blog of this multi-site instance. But the real problem is, how do I make the site see the wp_users table again, but still display posts from wp_1_posts? For a temporary fix, can I rename wp_users to wp_1_users to make it work until I can get a fresh 3.2.1 install to switch over to?

Back to this. So, I will need to backup and then wipe out my DB, then reinstall WordPress (upgrading to 3.2.1 now) and re-import content (not the whole original DB) to get it to be a pure WP 3.2.1 install?

anyone have any idea on this?

Is there a way that I can refresh my wp-config to act more like a straight-up 3.1.1 install, rather than an evolution from WPMU? For example, do I just back up, then delete wp-config.php and let a new one generate as I go through the install wizard, and then add any customizations necessary after that?

Yes, come to think of it, this would be an upgraded WPMU install. It’s been a long time in development, as you can tell, but it’s now at 3.1.1.

Thanks, Ipstenu, I’ll look into that as well.

Hmm. Well, I looked at another thread which recommended I change define( 'SUBDOMAIN_INSTALL', true ); to define( 'SUBDOMAIN_INSTALL', false );

When I do that, it fixes the problem (with a warning on the home page to drop the define('VHOST', 'yes'); definition from wp-config due to deprecation, so I commented that out).

But doesn’t this mean now that I can’t use subdomains for additional blogs on my Multi-Site setup? I’d really like to use subdomains, but I still want to avoid the problem defined at the beginning of this thread.

Andrea, thanks for the tip. However, in my case when I add that line, going to example.com instead now just returns a blank page (no source at all). I’ve even tried using the Redirection plugin to redirect example.com to https://www.example.com but it seems to ignore that directive.

I’m stumped. Any ideas?

Thanks!

Resolved: I had to completely back off the BP wiki component and front-end admin component and start over. The wiki posts were still in the system, so I was able to restore those, but I had to copy/paste them back in via the bp-wiki interface.

Andrea_r, I don’t want to hijack this thread, but I believe the subdomain and network issue is also related to another issue I’m having with BuddyPress. Can you weigh in on a separate post about that?

Thanks.

I’m also “installed in a folder” apparently, but I’m not quite sure what that’s referring to. I mean, presumably the wordpress files and folders have to reside in DocumentRoot, which itself is a folder. What exactly is WordPress looking for here?

I’ve done this to other blogs without a hitch, but this one has me stymied.

My wordpress is in a user home directory something like this:

/data01/home/username/production/wordpress/

and that’s exactly what DocumentRoot in the Apache vhost settings is pointing to. WordPress does work, but doesn’t allow subdomained network. What piece am I missing?

Sorry to but in with a tangent question, but where is the style “textwidget” defined? I can’t seem to find it in any of the twentyten theme’s CSS. When I try to modify it locally in my page with a style attribute change at the <div> tag level, nothing happens.

Ah! That’s what it was! Thank you. It was driving me crazy.