jhnpldng

This, https://premium.wpmudev.org/blog/how-to-install-wordpress-and-multisite-locally-on-macos-x-with-mamp/
BUT, wordpress subdomain requires domain names, not 127.0.0.1 or localhost. http”//localhost.com is ok because it has the .com but that needs to be set up and yes, it will require typing a couple of commands on the terminal. It’s not that hard but you will need the original password from when your computer was first set up.
su or sudo = super user aka root. Kind of like super-admin on wp multisite it means you can do anything. So here’s a couple more. All mac btw.
https://blog.teamtreehouse.com/introduction-to-the-mac-os-x-command-line
https://decoding.wordpress.com/2009/04/06/how-to-edit-the-hosts-file-in-mac-os-x-leopard/

It can be done and it could be done this afternoon. Just takes a little patience. You have to set up your local install with a domain name before turning on multisite. It could and probably should be done before even installing wordpress.

There’s a lot of plugins that just don’t do multisite very well and I’ve found that some like to be network activated while others need to be activated individually on each site. I must have at least 100 hours into trying plugins, deactivating all when something suddenly slows the site to a crawl or I get some kind of error. I keep a list now of what’s network activated, what activated on the main site only and what’s activated only on the subs and what’s individually activated on main and subs. If you search for “plugin auditor”, there’s a couple of plugins (because you need two more) that show you what’s activated where.
I’m running with subfolders rather than subdomains and things are going ok. I didn’t really have a choice on that as I have ssl but not a wildcard ssl which would cover subdomains. The only other type of multisite I know of is a networks of networks with lots of domain mapping but it’s not needed for just a few zones of a site.
How many plugins do you have? I’ve got 41 I active and things are still ticking along pretty good. Took me a while to gather that working collection. My subsites only show 3 active as that’s all that were activated individually one them. I’ve got 18 active on my main site and 19 network activated. Then 15 more inactive that I’m wanting to try out. One at a time, carefully with lots of inspection to make sure everything’s ok. Page speed tests etc. I don’t have buddypress but do have bbpress. Take a look at Ultimate Member as a possible replacement for buddypress.
I would keep trying with what you’ve got before rearranging install type. Changing multisite after it’s set up a certain way tends to lead to a whole new set of problems. I can post my list of plugins if you want. I’m using a note-keeping program to keep track of everything website related.
Yeah, that common suggestion, “try deactivating all your plugins and see if that fixes it” has a whole new meaning with multisite.

Here’s a shot of what it looks like with those two items above taken care of. https://www.ozarkswebdesign.com/images/resp.png
Ctrl+Shift+m in firefox will give you mobile views. Chrome has it too and from what I’ve read it’s more properly rendered. Both browsers also have web inspector. Might have to get the addon for chrome. In firefox, it’s under Tools>Web Developer>Inspector. This opens up a panel either on the bottom or side of the browser and shows the source code for the styles. You might have to click on styles on that panel. A smaller panel within that panel has all your css and you can actually change it as viewed. It doesn’t change it permanently and a page refresh resets it but it’s good for nailing down what’s causing things to not look right or to just try things to see what they would look like. The above two tools are how I got that screenshot.

In here, talkingtree.org/media/suffusion/custom-styles.css you have some widths specified in pixels and the one that’s giving you the most problem is

#wrapper {
    min-width: 1000px;

The wrapper is the outer most container that wraps everything including pics and the css rule above is forcing the whole page to never be under 1000px wide. Comment that out by doing this;

#wrapper {
  /*  min-width: 1000px; */

Being that it’s called custom-styles, I’m guessing it’s settings in the theme options page in admin. I’m thinking it’s something someone has added and not something that comes from suffusion theme.

Here’s more css that affects things.

#main-col {
    width: 725px;
}

#wrapper {
    width: 1000px;
    max-width: 1000px;
    min-width: 1000px;
}

I would comment out the min-width first and change main-col width to a percentage, 75-85%. You’ll have to play with it a little. Those two things will fix it.

It’s possible but prob not. Have you tried any of the site speed tests to see what they have to say? Deactivating plugins, swapping themes etc. You can deactivate plugins and then reactivate and they return to how they were. You can swap themes and swap back and all your original settings will come back.

ok, Thank You

