Our Recommended Tags plugin for WordPress 2.3 has only been out a few days, but we just released a pretty big update thanks to some of the feedback we’ve received via email. This plugin works off of the new WordPress 2.3 tagging system, and having spent several hours putting this together I have to give the WordPress development team major props. They did an amazing job putting together an intuitive backend to the tagging system which has made the development of this plugin a thousand times easier.
So what’s new in Recommended Tags? Check it out:
- New configuration screen makes it easy to manage nearly every aspect of the plugin!
- Type-ahead tag completion matches what you’re typing to your existing list of tags. I even made it show the number of times a tag has been used in parenthesis after the tag name.
- and more…
Of course words can’t explain everything, so I’ve snapped two screenshots that show what Recommended Tags is capable of (left: configuration screen, right: using the plugin):
So what’s next? I think everything I personally want to see in the Recommended Tags plugin is done, but I would love to hear your opinion. I eventually plan on writing a new plugin for managing your tags in a central location, because WordPress 2.3 has no way to add/remove tags like it does for categories. I would love some feedback though.
Enjoyed the post? Subscribe to our feed to get a daily dose of CyberNet!
Tags: Newly Released, Software, Screenshots, WordPress
Related Posts:
- Recommended Tags Plugin for WordPress 2.3
- Recommended Tags for WordPress
- WordPress 2.5 is Pretty Nice
- WordPress 2.1 Ella Released – Over 550 Bug Fixes
- Jack Slocum’s Comment System Available as a WordPress Plugin
Very nice! Thanks for supporting this plugin Ryan. I need to upgrade to 2.3 so I can start using it!
You just have to be careful when upgrading. We just did it on our site yesterday, and ran into a few unexpected bumps along the way. There have been a lot of database changes, but it really is for the best.
When I am writing a page, it shows a error below write page box:
I am aware of this error, and am working to fix it. I just can’t reproduce the problem.