Greetings. I am developing my site and things are going well except that I appear to have an infinite loop in the proddetail page. Oddly, it doesn't happen all the time -- even with the same product. I can refresh one time and it doesn't happen, then refresh again and it does. All the necessary processing appears to work, so the only sign that something is wrong is that the processing indicator keeps spinning.

My only clue is in the developer's console where I see the message below hundreds or thousands of times (depending on how long it is before I notice the loop). Anyone have any ideas? Thanks.

CONSOLE MESSAGE IS AS FOLLOWS:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('<URL>') does not match the recipient window's origin ('<URL>').
cb=gapi.loaded_0:164 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://accounts.google.com') does not match the recipient window's origin ('http://localhost').
cb=gapi.loaded_0:164 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://accounts.google.com') does not match the recipient window's origin ('http://localhost').
(anonymous) @ cb=gapi.loaded_0:164
setTimeout (async)
call @ cb=gapi.loaded_0:164
call @ cb=gapi.loaded_0:176
(anonymous) @ cb=gapi.loaded_1:288
_.Xw @ cb=gapi.loaded_1:308
dx @ cb=gapi.loaded_1:288
callback @ platform.js:61
sb @ platform.js:19
L @ platform.js:17
Rd @ platform.js:61
Z.S @ platform.js:60
setTimeout (async)
Z.S @ platform.js:60
Z.U @ platform.js:60
Hb @ platform.js:60
qd @ platform.js:48
md @ platform.js:47
Ga @ platform.js:54
Ia @ platform.js:9
(anonymous) @ platform.js:55
pb @ platform.js:16
L @ platform.js:16
(anonymous) @ platform.js:19
qb @ platform.js:19
B.load @ platform.js:19
(anonymous) @ platform.js:63

Rick Haylon

Hi Rick

Sometimes the best way to troubleshoot something like this is to start removing javacsript calls and non store code from the page until you find the culprit.

Andy

Please feel free to review / rate our software

I appreciate that. Harder to do because it doesn't happen all the time. I was hoping to have an idea where the "postMessage" was being executed so I could narrow down where to look.

Rick Haylon

Rick, your issue is similar to that identified in this StackOverflow post >>

Basically, your Google Account is on secure https://
Your webpage is unsecured http://

This error is only flagged in the Google Chrome console.

For me, those technical errors disappeared after moving the entire website to load over SSL secured https://
which is best practice anyway these days.

Otherwise, in your .htacess file, you can add the entry Header set Access-Control-Allow-Origin "*"
which I did not want to do.

Gary