Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Javascript Error in IE6 on SSL-Proxy and Google Tracking Code #569

Closed
anonymous-matomo-user opened this issue Feb 26, 2009 · 4 comments
Closed

Javascript Error in IE6 on SSL-Proxy and Google Tracking Code #569

anonymous-matomo-user opened this issue Feb 26, 2009 · 4 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.
Milestone
RobotRock

Comments

@anonymous-matomo-user
Copy link

I had a customer using IE6 today reporting javascript errors in our shop when he tries to check out.

I fired up Internet Explorer 6 and tried it myself and can reproduce the error. However, this is most likely due to Google Analytics (which currently runs side-by-side to Piwik). We have a ssl proxy for secure checkout and as the domain is different to the regular shop domain, links to the ssl area are wrapped into ‘pageTracker._link()’ in order not to loose the customer and miss the sale in the Google Analytics conversion.

The Microsoft Debugger claims an error in _pk_is_site_hostname(), the line in question is

```
if ( alias.substr(0, 2) == “*.” ) {
```

At least it is the line highlighted by the debugger. I can’t reproduce this in Firefox nor Safari, it only fails in Internet Explorer.
@robocoder
Copy link
Contributor

Should be fixed in #566. Prototype and MooTools are culprits.

@mattab
Copy link
Member

mattab commented Feb 27, 2009

msslovi0, can you please apply the patch in #566 and see if that fixes your bug?

vipsoft, I would also think this fixes the bug but because this one is critical (warning in browser) we have to make sure this is the case.

@robocoder
Copy link
Contributor

Ok, I’ll remember that when I’m triaging new tickets.

msslovi0: while we have your attention, can you also verify that your shop (eg ecombase) uses MooTools? Thanks.

@anonymous-matomo-user
Copy link
Author

The fix from #566 solves this one, too. Thanks for your fast response.

We’re running a xt:Commerce-Shop (not Ecombase, which is forked from xt:C) and are not using Mootools. However, we are currently in a transition from Prototype/Scriptaculous to jQuery, so on some pages both frameworks are used (Prototype by default und jQuery in compatibility mode). If you need URLs, let me know.

@anonymous-matomo-user anonymous-matomo-user added this to the RobotRock milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
RobotRock
Development

No branches or pull requests
3 participants
@mattab @robocoder @anonymous-matomo-user