madivad

Great find, this has been bugging me for a while! Thanks!

Sorry this is late… but it’ll help others I suppose…

Depending on the theme you’re using and if it applies the “logged-in” class to the body (I believe the default theme does, as does the theme I use, as does the theme used by the author of the hint) you can use the method described here. Works as described and is very easy.

– Create a child theme to apply a custom style as detailed below, or use a custom style sheet plugin (I use the the Custom Style Plugin, and it does this flawlessly — plugin hasn’t been updated for a while, and the author says it works for wordpress up to 2.9.2, but I am still using it on 3.2.1 with no issues — I’ve been using this plugin for years!)

– add the following code to that CSS:

#nav li.logged-in-nav {
display: none;
} 

body.logged-in #nav li.logged-in-nav {
display: list-item;
}

– Then on the menu item you create for that page, simply add a css rule for it. ie, there is a box for CSS Classes, add logged-in-nav to that textbox

For this to work, you’ll need to actually have a primary list defined then edit the actual menu item to find that CSS Classes field.

Downside, the link is still available in the source code for the page, but unless someone goes looking they wont find it.

Now, if only someone could tell me how to do exactly the same for users that ARE logged in — ie, I want to hide some pages from logged in users, but there’s no “not-logged-in” or “logged-out” class for the body tag.

If someone could tell me how to create such a class to that’s added when the page is generated, I’d be stoked!!!

Someone beat me to it, I was about to report the same thing ??

I have turned on (and off), tried both ways with that option you suggest. In some ways, remote login OFF is better for the user experience, but a PITA for me. But what I did find, that although this is under SITE administration, changing it ANYWHERE affects all sites. ie, I had it on in all sits, turned it off in one, and went thru the others, and they were already turned off. They were all turned on initially.

So, back to that option under “My Sites”, what is it for? There’s little I’ve found for it. I was going to play with it for one of my lesser blogs, I still might. But don’t want it stuffing anything else.

My basic intention is to go from using dom1.com as my main admin site to using dom2.net. Because this will give the users the most streamlined effect–I want to integrate facebook (as per other topic), but I don’t want them EVER seeing the old admin domain. I’m pretty sure they won’t, but I want to be sure.

Yeah not ideal I suppose but only one site will be fully integrated. The other sites won’t be having any feeds to or fro and no obvious Facebook buttons.

My Internet has been out for the better part of a week, so hopefully it’ll be up and running in the next few days and I’ll start playing.

What my main concern was is if someone logs in with Facebook and has the same user details as someone who logs on with openid, twitter or gmail. They could potentiall have identical details with only an email address being different. How would wordpress deal with multiple users with the same name?

Ok, I just went looking–still not prepared to experiment just yet…

What I’ve just realized is that this option to change the primary domain is only available in the subdomains themselves, not in the network admin.

For each blog, the primary domain is https://dom1.com (regardless of the blog).

For the first time ever, I just opened the drop down and what I saw wasn’t what I expected. With reference to the URL’s I provided above, the drop down (for example in the case of dom2.net) is
https://dom1.com <– current setting
https://dom1.com/dom2
https://dom1.com/abc
https://dom1.com/xyz
https://dom2.net
https://dom1.com/another
https://dom1.com/onemore

I’m assuming the dom2.net appears, appears as a result of domain mapping elsewhere.

The line dom2.net is different in each blog, and the URL for each blog appears in this spot

So maybe this option doesn’t do what I was expecting. I’m not too sure now…

Sorry, I’ve misstated what it is I actually want to do.

I have domain mapping and use various domains with my blogs–in the following forms:

https://dom1.com <– primary install of wordpress
https://dom2.net
https://abc.dom2.net
https://xyz.dom2.net
https://another.com
https://one more.net

All domain names point to the one folder on my web host.

Problem is anyone logging in on dom2.net is redirected to dom1.com for that and sent back. That’s one of the problems I want to address (I know there’s another option to keep the user local, but that’s not ideal for other reasons).

There’s an option under “my sites” to select the primary domain for the wordpress install. Technically the db isn’t moving, just the pointed URL for back and front end stuff. Just to clarify, all the URL’s point to the one web server’s folder. I just want the primary domain to be dom2.net now. So these logins are within my main network of sites.