Patience. Give more than a day for someone to respond before clicking resolved.
My mistake, I thought this plugin was WP User frontend. Maybe you could make those as links on the description page. But I looked at that plugin and it doesn’t look too good to me. I’m running a multisite with paying customers so I can’t have something that might be buggy. They are good ideas so keep working on them. Best of luck.
Ok, now resolved. ??

I’m running https with no “force https” plugins. Once you have a set of plugins and a theme chosen and get those cleaned up you don’t really need anything to force https. The only issues are when a theme or plugin calls external assets. eg. I had a plugin that pulled a placeholder image from https://placehol.it That was giving me the mixed content issue and taking away my padlock. Once you have an ssl set up on your host/server, you set up .htaccess to redirect anything http to https. To help find any non secure items,,,https://www.whynopadlock.com/
There’s also a couple of plugins that will help with “non secure” items but as long as no file has https:// in it’s contents and all files are on your ssl server, everything’s secure. You can even use google fonts and have the padlock as those come from an https:// address but the preference would be all files originating from your server.
WP already has some built in switches that you can use and simply making sure everything says https in all wp settings does most of it. You may have to check the database for https:// entries. I had a couple in wp_site_options table.
wp-config can have some definitions added. https://codex.www.ads-software.com/Administration_Over_SSL That one will force ssl for login and admin pages. I’m using it but it’s redundant since my whole site is https/ssl but redundancy never hurts when it comes to security.

Search the wp site for “force ssl” and you’ll find more info.

Next you’ll need some way to lock the site(s) down from non logged in surfers. admin pages aren’t really a problem as they only show to logged in users anyway. A membership plugin would work but most of them are a mess and also tend to be social based with profiles, wall, like buttons etc. The two I was down to until yesterday were Paid Memberships Pro and Ultimate Members. Somewhere recently I saw a switch to “make site private” but I’m not sure where. It was either in one of those two plugins or wp itself. UM is loaded with switches for logged in users only; from the menu items to the posts and pages so it might be that one.
Paid Memb. Pro has one feature that’s pretty slick for multisite. It can create a site upon user registration. However, it’s a blank site with no settings carried over from another so then you get into setting defaults for all new blogs. I’m using it with one of the multisite clone plugins that has a setting for which subsite to use as the default for all new blogs no matter how they’re created. I had to modify a pmpro file so that it wouldn’t come back with a page telling the new site owner they were reclaiming their old blog and not giving them any links. Something about the cloning made it think they were reclaiming a site. The modified file was actually the addon plugin for pmpro to create sites and didn’t come through wp.org so I don’t have to worry about it getting overwritten by an update.
At long last, I have it so someone fills out registration form including CC info, clicks submit, pymnt is processed/site created and when the page refreshes, they have a link to manage their new site and are already logged into it. And, this site is cloned from an unpublished master copy and has all plugins, themes, settings and content from it.
I’m not sure what you will have to do for credentials. I don’t know if you’ll be dealing with existing customers or new signups.
You’re basically trying to use a CMS as a CRM but I understand. I looked into CRMs quite a bit at one time. 20 bucks per person per month. Dollibar was the only thing I found that was truly open source and free.
You’ve probably seen it but every site can have an upload quota and max file size set so You’ll have to set those.
I think Comodo is about the cheapest CA out there. Make sure you get SHA-2 and not SHA-1 as SHA-1 is about to become obsolete.

Got it taken care of

Just ran across another for posts.
Network Latest Posts

Update. That front end 404 only happened once but I still had isssues so I did a fresh install of wp multisite with no plugins except for Paid Membership Pro. Went through checkout and it creates a site just fine. Installed and activated Multisite Cloner, set a subsite as default for cloning and went through checkout again and PmPro gave the white screen of death. It DOES create a site and user for it but can’t seem to retrieve the site/user info and display it on the page like it normally would. I could pay them $100 for support but they would probably tell me it’s not their problem. So if you can do something for me, that would be great. I could get around a lot of this with mu-plugins and if I was a php programmer, a functions.php file but I’m not a programmer.

Regards, John

It works on a fresh install of multisite so it was not a pmpro problem.

The settings for that are under ……com/wp-admin/network/settings.php
Choices should be:

• Registration is disabled.
• User accounts may be registered.
• Logged in users may register new sites.
• Both sites and user accounts can be registered.

I’m running multisite with that exact same htaccess snippet with no problem.

Neat idea. I was going to make multiple child themes for each theme but this is slick.