Using 0.5.4.3 and WordPress 4.0 bug?

It won’t be in the mapping table until mapped. In the options, what is the id? Just verify that it is 1. It should be, but check.

Oh…different thought. Did you copy the network setup bits to htaccess and config? Just checking.

My first site’s id number is 2. Try id number 2, somesite1.com, and check primary.

Yes network activated. But it only shows on network admin. I think you are there. Just need to get it mapped.

I was surprised to learn that plugins that are network activated do not show in the individual sites as plugins. The functionality is there but no control in the plugin menu. I guess this makes sense because by network activating you are removing control from individual site admin.

So if I want everyone to use a plugin, I network activate it. Each admin can do settings for their site but can’t deactivate or delete. To them it is just part of the site.

Domain mapping is invisible in the sites but controlled in network admin. So what you are seeing sounds right.

Yes, I used ID1.
Nothing showed up in the table but since I hit SAVE, it should have.
Yes, I copied those things during the initial network setup.

Yes, I would understand why network activating that plugin would not show up in other sites. It makes perfect sense.

The document doesn’t however because it eludes to the user going to their first (primary) site to add that first site.

LOL, and this is why I’ve constantly decided to simply rebuild everything. This is a new problem I’ve not seen before yet I’ve gone through this same setup countless times now ??

I think you have it this time.

Just try 2.

I don’t remember if it gives an error message if mapping fails or if it just doesn’t show. If you successfully map, the table shows up on that screen.

You’ll want to map each site twice…once for with www and one without. Pick one of those as primary and one is not. Id number is the same both times.

The biggest issue I see is that the id number doesn’t show up in the sites list in 4 like it did in 3.

In the database, I see the tables for the new site with the id number appended to their prefix.

Hmmm, you’re right, I forgot that 1 is actually the main site.
Ok, so that worked.

Site ID Domain Primary Edit Delete
2 https://www.somesite1.com Yes

Each new site should be set to primary right? This is another bit of confusion in the many docs I’ve read.

Connecting to https://www.somesite1.com from remote now gives me;

Nothing Found
It seems we can’t find what you’re looking for. Perhaps searching can help.

I had mentioned above that some folks say go into the network dashboard, sites, pick the site, then edit that new site.

In settings, change the Siteurl and Home to the full name so in my case, would be https://www.somesite1.com.

Did you do this?

In the mapping table, I now see what seems right;

id blog_id domain active
1 2 https://www.somesite1.com 0

>You’ll want to map each site twice…once for with www and one without. >Pick one of those as primary and one is not. Id number is the same both >times.

Wait now, I’ve never read this anywhere? Then again, I never read the full doc yet either since I got stuck at this point.
Map each site twice?

Yeah!

Primary just gives you the choice to redirect https://www.somesite1.com to somesite1.com.

I have a client with too many domain names, so I have to redirect several to one site…So not always primary.

Say I want without www to be primary.
I can then add https://www.extraname.com as not primary and extraname.com as not primary. If somesite.com is primary, no matter which one the user types in, they get somesite.com

And…there is the usual internet window when things may go odd places. Can be up to 24 hours but usually less as the domain propagates.

You did it!

That may not be in the document. And I may be wrong but it is something I learned to do for seo a long time ago. It isn’t a making thing, but an seo cannonical thing.

I admit to doing it without full understanding of why. Grin. I think it consolidates hits and prevents duplicate content.

There’s a swypo there. That was supposed to read: it isn’t a mapping thing…

>Primary just gives you the choice to redirect https://www.somesite1.com
>to somesite1.com.

Oh, so, sort of an alias function within a networked multi-domain setup?

LOL, I’m getting out of sync with you now :).

So, what do you think my next step should be? DNS is obviously sending the traffic to the main site, which in turn needs to send that to the proper domain now.

When I look in Network/Dashboard/Sites, I see no mapping on either the main site or the new site I just entered. That section is blank.