Hi,

Thanks for the module. Woopra looks very cool.

Unfortunately, they don't have support for HTTPS connections yet:

http://www.woopra.com/forums/topic/https-support

This causes 2 problems:

1) Users will get an annoying "This page contains secure and unsecure..." notice on every HTTPS page.
2) No HTTPS analytics will be captured. This is a bit of a deal breaker for ecommerce sites...

Nothing you can do to fix that, I don't think, but you might want to add a note to the documentation to save other folks some time troubleshooting this issue.

Best,
Chad

Comments

btopro’s picture

btopro commented

https is now supported, if you want it to work you need to update your code and also change the woopra_js variable to point to 'https://sec1.woopra.com/js/woopra.js' instead of the static.woopra.com link

ferrangil’s picture

ferrangil commented

Should we change this into the woopra module file?

If we always point to the https... .js file, will we get any warning when browsing http://www.example.com/onepage ??
I think the warnings are only when browsing over https and having elements on http, right?
Thanks

btopro’s picture

btopro commented

I know there's a way to look at where the address is sitting currently and point to https or http accordingly. Definitely shouldnt always point to https. This module needs to be overhauled (imho) simply because the woopra API has changed quite a bit since this first came out. For example, you don't need the registry keys and things in the address that's connecting to woopra; their architecture just looks at what server sent data and blocks / accepts based on that.

tomdeb’s picture

tomdeb commented

https has been added to cvs. will soon create a new release.

tomdeb’s picture

tomdeb commented
Status: Active » Fixed
tomdeb’s picture

tomdeb commented
Status: Fixed » Closed (fixed)