Tracking beacon causing SSL warnings

  • Resolved nuttyben

    (@nuttyben)


    10 years ago

    Hi Gezim!

    We’ve switched from ZipList Recipe Plugin, and first off let me just say, thanks for carrying it forward!

    The issue we’re having is that the tracking beacon you added is always loaded from an https:// URL, even when the blog is loading from an https:// URL.

    For now I’ve manually edited your code to remove the beacon, but this will of course cause problems for upgrading. Is there any chance you’d be willing to add a config option to disable the beacon, and/or set up an SSL cert and then change it to a schemaless URL (“//www.ziprecipes.net/beacon…”)? Obviously making it configurable would be a more privacy-sensitive approach, but perhaps you have you reasons for not doing so. ??

    Thanks!

    -Ben

    https://www.ads-software.com/plugins/zip-recipes/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter nuttyben

    (@nuttyben)

    (Also, it turns out that the Zip Recipes registration form cannot be submitted if you have wp-admin running over SSL. It tries to post to a non-SSL form. I ended up manually setting zrdn_registered = 1 in my wp_options table to get past the form, but if you happen to fix this I’ll revert that option and then we’ll actually register the plugin. :))

    Hi Ben! (You so nutty, man!)

    Good finds, for sure.

    I’m really not doing anything with the beacon at all. It was there and I thought it’d be nice to see some data but … I’ll just remote it! ??

    Same goes for the registration when you’re using SSL.

    Frankly, I don’t want to buy an SSL certificate and set that up for no good reason.

    Thanks so much for the investigations!

    BTW, Ben, pull requests are more than welcome here: https://github.com/hgezim/zip-recipes ??

    Just pushed an update ??

    Thread Starter nuttyben

    (@nuttyben)

    Thanks Gezim!

    Sorry for falsely accusing you of adding the tracking beacon. I guess I was looking at the wrong repo.

    (This commit makes it look like you added the tracking beacon: https://github.com/hgezim/recipe_plugin/commit/84444aca75476ab52ede9d5bec46598e8b3348c7 … but now I’m guessing that was just due to some sort of merge or something. I found that repo by traversing the forks of the original ZL plugin.)

    Thanks for quickly addressing these issues! I’ve removed my beacon-disabling hack and updated our plugin, and everything is now working smoothly, with no SSL warnings.

    And if we encounter any further issues on our side, I’ll definitely submit them as pull requests. Thanks again for carrying this plugin forward!

    -Ben

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Tracking beacon causing SSL warnings’ is closed to new replies.