Hi,
I’m having exactly the same issues as Yas1212 described. Pages loaded via https:// are presenting errors with unsecure elements that are loading as http://, such as fonts.googleapis.com and custom logo uploaded through the Theme’s Admin Panel. Changing the paths from http:// to // seems to be the alternative fix, if only I knew in which files these infos are being called…
Well, just adding voice to the chorus… I’ll be waiting for an answer to Yas’s problem.
Thanks, and sorry for my bad english (it is not my native language)!