I had SSL forced on admin/login and transaction pages only, and that worked well, except BB developed issues. You suggested forcing SSL on front end also, which solved the problem with BB.
But making all pages and content secure is proving to be a time-consuming, whack-a-mole project. The plugins that do this don’t work completely, and create issues of their own.
I was set to launch, hosting portfolios on multisite before this came up.Thinking I may have to remove the Beaver but really don’t want to. And lots of content built on it.
Did you set the WP and Site Addresses under Settings > General to use https? Doing so should automatically change all instances of http to https on your site. Is this not the case for you?
Also, I use the function below to force https all pages on the frontend. Just wondering if you’ve tried this method?
Thank for the response. I don’t see that option in Settting > General on Multisite. Anyway, forcing both front/back end SSL is not the problem. The Domain Mapping plugin does this.
The problem is securing all content. Otherwise, the browsers give out those Danger! warnings. And a problem develops with blog comments with https and no green padlock. ‘Get a ERROR: please type a comment’ message.
Turns out my theme had some unique code in comments.php that was causing the SSL issue. (Wasn’t a problem on other themes.) Solved it by disabling comments.Now all front end is SSL with no issues.
Sorry, this issue wasn’t well-expressed…I confused them on Beaver Builders as well!