• Hi there,
    I’m running the free version of Revive Old Posts. I’ve got it hooked up to my bit.ly account so that shortlinks are automatically created whenever ROP generates a tweet.

    Although my site is https://, I’ve noticed that that the ROP link sent to bit.ly is https://.

    The result is weird security warnings when people click through the links.

    Is there a setting I’m missing?

    Thank you!!
    Carrie

    https://www.ads-software.com/plugins/tweet-old-post/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey Carrie,

    Are you getting the sharing link from a custom field ? If not, what we are sending to bit.ly is : get_permalink( $postQuery->ID ), which should rely on your WordPress settings.

    Thread Starter Carrie Dils

    (@cdils)

    Hey Ionut! I didn’t know I’d get the man himself on the forums. ??

    My site settings are https://. It may be something going on in my bit.ly account then.

    Thanks for the info!

    Plugin Contributor Hardeep Asrani

    (@hardeepasrani)

    Let us know if you were able to fix this. ??

    Thread Starter Carrie Dils

    (@cdils)

    Thanks for following up, Hardeep.

    I disconnected bit.ly and confirmed that your plugin is sending the URL correctly (https:// in my case). Twitter’s link shortening service has picked up where bit.ly left off and still wants to add that https:// protocol to links. Not sure why, but it’s not an issue coming from Revive Old Post.

    Cheers,
    Carrie

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Changing HTTP to HTTPS with bit.ly’ is closed to new replies.