Support » Plugins and Hacks » WordPress MU Domain Mapping » Primary domain and WordPress HTTPS Plugin

Primary domain and WordPress HTTPS Plugin

  • I have a client who has 8 blogs on our WordPress multisite network (I also have about 380 other sites on the same installation). This particular client requires SSL in the admin dashboard, so I use the WordPress HTTPS plugin to accomodate them.

    domain.com has a wildcard SSL certificate to work with https://*.domain.com

    Is there any way around this? I see a “Domain Mapping” option in the WordPress HTTPS plugin, but before I try to remove the sites from WordPress MU Domain Mapping, I’d rather have the knowledge base all down on the subject in order to not cause a service disruption.


Viewing 8 replies - 1 through 8 (of 8 total)
  • This is a question concerning WordPress HTTPS and the Domain Mapping section there is not what you think it is. It does not provide domain mapping for the site. It is for outside resources only.

    Plugin Author Ron Rennick


    If you are going to use SSL in the admin for only the main site domain then you need to set domain mapping settings to run the admin into the original domain.

    Hi Ron –

    Thanks for your reply!

    I am not using SSL for the primary domain – only for the sub-domain (non-primary) backend part of the site.

    Any other ideas?

    Plugin Author Ron Rennick


    …only the main site domain…

    that includes the sub sites.

    Unless you are using SSL for both the main site (including unmapped sub sites) & the mapped domains then the way to do it is run SSL on the main site and have the mapped domains admin panel run under the original url.

    The alternative is to hire a developer to write some custom code for you that selectively enables SSL for you based on settings that the custom code manages.

    Here’s a clarification of my setup and the reasons:

    http://www.site1.com => URL the world sees when they go to the site

    site1.company.com => company.com has a wildcard SSL certificate attached to it because the client has many sites, so the wildcard cert is the most cost efficient way to give them SSL access across all their site backends at site2.company.com and site3.company.com

    Most of the client’s sites use sitename.company.com, but three of them are different (site4.com, site5.com, site6.com)

    So you’re saying I will need to modify the code to make this work? My thoughts are to possibly put a wrapper around the whole domain mapping plugin…

    if($SERVER[‘HTTP_HOST’] == ‘company.com’)
    … bypass the domain mapping plugin somehow based on the URI
    … run the domain mapping code as intended …

    Plugin Author Ron Rennick


    You’ll need to write a custom sunrise.php to selectively enable SSL.


    thanks for your thoughtful reply. I’m the developer who will be looking into the custom code to handle this issue. Would the code you envision to handle this selective enablement be something along the lines of case switches for each of the domains? Any offhand guidance is appreciated since changes to this file seems to be in the category of a core change to my thinking.

    Plugin Author Ron Rennick


    sunrise.php is part of the domain mapping plugin & you cannot have multiple sunrise.php files. So, if you need to do something custom then the only choice you have is editing it.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Primary domain and WordPress HTTPS Plugin’ is closed to new replies.
Skip to toolbar