Hey guys, I’ve read a pile of posts around this issue but cannot seem to find any resolve with it. I can’t get the builder to work at all when using WPMU Domain mapping plugin. Are there specific settings that have to be in place for this to work? Thanks!
Hey Mike,
Sorry to hear! Did you by chance check out this thread? Is that issue similar to what you are experiencing?
Best,
Billy
Well it seems a bit different. I have the mapped domain working properly on two sites, the edit page works just fine and the admin areas work just fine. The customizer works as well. The only thing that isn’t working is BB. It seems to be trying to edit at the mapped domain (http://mappeddomain.com/?fl_builder)
I think i fixed the issue. This domain mapping is finicky for sure…
Agreed! What did you end up doing to fix it? I am assuming it was some type of setting in the WPMU plugin?
Best,
Billy
It ended up being the domain mapping plugin settings and forcing https (my user error). Sorry to bother you guys! Get back to making awesomeness! 
Hahaha, no worries, and will do!
Ok might have spoken too soon. When I click page builder from the pages list it try’s to open https:// and goes to the mapped domain. I can’t figure out what is going on.
My setup is:
Admin & Login set to original domain. Cross-domain autologin set to No (I don’t want users logging into each others sites). Verify domain’s DNS settings = yes, Check domain propagation before mapping = yes, Would you like to force https in login and admin pages:yes, Would you like to force http/https in front-end pages:no.
Everything works exactly as expected except for the BB edit. When clicked it takes me to the HTTPS:// mapped site instead of the original domain. Kinda urgent on this one if you guys have the time.
Hey Mike,
Sorry for the delay, would you mind providing access to the site in question? I’ll probably have to have Justin take a look at this as I’m not hugely familiar with using WPML. Thanks!
Best,
Billy
[Content Hidden]
Hey Mike,
This is a tricky one as we’re using a core WordPress function (get_permalink) to build the edit URL. I dug into the core code for the View Page button and it looks like they are wrapping get_permalink in set_url_scheme which I’m guessing is why that link works and ours doesn’t. Would it be possible to get FTP access to test that out?
Thanks,
Justin
Ah, nevermind, it looks like we’re using set_url_scheme as well. Let me do some more digging.
Justin
Hey Mike,
I’m not 100% sure but I may have a fix I can try. Would you mind shooting FTP info over?
Thanks,
Justin
[Content Hidden]
Hey Mike,
I made some changes to how we build the edit url that fixed the https issue. However, I can’t prevent it from going to the mapped domain as that is the domain that is set for the post permalink. You can see that in action for the test page I made. The WordPress UI shows this…
The View Page button also goes to the mapped domain.
The reason that is an issue is because when you try to launch the builder, you are launching it on a domain that you are not logged in on. You should be able to fix that by turning on Cross-domain autologin as that’s actually meant to log the user into the sub domain and mapped domain, not other people’s sites.
Let me know if you have any questions about that.
Justin
Thank you Justin. So I checked the Cross-domain autologin and it wasn’t working until I deselected the Load Cross-domain autologin asynchronously option. Really appreciate the help!
Also, will you kindly remove the reference to the site above. Thanks!
Great! Glad it’s working now. Link removed.
Justin
Crap so it looks like all is working except adding images. It won’t let my upload anything.
Hi Mike,
I tested this out and it looks like there is an issue with the WordPress media uploader and your domain mapping setup. It’s really hard to say what the issue could be as the error is out of the realm of what Beaver Builder has control over. We’re not doing anything special with the media uploader other than loading it on the front-end. That implementation is handled by core.
You might try installing another plugin that uses the media uploader on the front-end to see if the issue is there as well. If it isn’t, then we can look into what they are doing and see if there is something we could be doing different. If the issue is there, then you’ll need to figure out what in your domain mapping setup is causing the issue.
Justin