Hey guys, I'm not sure why, but the plugin stopped working... Now every time I post something, instead of my short link I have something like http://www.zunkabitz.com/post?=404. Why is that?
I have to ask you the obvious first, just to get it out of the way; did you update your legacy API key with a new token from the link provided?
Once we know that's not the issue, I can better help figure out the problem!
Yeah, I did that yesterday.
Have a look at my Twitter: https://twitter.com/zunkabitz
See how it used to be "http://zkbtz.tk/" (because Bit.Ly) and now is not? That's what I don't understand...
The same thing happened to me after the update. Here's my twitter that shows its no longer using my custom short url. https://twitter.com/Chattertainment
Same problem here.
I have changed my token, and the short link not work any more
Same here, still happening..
HI Guys, I have the same problem. Plugin is not working anymore with the new token method. I have confirmed the the token has been entered exactly as it was and its still highlighted red when I save.
Same problem, any links work, have a longer links... please patch thanks for your work !
Give 2.2 a try. I updated the plugin to use the WordPress http API instead of directly calling cURL. With any luck that should cure the issues!
If anyone who posted tries the new version and can confirm it's working, that would be great.
It doesn't appear to be working.
@leonardogsouze, version 2.2.1?
Is it accepting the OAuth Token (is your input red)?
I tried the update and the OAuth Token is still red.
2.2.1 and the OAuth Token seems to be fine, not red.
I'm sorry, it is red.
Actually, up until today I could still get the shortlink doing this: I'd schedule my post to 10 minutes in the future and when the page refreshed, I'd have the option "Get Shortlink" right below my post title. However, now it gives me a general address like http://www.zunkabitz.com/?p=4083
Alright, I think I figured it out. Released 2.2.2, should be up on the repo in a matter of moments.
You will have to go to the settings page and resubmit (save changes) and it should authorize the token this time.
2.2.1 work for me ;)
I can't find the update 2.2.2 even though it says 2.2.2 on the changelog.
I deleted the plugin and tried to install again, but all I could find was 2.2.1
Now that I reinstalled the plugin, the Oauth token is no longer red. However, still doesn't work.
For some reason WordPress.org ignored the 2.2.2 update. I dislike releasing updates simply for the sake of upping the version number (especially when I just put how many updates out?) but that's frustrating to say the least.
I'm going to fiddle around with it some today and release another version this afternoon in hopes that the repo will pick it up this time.
Still out there? There's an option to turn on debugging in the latest version so we might be able to get to the root of this finally. :)
Hi Guys, seems to be working for me now with latest release. Im a bit disappointed that the "get shortlink" option was removed from the admin bar. Now it take extra time having to enter the post to get the shortlink.
I've checked the Debug box, now how do I see the result?
So I've updated it to the newest newest version, still not creating the correct shortlinks. As everyone has stated it ends up being the full url with what leonardogsouza has. Done (and redone) the Oauth token and still no luck. Just updated the plugin to newest version in hopes it would fix it, but just published another article and no luck. Still doing the same.
What's the status on this issue?
leonard, the file you're looking for is
/wp-content/plugins/wp-bitly/log/debug.txt. Pop it open and with any luck we'll have an error message from the http request that could help us fix the issue. If it's short and doesn't contain any sensitive information, please post it here. Otherwise you can send it to me directly via mark.watero.us/contact/
If you could do the same tony, make sure debugging is checked, save your settings once or twice to get a few entries in the log file, and start a new thread here with the results or send them to me at the link above if you would prefer.
Tried to access through FileZilla now but there was no debug.txt
I'll create a post now to see if it's working.
Depending on your server configuration you might have to temporarily chmod the
log/ directory to 0777. Once the file is created it should retain ownership and you can set the directory back to 0755.
I didn't make a very robust debugging system, because I don't intend to leave it there. :) It's just meant to give us some insight.
I hate to be that guy, but I'm not entirely comfortable with changing chmod & all that stuff. Just not something I understand at the moment and don't want to bring my website down. I can certainly do the debugging thing and post it (if it shows up, since Leonard said he didn't see the correct file).
Anything else I can do?
Still not working. The only way of using is to schedule my post to, let's say, 10 minutes into the future, then I get the option "Get shortlink", then I update the Publicize box with this link...
Just did another test (after the new update).
I didn't schedule my post, just wrote and posted it. Here's an example of how my posts used to appear on Facebook right after I click "Publish" (on WordPress):
And here is how it looks now:
As you can see, there is no shortlink and now I can also see the message "Posted by WordPress" right below "Zunkabitz shared a link".
This topic has been closed to new replies.