mvied

You can’t do cross domain AJAX calls. You can’t even do HTTP AJAX calls on HTTPS pages without some tweaking.

No. If a server is not hosting content over HTTPS, there’s nothing you can do except remove that from your site, or host it locally.

Unfortunately, you can’t. Your only option is to secure your entire admin panel.

It’s a big pain to get that to work correctly because domains can’t set cookies for other domains, so you would have to toss the session around to get that to work right. I’m too worried about the security issues that might create, but one day I plan on implementing it.

You can add booking.cv.com or more specifically booking.cv.com/xxx/js/remote.js as a URL Filter.

No, I’m pretty careful with those. The empty URL being passed into this method could literally come from anywhere. It could just be bad HTML. I’ll just have to suppress PHP warnings on that line since it can happen.

Domain Mapping doesn’t work from HTTPS to HTTP, but that is purely an oversight on my part. I’ll get it fixed in the next version.

In the meantime, you’re more the welcome to try this hack using a filter I provide.

function wphttps_fix_cdn($url) {
	return str_replace('ssl.cf2.rackcdn.com', 'r22.cf2.rackcdn.com', $url);
}
add_filter('http_external_url', 'wphttps_fix_cdn');

Nope, not a clue. The error doesn’t occur in the plugin. Perhaps you’re running out of RAM? Try increasing PHP’s memory limit. Usually if that’s the case it will say that, but I’ve seen it do things like this before.

The plugin isn’t necessary unless you’re having issues or you’re trying to do something with SSL that WordPress will not allow you to do. If you’re just securing your entire site, your admin panel (or both) and you’re not using any old, crappy plugins, this plugin is probably not necessary.

The first and only feature the plugin had initially was ensuring that all elements on the page loaded securely. If you have any element on the page that loads over HTTP, your certificate will appear invalid. Due to old/bad plugins, this can be an issue. This plugin will fix all of those that it can.

It allows you to use any domain for your HTTPS content, which WordPress certainly can not do. It also allows for an easy way to specify what content you want to be secure and what content you don’t want to be secure. Again, if you’re securing everything, this doesn’t matter.

I’m guessing you have quite a few multisites? I need to optimize the installation for sites that have a lot of sites. The plugin is running the install process for each site and that (apparently) eats up a lot of RAM. I’ll see what I can do about it in the release I’m going to push out later today to fix other issues with 3.3.5.