annathepiper

Last update, I think: SUCCESS!

As of tonight I successfully installed the new version of the WordPress MU Domain Mapping plugin, and got the #2 blog on my network, unseeliecourt.annathepiper.org, remapped over to https://www.unseeliecourt.net where I wanted it. ??

What I had to do to get it to work was:

1) Make sure my Apache vhost file for unseeliecourt.net was pointed to the same DocumentRoot as annathepiper.org
2) Make sure that the domain mapping plugin was pointed at https://www.unseeliecourt.net
3) ALSO edit the site data to change siteurl and home values to https://www.unseeliecourt.net so that my theme could work

So I think the majority of my questions are now resolved to my satisfaction. Thanks much everyone for your assistance and pointing me in the right direction! ??

Updating again to answer my own question:

I fixed my new issue by setting a NOBLOGREDIRECT value in my wp-config.php file, which I apparently needed to do because I had new user registration off.

More as I have it!

Andrea,

#1 – I don’t need to remap the main blog, just all the subsequent ones. ??

#2 – Noted!

#3 – I AM the host! All of this stuff is being done on my own server. ?? I just need to know what might need fixing. My Apache vhost file for annathepiper.org hasn’t changed; the ServerName still says https://www.annathepiper.org, and my ServerAlias says “annathepiper.org https://www.annathepiper.org *.annathepiper.org”, now that I’ve set up wildcard subdomains.

Edited to add: Since the forum seems to automatically change www-type links, please to note all references to https://www.annathepiper.org above are actually without the http bit in the front!

Status update on this:

Successfully converted one of my previous sites to the first blog in a network. For the interested, that site is https://www.annathepiper.org. (That’s my main personal blog.)

Pulled unseeliecourt.annathepiper.org in as a secondary blog on the network. This is also now working; the DNS appears to have propagated out at least some from my home network.

Remaining yet to do:

1) Figure out how to redirect https://www.unseeliecourt.net to the newly established unseeliecourt.annathepiper.org; am expecting that the previously mentioned domain mapping plugin might help here.

2) Must also figure out if I can still account for non-WP content involved with other secondary sites or if it all needs to be maintained in this new network.

New problem:

1) Before I converted annathepiper.org to the first site in a network, I had annathepiper.org and https://www.annathepiper.org both working successfully to direct me to the homepage of the blog. Now https://www.annathepiper.org is working, but annathepiper.org is redirecting to https://www.annathepiper.org/wp-signup.php?new=annathepiper.org, and shows an error message that says “registration has been disabled”. Does anyone know what I might have broken there?

Okay, update. Here’s where I am.

I was able to successfully create a test site, as I mentioned, and I spun off a second site on its network and tonight got content imported into it from one of my established sites.

What DIDN’T work was trying to set up the mu-domain-mapping plugin. It complained at me that it had to be installed in the root directory of my web server. I can’t do that on the grounds that I didn’t install this test install of WP 3 there–and I can’t, because there’s an established set of (non-Wordpress) webpages there already that I’m not going to overwrite.

What I’m trying to do instead is build a network off one of my previously established blogs, with its own domain, so that I can use THAT as the web root that the mu-domain-mapping plugin seems to want. I’ll report back if that works.

Thanks everyone for your replies!

Re: importing the content of my old blogs into the new network:

I assume that if I wish to import Blog A into the new network, I first need to create a new placeholder Blog A in the network, yes? And then I import content into it?

Giving that a try tonight but am finding that the new placeholder blog is throwing me 404s.