inge12

Thanks, Ipstenu. Domain mapping with the plugin works fine for me, PROVIDING I do not have an actual subdirectory https://ssnet.org/sabbathissues/

When I had such a physical subdirectory, my previews and other redirects from the dashbord would go to https://ssnet.org/sabbathissues/ and show me an ugly directory index, rather than redirecting to the domain.

Index of /sabbathissues
Parent Directory
Apache Server at ssnet.org Port 80

In order to have the site mapping function properly, I had to delete the physical subdirectory.

In the meantime, I solved the issue of registering for the site, etc by disabling being logged in to all sites at once — or something like that.

I’ve concluded I had better stick to precise WP instructions, without deviation, because that’s the only way it works properly.

Ipstenu, thank you for the response.

I don’t want to move multisite itself, just a subsite.

I was just thinking that installing the subsite in a subdirectory and using an addon domain would have suited me better.

I don’t quite follow you, though. WP is in https://ssnet.org/.
But I could not map a domain or use an addon domain through CPanel for https://ssnet.org/sabbathissues/ and have WP recognize it.

Or maybe I could? Maybe I should not have mapped the domain through WP as well? Does mapping a domain through CPanel interfere with domain mapping through WP?

After undoing everything in CPanel, the domain works, but there is no real subfolder https://ssnet.org/sabbathissues/
It appears to be only a virtual subfolder. Is that correct?

Just trying to understand.

If the subsite were in a physical sub-folder, I figure it would be simpler to provide ftp access to the owner of the subsite.

I also thought I needed a physical sub-folder to use that domain for email, but it seems that is not necessary. I can use it for email even as currently installed.

Okay, the Cpanel Redirect was the problem.

I had parked the domain on the root in Cpanel, as instructed by domain mapping in WordPress. I also redirected the domain to
https://ssnet.org/sabbathissues/
This was a mistake.

Removing the redirection fixed this problem, but it didn’t fix all problems. Then, when I creates a new post, the “Preview” went to the sub-directory index. Deleting the sub-directory off the server solved that problem.

After searching a bit more in the forum, I concluded that I would have preferred to install the subsite in the real folder https://ssnet.org/sabbathissues/. Then I could have mapped an Addon domain to that folder. But that option is not listed in the usual instructions for installing a subsite. I’m guessing that the upload folder would then have been in https://ssnet.org/sabbathissues/

Is that correct?

I’d like to know for future reference. (Also – would it be possible to move this install, without losing everything?)

I had typed in the correct redirect URL, but must have forgotten to save it.

It works correctly now

FS-Contact has a redirect function. I filled in https://sabbathissues.org, but it still redirected to https://ssnet.org/sabbathissues/ and an ugly Apache Index.

Help!

In the Meta section of my domain https://sabbathissues.org/ there is a link to “Register.”

This link take the user to the main site https://ssnet.org/

Do you mean to say it’s not possible for users to register directly at https://sabbathissues.org ?

It is sitting in a sub-folder: https://ssnet.org/sabbathissues/

The problem is that the registrations don’t appear to show up at all on https://sabbathissues.org/ and I have no way of knowing who is trying to register for the site unless I activate email notifcations.

Having to manually deal with hundreds of registrations is not my idea of fun. ??

The most practical alternative, in that case, would be for me to disable public registrations, allow non-registered commenting, and manually register contributors.

Or am I missing something? I mean, there’s got to be a better way in this age of automation. (I thought I had made a mistake in setting up the subsite and was hoping to be able to rectify the problem. I do seem to remember the choice between being able to log in to all sites at once or to individual sites. Can’t find anything like that in the settings now.)

I just tested “inviting” an email address to https://SabbathIssue.org. Responding to the invitation, I clicked on the link and got an error message:
An error occurred adding you to this site. Back to the homepage.
Clicking on “homepage” yielded a perfectly ugly page —
Index of /sabbathissues
Parent Directory
Apache Server at ssnet.org Port 80

Of course, the “parent directory” is the blog at https://ssnet.org/

I must have done something wrong. I think I “pointed” the domain in Cpanel as well as in the multisite setup. Could that be a problem?

Thank you very much, Parick! That was extremely helpful.

Thanks much, Patrick ??

Your instructions on adding a domain are good for me, because I’m on Hostgator.

Just a question: You seem to presuppose a sub-domain. Will the instructions work for a sub-directory as well? Or is it better to use sub-domains?

The issue is still the same as at the beginning of this thread, as far as I can tell:

Individual sites do not have the ability to install plugins.

Plugins installed on the network interface do not show up in the individual Dashboards unless network activated.

What I`ve found is this:
Some plugins will show up in individual sites after network activation and will give site owners the option to activate for that site.

Other plugins will not show up on individual sites as plugins, but the options will show up under Tools or Settings — no telling which. ??

Some plugins will not show up at all on individual sites because they have no options that can be set on individual sites. These are in the minority.

I`ve not yet found a plugin in the repository that is current and will not work after network activation.

PS I use a lot of plugins. ??

I found the problem. It was indeed the upgrade attempt of Weaver Pro II. The attempt to use Easy-Theme upgrade wiped out the version of Weaver Pro that was active, and the site defaulted to 2011 (supposedly), and that theme wasn’t even installed.

When I reactivated an older Weaver theme, everything was/is fine.

Okay, thanks, Ipstenu ??

That’s enough detail for me, I think. ??

I need instructions re “how to make a new db.” Just creating it won’t make the tables, I’m thinking. I tried the “make new table” option, and there were all sorts of options I didn’t know what to do with. (Sorry!)

Previously I did follow all the instructions in the Codex. The only thing extra I did was install sunrise.php.

After Ipstenu’s comment I’m wondering what difference that file actually makes.

Never mind.

The “Network Admin” option magically reappeared after I logged out, then in again.

Whew!

To answer Andrea:
No, actually the sub-domain install does not work. It only showed up in the Network panel as though it did.
So I deleted the empty sub-site and actually created a sub-domain in Cpanel. Cpanel told me the subdomain would be https://inga.4goodhealth.com and the document root would be home/public_html/inga (and that’s the same level as the wp folders).

I re-installed the sub-site. But the sub-domain install stil won’t work. What could be the matter?

H’mm … I installed the WP in the main directory of the site.

You mean picking subfolders for “sub-sites”?

The installation process told me that I could not use sub-folders because this was not a “new install” (I had already imported content from another blog) but had to use sub-domains, which was fine with me.

Does that make a difference? Does it change default behavior?

Is it possible to change this setting after an install?

For instance, can I change an install to put sub-sites into sub-domains, rather than sub-folders? (I like the idea of shorter URLs for the main blog. Would be a bit of work, with 40 posts, 183 comments and 14 pages so far. Any (relatively) easy way to do it?

(I assume WP creates the sub-domains [probably virtual] automatically?)