[DOMAIN MAPPING] DIVI mixed content issue admin-ajax.php

After update Domain Mapping to new version issue with mixed content in DIVI with admin-ajax.php.
https://www.monosnap.com/file/4P6C8cGVn4lH1FMl7wf5E8grFrPRab#
This issue is still not resolved.

  • Predrag Dubajic
    • Support

    Hi Ben,

    We're currently looking into some new reports about mapped domains, cross login and SSL.
    At the moment can you try editing your pages from original domain instead of mapped domain and that should work.
    So instead of editing via mappeddomain.com/?et_fb=1 go to domain.com/subsite/?et_fb=1

    Best regards,
    Predrag

  • Ben
    • The Reaper

    That was from the domain.com/subsite....as you can see in the graphic the tech attached. Please review the last response here: https://premium.wpmudev.org/forums/topic/login-form-action-remains-http-for-unmapped-domain-on-https-only-site

    lets get on the same page and get the bug re-tested and fixed, here's the response i posted over there to double ensure we are on the same page:

    1.networkblog in https
    2. add two domains to your sub-blog
    3. choose a primary domain
    4. Front end redirect should be: Disabled and entered domain should be used (VERY important setting because with other options the bug doesn't exist, I repeat this setting must be set in domain mapping for the bug to show)
    5. Find a page that is https://networkname/subblog/somepage that is requesting the url wp-admin/admin-ajax.php (ie divi visual builder)

    You will see there is a mixed content problem because admin-ajax.php is being requested via http url, when it should be using http

  • Leonidas
    • Developer

    Hello there Ben ,

    sincere apologies for the delay here, but this issue proved to be quite tricky. Since the latest release, we have noticed that most members that couldn't force admin-ajax.php to load over https, to have their issues fixed, but there were some cases where the issue persisted. So, on your end, could you install the latest beta I'm attaching and see if your issues are/remain fixed?

    Backing up your installation and updating the Domain Mapping plugin to this latest beta should fix this issue and some additional ones, so you can update Domain Mapping and you can let me know how that goes, in this very thread. I'm attaching the beta below:

    Best regards,
    Leonidas

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.