I installed this plugin a few weeks ago using bit.ly as my shortener and have noticed a huge spike in calls to the bit.Ly shortening API. For the most part, I didn't have a problem with this as the calls have died down but I am now getting HTTPS calls to bit.ly and my site doesn't use this protocol for any of the articles or content. I get in the order of 50 calls a day to bit.ly to shorten non-existent HTTPS pages.
There must be something in the code of the plugin causing this. I would love to see it fixed.
Cheers.
http://wordpress.org/extend/plugins/wp-tweet-button/
Interesting. i don't exactly know what could be going on. Until the next release you can:
find:
if ($perms == false) return false;
add this line after it:
if (strstr($perms,'https://')) return $perms;
This will prevent shortening of https:// URLs.
Version 2.0.3 has an option to exclude https urls from shrinkers.
Thanks, I will give that a try!
Tanin, I still have that same problem when using bit.ly, also for http protocol. When I revert back to the normal button everything is fine. But, if I set it up to shorten via bit.ly, then I get a raft of API calls. Looking at the URLs of the API calls, I think the calls are the result of some sort of interaction with a webcrawler, meaning the button triggers an API call to bit.ly to shorten a page even if the page doesn't exist because of the webcrawler.
For example:
http://www.creditwritedowns.com/2009/05///////twitter.com///credittrader///status///1669174400
http://www.creditwritedowns.com/tag/forex/page/31
I can't access your site. Are you using a manual placement?
The site is now up. No, I am not using manual placement. Tanin, I think this is bit.ly's problem more than the plugin but I wanted to alert you to it. I switched to cl.igs as a shortener and the problem goes away.
