• Resolved faquick

    (@faquick)


    Hi,

    I saw that the plugin has been taken over by clint.s and looking at the diffs it looks like he did a big job on it.

    First of all I would like to thank you, clint.s, for your work!

    Then, before updating, I would like to know if somebody already tested it in their WP installations and if I should be aware of anything before updating (i.e. will I need to re-authenticate with bitly new API? should I pay attention to something specific while updating? etc.)

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi faquick! Yes, I had to reauthenticate for the the new WP Bitly to show the custom domain on my Bit.ly account.

    Didn’t notice any other issue other than that. It seems to be missing the Short URL tab on the posts’ admin bar, but when you edit the posts, you’ll see the WP-Bitly section. It shows the stats — which has real-time figures — and a button to get the short link.

    Plugin Author bitlydeveloper

    (@bitlydeveloper)

    Thanks @faquick! We’re excited to be back & live. This Plugin was built by clint.s working directly with Bitly. It should support existing functionality from the previous plug-in plus additional capabilities such as use of a custom domain! Please let us know if you have comments or questions!

    Thread Starter faquick

    (@faquick)

    I bit the bullet and updated, I also disconnected and reconnected, but I cannot see my custom domain on the settings page: I only see the default bit.ly. When I go and edit a post and click on “get shortlink” I see the right custom domain. I am using a free Bitly account and I selected my custom domain as default on Bitly settings, so probably it will keep that setting, but not seeing it in the WP dashboard creates some confusion. The previous release did not show any of that, so I think it is by design for it to use the default even if it is not “bit.ly”. I am not sure if this is a bug or if it would only work for custom domains on paid accounts. If that is the cause, maybe specifying it in the interface would avoid any confusion ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘New life for this plugin?’ is closed to new replies.