Support » Plugin: Slimstat Analytics » Not compatible with HTTPS!

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

    (@coolmann)

    Hi there,

    Your love for exclamation marks is just flattering 🙂 Jokes aside, WP SlimStat should generate urls according to your wordpress settings. I will run some tests on my dev environment and see if there’s anything that needs to be tweaked on either my or your end.

    Ps: a vote for my plugin would be a nice way to say thank you!!

    Thanks for the quick reply! (Oops, another exclamation mark)

    The error message from the console in Chrome is:

    The page at [URL] displayed insecure content from [URL]/wp-content/plugins/wp-slimstat/wp-slimstat-js.php.

    XMLHttpRequest cannot load [URL]/wp-content/plugins/wp-slimstat/wp-slimstat-js.php. Origin [URL] is not allowed by Access-Control-Allow-Origin.

    Any thoughts?
    Thanks again.

    Plugin Author Jason Crouse

    (@coolmann)

    Would it be possible to know the URL where this is happening?

    Thanks

    I think I should keep that to myself for my client’s privacy, sorry. I just reactivated SlimStat for a second to generate that error, then deactivated it again so the secured pages would display without insecure content.

    Plugin Author Jason Crouse

    (@coolmann)

    I understand. The thing is that I was not able to reproduce the issue on my local server: the path to the tracking script is correctly pointing to the HTTPS resource, so there must be something in your configuration preventing the script from working. Can you check in your source code if the path to your wp-slimstat-js.php has HTTPS?

    WP SlimStat is using home_url to generate that URL:

    http://codex.wordpress.org/Function_Reference/home_url

    According to the codex, the appropriate protocol will be used, that’s why I’m confused. Maybe it’s a conflict with some other plugin?

    If you want, you can contact me in private to give me more info:

    la buca delle lettere

    Thanks

    Plugin Author Jason Crouse

    (@coolmann)

    Marking as resolved.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Not compatible with HTTPS!’ is closed to new replies.