Please try them out and let me know your feedback!

Remember, this is beta (uh, more like alpha) software and has been barely tested. It works with:

• WPMU  1.3.3
• MySQL 5.0
• PHP 5.2.5

As you use, it please let me know what version you’ve been able to get it running on. I appreciate any feedback that can improve the plugin.

Why another search plugin?

Well, this one is written specifically for the WPMU. There are a few plugins that already do this, but they all require some kind of core file hacking, running some back-end cron job, or modifying the default templates. I wanted something that was completely plug-n-play.

If you had an ideal global WPMU search plugin, what would be on your wishlist?

Get the update.

This can be beneficial for tag or category searches, and even for custom attachment archives.

If you use it, let me know!

Download page: Attachment Category Updater WordPres Plugin

I’d agree that simply deleting the feed-* files would be sufficient and acceptable. However, whenever I hack (or remove) core files, I add extra work for myself when it comes time to upgrade. The added work comes in remembering to delete those files with every upgrade.

The solution? A plugin. WordPress has a great framework for plugins. And that’s why there are so many great ones. So here it is… The No Feed WordPress Plugin.

If you use it, let me know!

Download page: No Feed WordPress Plugin

So how can you encourage people to comment more? Here are a few tips:

• 10 Techniques to Get More Comments on Your Blog (ProBlogger)
• 10 Tips for Attracting More Comments (Performancing)
• Increasing comments (Blogozine)
• Understand why people don’t leave comments by (Successful Blog)
• Get on the D-List (Courtney Tuttle)

How are people encouraged to comment on your blog?

Favicons are those little icons in the Address bar and next to your Favorites. When I migrated to Blogger, I lost my custom favicon and inherited the default, orange “B.” To restore it to my original “j.u” favicon, I performed some first-grade slight-of-hand trickery (It’s really easy).

1. Choose a favicon host.Although possible, Blogger doesn’t make it easy to upload non-post files. To get your favicon online, you need to sign up with an image host. I chose ImageShack since I had a few things on there already. Others you could use include Photobucket or even GooglePages.
2. Create my favicon.If you’re creating your own, simply create a 16 x 16 pixel image. You can save it as a GIF or PNG. They should both work.I already had a favicon, although it was in .ico format. When I was on my own server, that was fine, and correct. ImageShack, however, doesn’t allow the uploading of .ico files. I had to convert my file to a standard image format. I chose PNG.
3. Upload my faviconI uploaded my favicon. Imageshack gave me a few choices of code to use to display my favicon. I copied the “direct” URL and pasted it in the next step.
4. Add favicon to templateOnce my favicon was online (it took less than 4 minutes), I inserted the appropriate HTML into my Blogger template.<link href="URL_TO_YOUR_FAVICON" rel="shortcut icon">

The whole process took less that 10 minutes, and almost less than 5. If you’re ready to dump that orange B for a spiffy new icon that better represents your blog, the four steps are all you need. If you need help with any of the steps, feel free to leave a comment.Update: If you’re getting some kind of parse error in Blogger, it’s probably looking for a closing tag. Try this code instead (note the added slash toward the end). <link href=”URL_TO_YOUR_FAVICON” rel=”shortcut icon” /> 

My WordPress paths had this structure:
http://jason.ungos.com/2007/09/27/blog-downgrade/

On Blogger, the same post looks like this:
http://jason.ungos.com/2007/09/blog-downgrade.html

Here’s how I’m doing it.

1. Setup a missing files host.
2. Redirect visitor to new Blogger path.

Blogger Missing Files Host
The missing files host option was probably created to deal mostly with broken images or downloadable documents. I’ve expanded its use a bit by creating a custom 404 page that has some redirecting functionality.

The custom 404 page is a PHP script that:

• Checks the URI
• Determines what kind of document is being requested (post, tag search, etc.)
• Semi-intelligently determines the new URI, and
• Redirects the visitor.

Here’s what I have so far:

It’s neither elegant nor robust, but it achieves my main goal of dealing with old post links. I plan to develop this a little more to accommodate changed page names, broken images, and feeds.

Anything else I should add?