Thanks, I’ll get on that.
update 1.8 should fix this, let me know if you still have problems.
Yep, that looks like it fixes it. Thanks!
Yep, that looks like it fixes it. (Interesting that the post_status is future at that point when it wants to send out the tweet, but that seems to work.) Thanks!
I’m not sure if anybody else experiences this but when I _update_ a post via an xmlprc client, it tweets again, is there a way to stop this behavior? It also generates a fresh bit.ly URL which is kind of annoying.
It might be a handy feature if it.. a. It recognized it was an updated post and appended something like [UPDATED] to the end of the tweet. b. It used the original bit.ly URL
@cqrt Sorry it took so long to reply. Version 1.81 should fix this, although it will only work with posts that are tweeted after the 1.81 update. As far as I know, it is not possible to see if the post has been previously published when using xmlrpc, to get around this I am adding meta-data to all posts after they have been tweeted. In the future I think I will add an option for tweeting a post on update with modified tweet content. As far as the bit.ly links, it was my understanding that if you sent a url to the API and a shortlink already existed with that key, it would simply return that shortlink instead of creating a new one. I’ll have to look into it further. Thank you for your feedback.
@danperron Thanks for the update, I can now abandon the web interface for updating posts.
it was my understanding that if you sent a url to the API and a shortlink already existed with that key, it would simply return that shortlink instead of creating a new one.
It should work in theory but unfortunately bit.ly’s system of detecting duplicate URLS breaks if you use a URL with some additional parameters, for example adsense UTM parameters, which I found out the painful way after installing a UTM tracking plugin combined with a social bookmarking plugin that had a bit.ly API feature, resulted in 800 new duplicate URLS spamming my bit.ly account over a 3hr period.
http://www.site.com/dir/post/
http://www.site.com/dir/post/?utm_source=… etc
Bit.ly doesn’t recognize that these will go to the same page and will produce a new URL.
But I digress, on this occasion the new bit.ly URL was my fault as I slightly changed the post title before updating.
Cheers
