When A Plugin Has A Yo Yo Effect

I really like Digg Digg, but after upgrading it on one site, the css and coding has been messed up where it distorts the site. I am not the only one reporting this. Some of this was to upgrade with update social bookmark API and some of the buttons have aesthetically changed.

The problem is that this plugin goes through phases of “it works” or “it breaks” or like I call it… a yo yo effect. Of course, this is something a lot of developers risk because not everyone has the same themes or may not even be coding right. In the case as this plugin, I am thinking it is coding to their effect.

Of course, this is only a recent issue, but it has happen in previous versions of Digg Digg. There are other plugins, like Tweetmeme that have done the same. In the past with Tweetmeme, it did not pass W3C validation.

What is the standard that plugins should have? Should they only be tested on the default themes offered by WordPress? How much free support should a plugin developer offer for free for themes outside a WordPress installation’s default, tested, tried, and true themes?

As users, we can merely tell our favorite developers what is going on. Those with some knowledge in development should try offering help (this will help the WordPress community grow closer.) It would not hurt to chip in a little money for the cause, especially if the plugin creator offers such a great plugin for free (because seriously… developers are under-appreciated.)

Above all, do not expect a developer to give support for free. I have seen some people get nasty about lack of support for plugins, but there is also a percentage of them who have faulty themes that may be part of the problem. This is not unusual to see in the WordPress support forums.