• Resolved InHouse

    (@inhouse)


    Hello, thanks for the awesome plugin!

    I’m getting multiple mixed content warnings on admin pages and I believe it’s due to the use of WordPress MU Domain Mapping to map the subdomain to another domain. Some images and scripts are being loaded (blocked) from http://sub.originaldomain.com while the page is https://sub.differentdomain.com. Is there a way for Really Simple SSL to force https for external URLs to fix this scenario? Thanks in advance for any help!

    Debugging
    Options:
    * WordPress redirect
    * Mixed content fixer
    SERVER: apache
    MULTISITE
    SSL is activated network wide
    SSL is enabled for this site
    ** Detecting configuration **
    plugin version: 3.1.5
    Already on SSL, start detecting configuration
    SSL type: SERVER-HTTPS-ON
    ** Configuring SSL **
    testing htaccess rules…
    test page url, enter in browser to check manually: https://campaign.useinhouse.com/wp-content/plugins/really-simple-ssl/testssl/serverhttpson/ssl-test-page.html
    htaccess rules tested successfully.
    checking if .htaccess can or should be edited…
    .htaccess does not contain default Really Simple SSL redirect
    retrieving redirect rules
    converting siteurl and homeurl to https

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Mark

    (@markwolters)

    Hi,

    the Really Simple SSL mixed content fixer is only active on the front-end of a site, therefore the free version of Really Simple SSL cannot fix mixed content in the backend automatically.

    Mark

    Thread Starter InHouse

    (@inhouse)

    Thanks for the clarification. Does the pro version support this? I’d consider buying if the pro version would definitely fix this scenario.

    Plugin Author Mark

    (@markwolters)

    We are not allowed to discuss the pro plugin on the wordpress.org forums, you can send us a message at [email protected] with any questions about the pro plugin.

    Thread Starter InHouse

    (@inhouse)

    Sent! Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Mixed Content Issue Using WordPress MU Domain Mapping’ is closed to new replies.