A great plugin called Sabre is a great option to let users who want to register on your blog to verify themselves as being real humans. What is Sabre you say? I let the author tell you that:

SABRE is an acronym for Simple Anti Bot Registration Engine.

Whether you all know or not, I am still gonna give you an intro to Bad Behavior. BB is an excellent plugin (perhaps that’s not a proper way to address a solution that’s much more than that) for WordPress. It protects your WordPress powered blog (which of course which you are self-hosting) against a range of bots, spammers, harvesters and so on.

Bad Behavior v2.0.22 lets you integrate the resources of Project Honey Pot (PHP) in the fight against the bad guys. It all sounds very good, doesn’t it? It should so too. But when I actually registered on PHP and entered my key on BB, Little was I to realize that I was putting myself into deeper mess.

Well, actually I should have written that I have added the Avatar Plugin to the blog. But since the author of the plugin calls it the Gravatar plugin, then who am I to change that.

Well, actually this plugin supports a lot of Avatar based services including Gravatar, MyBlogLog and OpenAvatar (?).

What I did was I didn’t really understand the settings for this plugin so I just played around with the settings until I found that it could display avatars from MyBlogLog on the comments form. Well, what have I got to loose in that? I just left it at that.

I don’t really have the time to read manuals and make tweaks like that! I have a lot more on my plate than I can eat already so no more extra puddings (or help files) for me! Eeeeew! I feel like puking already….

I am deactivating the World Wide Lexicon Plugin with immediate effect on APU!. This is being done to clear up my RSS feeds. Ever since I activated the plugin on my blog to enable translations into different languages, my RSS feeds have been mixed up with code coming from this plugin.

Actually the WWL plugin uses a hook to attach itself with the content of the post. Somehow this is not checked by the plugin whether it is being displayed on the website or is being seeded as an RSS feed.

After much deliberation and with the widespread availability of such tools as Google Translation and Altavista Babel Fish, I am removing the plugin to avoid discomfort to my readers who use Feed Readers to subscribe to my site.

Sorry, WWL project, I don’t understand why this issue was not fixed until now? I have to remove the plugin. I thank all for using the plugin on my site and apologies for removing it.

Well, sometime back I had managed to put together a list of WordPress Plugins I Use. This is an updated version of that very list. It’s not much different from the previous one except that I have stopped using some of the plugins from that list and started using some new ones to increase functionality of my blog and keep it running in an optimized and tip-top shape.

So, without further ado, here comes the list:

I just found this article on Weblogtoolscollection.com which talks of a plugin that allows WordPress to be integrated with Drupal. Good news (if it’s working perfectly) for those who have been managing the two installations separately. The integration of logons is also a feature of this plugin which lets you use a unified sign-in both the systems.

I had downloaded this plugin called WP-Wetfloor plugin by Siuyee which is in turn a wrapper plugin for Cow’s Reflections.js javascript code and makes it work on WordPress (well up until version 2.1 came out).

When version 2.1 came out, a lot of plugins broke up (with WordPress) due to a change in the hierarchy and many events were either dropped or renamed. Unfortunately for us, the Wetfloow plugin was a casualty of this change. After the author of WP-Wetfloor expressed her inability to make changes to it due to lack of time, I was trying to figure out how to modify the plugin myself and make it available to you all.

In the meantime, I found a workaround for this problem. As I work towards finding a way to fix the issue with this plugin with regards to it’s integration with the Editor in WordPress, I encourage you to use this workaround. It will be a little bit time consuming but believe me it IS worth the extra time. Don’t you agree?

To make the plugin work, simply install the latest version of the plugin from the plugin’s homepage and install (and activate) it to your blog.

After you finish doing this. Instead of searching for the button in the WordPress Rich Text Editor, simply insert an image using the normal “Insert Image” button and then go to the Code tab of the editor.

After going to the Code tab (which shows the HTML code for the post that you are editing), find the <img src="path to your image" /> tag that has the image that you want to use the Reflection API with and insert the following line class="reflect rheight80 ropacity40" in the same tag. After you insert the tag, it should look something like this:

<img src="path to your image" class="reflect rheight80 ropacity40" />

That’s it. This should do it for you.

Liked the article? Or not? Please share your feelings. I want some praise from you (or my share of ass-kicking if it is justified! ). Post your comments.

So, I was just looking around and found this post, Two Amazing WordPress Plugins, that gave me the whereabouts of a very good multilingual plugin for WordPress from the Worldwide Lexicon Project that helps users of a WordPress blog to translate the blog to different languages.

Now, this means a lot of things get solved for me. I have observed a lot of spanish users on my blog and since Google has been creating difficulties for some other widely available plugins in using Google’s Translation services via automation, I thought this will be a good alternative.

Atleast we have some hard working people over at the WWL project who are dedicated to the understandability of one language to another. I wish them good luck.

Oh yeah, and thanks for this good plugin. It will help my blog’s readers to read in their native languages whatever I write here.

I was using the Ol_Feedburner Redirect Plugin v2.1 by Steve Smith which had been released by him and was being maintained by him since 2005. Now it seems this plugin has been discontinued by him and does not support the new release of WordPress v2.x.

Now the reason for this is, hold your breath!, it’s adoption by FeedBurner themselves. They have adopted the Ol_Feedburner_Redirect plugin and have renamed it to Feedburner FeedSmith.

The original URL is also giving out a link to the new page of the plugin.

The new plugin does the same job of redirecting all your RSS feed access to your centralized feed at FeedBurner.

If you are installing and need more instructions on this plugin, check this article by FeedBurner for WordPress blog users (who host their own blogs).