Tanin

This plugin already has the option to remove it. The setting is called “Tweet link text” ??

The plugin shows the images as they’re uploaded. Checked the image URL?

Seems like the JetPack plugin is overriding the Tweet Button preferences. You could try opening the jetpack/modules/shortlinks.php and commenting out or removing the add_filter line at the top of the file.

Thanks. The WP Render Blogroll Links runs on more than 20.000 websites. We’re really happy with it.

Can you see if the issue is resolve in the latest version (you may need to clear your short url cache). Also, can you direct me to your site?

I can’t access your site. Are you using a manual placement?

Try using “Display the same tweet count across all shorteners” and if that doesn’t work, clear the shortener cache by checking the box labeled “Delete all previously saved shortlinks when I save” and save.

I suspect your template has removed the default hook to the_excerpt and uses a customized function to show excerpts. You can use the new version but you’ll have to clear the “Tweet link text” in the settings. That will remove the “Tweet” text from view.

This concept has been applied in 2.0.3

Version 2.0.3 has an option to exclude https urls from shrinkers.

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.

Yup.
Examples:

// Horizontal placement:
echo tweetbutton(null,null,'horizontal');

// Vertical placement (box):
echo tweetbutton(null,null,'vertical');

// Placement without a counter:
echo tweetbutton(null,null,'none');

The jumping through hoops in filters was done because some templates do crazy things with the excerpt filter. I’ll be testing your mutations against these templates and implement them in the next version.

The tweetbutton function doesn’t output the button, it just returns it. To output the button use echo tweetbutton();

That might have been due to a server issues at my end. Try again and let me know if it’s been resolved.