Plug-In Appears to Have Stopped Working

This sounds like a similar issue to the other currently unresolved thread. I’m working with them right now to try and track this down, and will keep you updated as anything new is discovered. Keep an eye open for an update to fix this hopefully in the very very near future!

Ok thanks, where’s the other thread link ?

I have your email but I have not had a chance to respond directly, that pesky day job is getting in my way at the moment. ??

I am going to continue to debug using the information Doug (@admindroidturf) has sent me, and will get back to everyone here as soon as I can.

Ok thanks, also as mentioned the version update has broken the plug-in, is there any possibility to roll it back to Ver 2.3.2 ??

Robert

The problem with reverting to 2.3.2 (which you can do by downloading it from the plugins home page >> Advanced View >> scroll down to the bottom, and then you’ll have to manually upload the plugin to your site) is that the authorization it used has been deprecated by Bitly.

All of your plugins are authorizing, but there’s a handful of people where the plugin is not properly saving the access token, and that’s what I’m hoping to figure out.

If I can’t determine what’s happening by this evening, I will try and release an interim update that allows you to manually add the access token supplied by Bitly when it redirects back to your WordPress dashboard.

I set up an environment that matches your PHP/MySQL versions and activated all the same plugins. No good, my test authorized just fine.

I have another suspicion. I’ll be releasing another update shortly that does two things: improves the debug log for the authorization process, and adds the ability to manually enter your access token.

Upon authorization, the notice at the top of the page will include the access_token sent back from Bitly. If you scroll down and don’t see it repeated in the text field next to Bitly OAuth Token, copy and paste it there, then save.

Alrighty, just pushed version 2.4.3

This adds new entries to the debug log, that will occur during an authorization attempt. With any luck the new information should narrow down my search if this version still doesn’t work.

This also adds the ability to manually add your access token. Once you’ve updated, please ensure “Let’s Debug” is still on, and disconnect from Bitly. Authorize again using the button as before. Upon returning from Bitly you’ll see your access token in the success message at the top of the settings page. If when you scroll down there is no access token in the text field below the disconnect button, you can copy and paste it in, then save.

Please let me know how it goes. Fingers crossed.

That’s great to hear! I’ll wait to hear back from @grunkern as well before I mark this thread as solved.

Reviews are always welcome! We don’t ask for them directly from the plugin, so I gotta plug em here once in awhile! ??

Thanks Robert!