Mark
(@delayedinsanity)
I’m trying to work out where this issue came from. All the same hooks as existed in version 1 are still there, and there’s even a couple extra now which are attempting to hook into get_permalink when called from within a plugin — which is what I believe Publicize is doing.
From what I can tell it doesn’t request wp_get_shortlink, it uses get_permalink. I have no idea why. While I’m trying to make WP Bitly compatible, it has been a pain, though I’m sure once I figure it out I’ll have a why didn’t I think of that sooner moment.
I’ll be back shortly, I’m going to go play under the hood.
Mark
(@delayedinsanity)
Try 2.2.8 and see if that fixes your issue.
I tested this version multiple times with Jetpack and it was passing the shortlink for me, so I’ll cross my fingers that it does the same for you!
Hi! Just tested it, but it doesn’t work. This is what happens:
https://twitter.com/AlwaysNintendo/status/470964080354680832
Mark
(@delayedinsanity)
The link you posted doesn’t work?
I updated to the latest version (2.2.8) but it didn’t work. Currently I’m still running Jetpack 2.9.3.
Mark
(@delayedinsanity)
I wonder if we could do an experiment… I’m 98% convinced this has something to do with the way Publicize shares its posts, not WP Bitly’s ability to generate the shortlinks (partly because the short links are generated the instant a post is saved for the first time, they’re always there).
Have you tried reverting to a 1.x.x series of the plugin to see if it starts working again?
I tried 2.2.8 on my own and was able to get the correct links posted to Facebook and Twitter. There may be another conflict we’re missing entirely.
Good idea! I will test this next monday and post another update here.
Same problem here… But i got this problem with three plattforms (facebook, twitter & tumblr)
Just tested WP-Bitly 1.0.1 with Jetpack 3.0.1 on a WP 3.9.1 Test Site and it worked fine (link to tweet).
After updating to WP-Bitly 2.2.9 it didn’t work anymore (link to tweet).
I’ve got the same problem here! WordPress, Jetpack and WP Bit.ly up to date but the publicize does not use the shortened bitly link!
Mark
(@delayedinsanity)
Well that’s bloody interesting.
Now that we know that (it works in 1.0.1) maybe I can figure out what I changed… it hooks to the same filters, so it’s not that.
Sorry for the slow response time, it was a busy week at work.
Mark
(@delayedinsanity)
Alright, I scrapped the idea of adding functionality to fix what was broken, and went instead with trimming excess bloat until it works again. There’s only two things I can see that 1.0.1 had that 2.2.x didn’t, so I’ve reworked 2.3.0 to operate in much the same way.
Crossing my fingers and all my toes.
Just wanted to say the new update worked for me! I made a test post and Publicized used the Bit.ly URL. Using latest version of WP, Jetpack, and of course, this plugin 🙂
Now off to try and figure out my other problem.
2.3.0 works! Thank you for your great support!
Mark
(@delayedinsanity)
Let that be a lesson to myself; before blaming the other plugin, always go back to your roots and make sure you didn’t just have a moment of stupid somewhere along the way. 😉
