This post relates to a bug described here:

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:

Then click on the counter to do a search (after a successful tweet),
the URL passed to Twitter becomes:

The portion to note is:


which becomes:


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:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to