Temerity Studios

Lets do a few things here, I’d really like to get this fixed for you.

First of all, can you turn on the Debug feature in settings, and then try and generate a few shortlinks again the same way you just did. Afterwards, take a look in your wp-content/plugins/wp-bitly/log/ directory and send me the generated file to [email protected]

Also if you don’t mind, could you email me or post here the URL to the domain you’re using Bitly on, and I’ll see if I can verify it against the API logs.

Nothing has changed with the way shortlinks are generated in the past two versions. The primary update was to the authorization process used with Bitly as they deprecated the old method while the plugin was in limbo.

Can I get you to double check on your Settings > Writing page that the button that appears next to Connect to Bitly says “Disconnect”? And that the post types (post, page or custom) are properly checked in the list next to Post Types?

• This reply was modified 8 years, 4 months ago by Temerity Studios.

I clicked the new logo and then the authorize button. It then logged me out of my WordPress session. However, when I logged back in, the shortlinks appeared. Thank you very much for your help with this.

Quoting this from the wpme shortlinks thread, I think you meant to post it here!

I’m going to mark this as resolved since it seems to be working for you now. I’ll re-open if anyone else has an issue with being logged out. Looking at the API server logs, it appears all redirects are remaining intact so it might be another plugin or other issue causing the logout.

Thanks for following up!

Hey guys, any new information on this? Did the instructions to disable shortlinks in Jetpack happen to work for you? Let me know, if this is a common issue with Jetpack or another plugin I’d like to sticky the topic so others can find it quickly.

Sounds like Jetpack shortlinks. The plugin used to arbitrarily disable that module so that it could override it, but we felt that was a little too unfriendly.

The filter should be running after Jetpacks, but you can also try disabling the module manually:

1. Go to Jetpack -> Dashboard.
2. Scroll to the bottom and click Debug.
3. Scroll to the bottom again and click Access the full list of Jetpack modules available on your site.
4. Look for WP.me Shortlinks in the list, and deactivate it.

I’ll set a task to look into this further and see if WP Bitly can override it without any inter-plugin aggression.

• This reply was modified 8 years, 4 months ago by Temerity Studios.

Taking a little longer than expected to work out the issue here. After a careful review it looks like the authorization server is doing what it’s expected to do and we’re at a loss at the moment for why your instance is logging you out.

If you’d be willing to let us take a closer look via your WP dashboard, please contact us at [email protected] to privately exchange that information. If not, totally understandable and we’ll continue to try and work it out from this end. There’s already a new version in the works with some minor updates, and we’d love to have this issue worked out for that release.

The issue appears to be a lack of base64 encoding on the state parameter. This is causing an issue on the verification server when it attempts to decode it.

It looks like you’re hosting with Bluehost? The function that should be encoding the parameter is part of PHP core, unless they’ve done something to disable it. If you could get in touch with their support and confirm whether or not they know of any restrictions on base64 that would help us narrow this down.