I’m pretty confident this setting iswhat I’m after and what I need to change. Just not 100% ??

I hope I’m more clear in my intentions now. The setting I’m talking about is the primary domain and so my question is, are there any tricks, tips, problems with changing this ‘willy nilly’

Yep, that fixed it for me: deactivate in the network plugins and reactivate it in the individual site. Hopefully this can be fixed in the next version ??

I see the error in my thinking, I don’t know what I was thinking.

Something along the lines of having multiple domains mapped to the one SUB-blog (not multiple domains to different blogs), if a request comes in on one of the domains that’s not the primary domain (for that sub-blog), it will get remapped to the primary domain.

Basically, what you’ve said in the paragraph about Donncha’s plugin, which incidentally is the one I’m using ??

As cynic said, the domain mapping tool is what you need, it’s here: https://www.ads-software.com/extend/plugins/wordpress-mu-domain-mapping/

They obviously need to have the domain name first. Go to their DNS and create entries that point the domain to your web hosting server ip address.

Next, go to your web host cpanel or equiv, and you need to map the incoming domain name to a folder in your hosting server. This will be the folder you have the WPMS installed.

Final step, once you’ve got the above plugin installed, go and add the mapping for the new domain name and mark it as primary, this way when wordpress receives a request from that domain name (and wordpress receives it because it’s mapped at your host server to the wordpress directory), the wordpress domain mapping plugin will ensure the user coming from the outside sees the correct domain name.

There is an added benefit, that the existing https://sitename.mainsite.com will still work, but if you marked the mapped directory as Primary (above) then when someone comes into it from that address, it will be remapped to the new https://sitename.com

I have a setup exactly as described. I have a placeholder root account
https://main.com

I have no subdomains off it, instead I have three other domains which all point to it:
https://domain1.com
https://domain2.net
https://anotherdomain.com

I even have two further subdomains off one of the above:
https://sub1.domain1.com
https://sub2.domain1.com

Each of the six blogs above are hosted in one wordpress install and all appear as totally separate blogs.

That plugin is great for global registrations where you want new users added to multiple sites at the same time, but what about just for the site they registered thru?

I believe, this was an option when multisite was a separate entity to wordpress. Correct me if I’m wrong, but I thought there was an option to allow logins thru the root site OR the site the user was on. Did that option get removed in the merging?

@naomi, but won’t all the domains remap to the original domain? I’m using a domain mapping plugin and I have several domains pointing to the same MS install, but they always get remapped to the primary domain for that blog… I do believe there is a hack to change this behaviour but it’s not default.

Do you have another domain name you could use instead of a sub domain? ie you want to keep it visually separate from your main site, it would add to that. I’m not 100% on if multisite would work from an install in a subdomain. I really don’t see any problem, as the installs are in two physical locations on the server, and it just comes down to your mapping with your hosting company. You will just point the subdomain to the folder of the subdomain. You can’t hose your main site by testing this (as long as you don’t install over the top or in the current directory that your domain name is mapped to).

However, from your second paragraph, I can only say multisite is not for you, or at least, not for the setup style you’re after.

I have just run through a series of tests and found that when a user registers, they are not assigned to any site and although they go thru the motions, a (super) admin must go and assign the users to each domain. There is a plugin that can make setting “default” but that’s certainly not what you or I want here.

I do remember under the old wordpress model, you had a choice to have users login via the main root site, or the site they are visiting. I’ve been trying to find that setting, but it seems that maybe they can only register at root level. I wouldn’t mind knowing what the best practice is here, because if you have a successful site, it would be a pain to have to go and manually add users to sites. The test users I just created indicate in no way which site they came from…

Hopefully someone can help me out on this final point, because that’s inconvenient. I would like a user, who registers, recaptchas, activates and then logs in, to have access to the site they registered for, and not all, or a subset of sites. Might be time to break open wp-signup.php

@yarby – champion effort, that fixed the exact same problem for me ??

Let’s hope that in an update they fix that!

This is the plugin for the domain mapping:

https://www.ads-software.com/extend/plugins/wordpress-mu-domain-mapping/

Requires manual setup, but works flawlessly and as described.