I'm currently working on a multi-site Drupal installation. There is one theming module shared by all instances which exposes some key blocks and views they all require. During development, this was built on the initial site, so occasionally you will find something like this in the module:

That works fine for as long as 'my_theme' exists, but what if it doesn't on another instance using this module?

There are times when you don't want people to search for specific content types. For example, you may not want to be obliged to theme a content type which is not supposed to be visible anyway, just in case it surfaces in a search. Or there may be a content type which you specifically do *not* want people to be able to search on.

There are two ways to skin this cat, that I know of at least:

I have a use case that Drupal doesn't handle very well out of the box. It's funny, as you'd think it would be something everyone would want and, as such, there would be a stronger contribution in the core. The use case is this:

"Site administrator can filter site users by any available criteria and contact them via email as well as save them as mailing groups."