I saw this in my error log.

msyite.com/home|1||getCurrentPosition() returned error 1: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).. Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

this is a Chrome web browser issue, but I wanted to bring it to your attention in case anyone else runs into this.
I don't think there is much the module maintainer can do.

Comments

SocialNicheGuru created an issue. See original summary.

RdeBoer’s picture

RdeBoer
Location Melbourne
CreditAttribution: RdeBoer at flink commented

Hi SocialNicheGuru,
I agree it's a bummer in Chrome.
And I agree there's nothing I can do about it....
Rik

kenwest’s picture

kenwest CreditAttribution: kenwest as a volunteer commented

Am I correct in assuming this issue would not appear on pages served up via https?

RdeBoer’s picture

RdeBoer
Location Melbourne
CreditAttribution: RdeBoer at flink commented

Yep. HTTPS will not have the issue. And neither does localhost.
Rik

RdeBoer’s picture

RdeBoer
Location Melbourne
CreditAttribution: RdeBoer at flink commented
Title: getCurrentPosition() returned error 1: Only secure origins are allowed » getCurrentPosition() returned error 1: Only secure origins are allowed (Chrome)
RdeBoer’s picture

RdeBoer
Location Melbourne
CreditAttribution: RdeBoer at flink commented
Status: Active » Closed (works as designed)

Not a module issue, but a HTTPS vs HTTP issue.

SocialNicheGuru’s picture

SocialNicheGuru CreditAttribution: SocialNicheGuru commented
Related issues: +#2692061: The "Locating you" message hangs [cause: must use HTTPS]