Unfortunately not :( The "Force HTTPS" is really just that: it converts all URLs to HTTPS. If it didn't it wouldn't fix the "partially encrypted" warnings. Most of these warnings come from plugins and modules which try to include Javascript from an external server (e.g. Google, Facebook, jQuery CDN, ...) but only do so using an http:// URL. The Force HTTPS feature really forces those URLs to become https://. The downside is that it converts every single external link to HTTPS as well. It can't be "fixed". It's only useful because it makes a blind search & replace and it causes you trouble because it makes a blind search & replace.
The proper solution is to identify which scripts on your page are accessed by http:// URLs and contact the developers of these plugins/modules, asking them to fix them. Then you can disable the Force HTTPS feature. It's a lot of work, but it's worth the trouble. Take it from someone who had the "partially encrypted" issue on his business site, wrote the Force HTTPS feature as a bandaid and went through the trouble of fixing all problematic extensions himself ;)
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
