WordPress.org

Support

Support » Plugins and Hacks » Google Maps Widget » [Resolved] protocol mismatch errors

[Resolved] protocol mismatch errors

  • My web browser source inspector shows many errors, saying, “Blocked a frame with origin “https://maps.google.com” from accessing a frame with origin “http://mysite.com”. The frame requesting access has a protocol of “https”, the frame being accessed has a protocol of “http”. Protocols must match.

    http://wordpress.org/plugins/google-maps-widget/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author WebFactory

    @webfactory

    Well that doesn’t help me at all. I realise that you are not “are not obligated [sic] to do anything” but either you’ve come up against this problem before, or you don’t recognise it.

    Plugin Author WebFactory

    @webfactory

    Unfortunately we do not have a crystal ball. What version of WP are you using? What version of the plugin? Is your site on HTTPS? What browser debugger displays the errors? List goes on.

    Yes we’ve seen that error a number of times, as with any other error users post here. But problems that borderline “it’s not working” are not something we can fix. So unless you can provide the URL of your site I guess we’ll leave this one on “we’re not obligated to do anything”.

    Plugin Author WebFactory

    @webfactory

    Closed due to inactivity.

    3.8
    1.30
    No
    Safari debugger

    So if you’ve seen the error a number of times – what kind of things cause it?

    Or do you need my inside leg measurement first?

    Plugin Author WebFactory

    @webfactory

    Those errors come and go as Google makes changes to their cross-origin-requests domain rules. It affects YouTube, Google Maps and any other iframe based embedded code (API based calls are not affected, but our plugin uses iframes for the bigger maps). There’s no real solution for the problem but since it’s only manifested through the debugger …. I’ll be so bold to call it a “problem”.
    Once we switch to API for the larger map we won’t be seeing any cross-domain or protocol mismatch issues.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Resolved] protocol mismatch errors’ is closed to new replies.
Skip to toolbar