Using 0.5.4.3 and WordPress 4.0 bug?

Ron, yes, the domains point to the IP of the server.

In Apache, I have a ServerAlias for each domain which the main domain should be responding for.

At least, this is what I’ve read needs to be done on the Apache side.

Anyone?

The plugin DOES work with 4.0, right?

Yes.

When I try to access the dashboard for the #2 site, I get the dashboard for the #1 site.

When I try to access the dashboard for the #3-#5 sites (unmapped) I also get the dashboard for the #1 site.

Since you have the same issue on all subsites (mapped or not). The simple way to eliminate DM from troubleshooting is remove it from your install until you get sites 3-5 working.

Anyone?

@bloggy2013 – what I suggested you check in my previous response to you was in your client/customer’s DNS vs your webserver.

Okay. I tried network disabling the plugin and it locked me out of everything. I’m not even going to try and sort this out at this point. All I can think is that I must’ve messed up the database somewhere in my initial setup.

So, I’m going to start over from scratch and re-arrange the domains on my server. I’ll check back in when it is done and let y’all know if it works.

I’m pretty sure this was my error from that initial setup.

Things I’ve learned:
1) must be set up in the root directory
2) start with your primary domain FIRST — don’t try to change which is primary later.

Hi Ron,

>what I suggested you check in my previous response to you was in
>your client/customer’s DNS vs your webserver.

I run the DNS servers as well so know that everything in DNS is correct.
Unless I am not understanding your reply?

The problem here is that this is taking days and days and there are several of us who would like to get this working.

I appreciate your help Ron, I’m just not sure how to get anything done in an efficient amount of time.

Ron — thanks for the help. Here’s what I did:

1) delete everything (sigh)
2) created a new main domain for my server that more correctly represented the logic of what I do. This way, everything could fall back to that without conflicts.
3) had the hosting company rename my account to put that domain as primary.
4) installed wordpress 4.0 in the root directory of that new domain
5) installed domain mapping plugin
6) began importing the blogs. I’ve got 2 of them done and one live.
7) parked and domain mapped 1. Will try with more soon.

I can access all control panels and sites. So — it was something I’d botched in the database during the install.

I’ll let you know if anything changes, but I think this fixes it.

I just noticed this in the log, someone hacking at this plugin.

[Sun Oct 05 15:48:30 2014] [error] [client 180.76.6.147] PHP Warning: Creating default object from empty value in /var/www/html/wp-content/sunrise.php on line 23
[Sun Oct 05 15:48:30 2014] [error] [client 180.76.6.147] PHP Warning: Creating default object from empty value in /var/www/html/wp-content/sunrise.php on line 31

Interesting that someone would specifically look for this file. Could this mean a potential exploit being worked on?

Anyhow, my setup is still not working so I am still stumped.

Bloggy, isn’t sunrise.php a file used by several plugins? I thought it was a common piece.

Re getting your site working, was there anything non standard in your setup? I followed instructions to edit the database for a non standard setup and that is how I messed up before. I now have 6 sites up in mixed stages of completion, all working well.

I also learned to add my main user to each site or it would not show up in my list of sites even though it was there.

I hated stripping down and starting over, but it is working fine now…

I think it broke when I changed the primary site from 1 to 3…I think.

@bloggy2013 – get sunrise.php from the development version. The warning is fixed in that version,

Thanks Ron.

@deleyna, nothing unusual, just a brand new wordpress install. I followed all of the information I could find and am where I am with only two sites working. The rest never work.

I’m not sure what you mean about editing any database, I’ve not seen any mention of such a task in any doc I’ve read.

@bloggy — I was only editing the database because I’d set up the MU installation wrong originally and I was trying to save it. ??

I’d changed from having my #1 site be the main site to try and use the #3 site as the main site. I don’t recommend that option.

My current installation is standard. Clean 4.0 MU installation. Added the plugin for redirect. (And of course many others for the various sites…) and they’re all working fine.

So…it does work. Don’t know what is stopping it in your case. Wish I could help. Good luck!

You can’t use instructions for WPMU, that is a different product.

You can’t use the Ottopress instructions mentioned in the plugin documentation; leaves things out.

I wrote https://lcblog.lernerconsult.com/2012-wordpress-3-multi-site-domain-mapping/ and it covers in detail how to set up Multi-Site and how to set up Domain Mapping. I even have how to recover from getting it wrong while trying to get it working.

Yes, it works on WP4.0, I have it on a several hundred site installation on IIS, they upgraded to WP4.0 over a week ago.

Yes, domain mapping only works on installations located in the root of your account or the root of a (real, not virtual) subdomain. That is a DNS limitation, not a limitation of this plugin.

Good to know. I wish I’d found better instructions the first time around, but I had them the second time — and it works like a charm.

Again, I re-installed a fresh copy then went through all of the steps which are simple enough for most anyone to follow.

There is a little confusion with how to set up the plugin, specifically, that of having to move the domain_mapping.php file to /wp-content/mu-plugins which immediately breaks the plugin.

If not moving this file, then even when the plugin is network activated, it never shows up in the main domain ‘tools’ as mentioned in;

Easy Way: User Domain Mapping page

***SNIP***

Click the Dashboard link.

In the Tools menu, select Domain Mapping
/wp-admin/tools.php?page=domainmapping