Support » Plugin: WordPress HTTPS (SSL) » [Plugin: WordPress HTTPS (SSL)] installation in the mu folder

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Mike Ems


    No, not currently. What kind of settings or tools would you like to see?

    I want to be able to run a secure network. I have created a multisite install for my senior seminar class, and it must be password protected and run over ssl for security. I am using a combination of plugins, including Better WordPress Security, and everything is running smoothly except that my home page and the home pages of all the sites on the network are loading insecure content. Clicking the setting on WordPress HTTPS solves the problem, but I will need to go into all the sites and set them up individually. I can do this, but it would be better, I think, in some cases if the admin can control the settings for the whole network. I need a way to force all page elements to go to SSL for all the sites cleanly and efficiently.

    Thanks for responding so quickly.

    Though I haven’t tested it, most likely if you drop this plugin into the mu-plugins folder you will still have to configure the settings on each site. It takes a bunch of extra coding to get both master network wide controls and granular controls for individual sites.

    At that point you might as well put it in the main plugins folder and network activate it.

    The mu folder only allows for one php file to be loaded. It will not allow plugins contained in folders such as WordPress HTTPS. I tried combining files from the plugin and dropping them into the folder, as well as dropping some of the individual files in, but to no avail.

    If you want to put a regular plugin into the mu-plugins folder you have to pull the main php file for the plugin outside the plugin’s folder and then edit php file to change the paths to any file references so they include the plugin’s folder.

    Not sure if I explained that in a way that makes sense or not. But that’s one of the big reasons they implemented the “Network Activate” option for regular plugins on Multisite. It’s less complicated for most folks to just do it that way.

    Besides, once you start modifying plugins you have to keep re-modifying them every time the plugin developer releases a new version. Mostly it isn’t worth the extra hassle.

    Plugin Author Mike Ems


    What do you mean by “Clicking the setting on WordPress HTTPS” what setting is making all of your sites work correctly?

    “Secure Front Page” setting makes the sites work correctly. Otherwise they display an error for loading insecure content. It’s not a huge deal, but I feel like some students will struggle with the error. I would like to make it as smooth as possible.

    Plugin Author Mike Ems


    Hmm, that doesn’t make any sense. In my development version, I ensured that when you Network Activate, the plugin is properly activated for each subsite. I think the issue is that the plugin just isn’t installing for each site.

    Secure Front Page should not make insecure content errors go away, but rather I think saving the settings is making it work.

    If you do want to use the Secure Front Page option for each subsite, you’ll still have to go enable that option for each site.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘[Plugin: WordPress HTTPS (SSL)] installation in the mu folder’ is closed to new replies.