This post relates to a bug described here: http://drupal.org/node/1047148
An issue with the Tweet button for Drupal was identified. The Tweet button counter was not working and clicking on it resulted in a failed searched. Tracing through the code it was discovered that the data- url was being encoded incorrectly. If we set the data-url to: http://www.mysite.com/?q=node/76 Then click on the counter to do a search (after a successful tweet), the URL passed to Twitter becomes: http://twitter.com/search?q=http%3A%2F%2Fwww.mysite.com%2F%3Fq%3Dnode%252F75 The portion to note is: node/76 which becomes: node%252F75 The problem is that the last '/' is encoded as %2F but the '%' is then interpreted as a string and converted to %25. So, there seems to be a special case where the last portion of the URL query is encoded twice. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
