I've been heads-down for the past 4+ months working with Bonnier in an effort to migrate FieldAndStream.com and OutdoorLife.com to Drupal 5. I'm proud to say that earlier this week, both sites went live! In case you're not familiar with Bonnier, they're also the parent company of Popular Science, a well-known Drupal site.
As a contractor to the development team, I took part in adding new and expanding existing features to the sites. The previous incarnation of both sites was based on a proprietary content management system that had reached its limits.
The two sites have virtually the same feature set, but each one has their own custom theme and vocabularies (and not just in the Drupal-ese meaning of the word!) Therefore, most of the work we did had to be written in a generic enough way to work in both places.
It is often desirable to add a node count to the title of a view to help users gauge how many nodes have been returned - especially when using exposed filters.
In Views 1.x, this is a fairly simple process using the "hook_views_pre_view(&$view, &$items)" function (documentation).
Let's say you have a view that displays titles and authors all content of type "story" on your site in table format. Furthermore, you've exposed the "Node: Author Name" field as an exposed filter for the view:
Collecting and using user profile information has always been a popular aspect of the Drupal module scene. The Profile module (part of Drupal core) has always been a relatively straight-forward way of collecting additional profile data about users, but its lack of default Views and CCK integration has been problematic for most users.
Saving user data as nodes has been possible using a variety of methods for quite a while, but it seems that with Drupal 6.x, things are coalescing around the Content Profile module. This allows you to set a particular CCK content type as a user profile (the module actually creates a default "profile" content type automatically for you) - thus gaining all the advantages of CCK and Views (and their associated universe of modules) when dealing with user profile data. This is extremely powerful and lets you do all sorts of wacky things with your user's profile data (don't be evil).
This article talks about the (relatively easy) process of getting the Content Profile module configured for a Drupal 6.x site. Then, I'll go through the process of making one of the profile fields available to Views and a template file for use when displaying a node. This might be useful if one of the Content Profile fields you're collecting is a short biography of the user that you want displayed within any nodes the user has authored. Then, your standard node view can look like this:
Seeing how Drupal consulting is about 90% of my business, I figured it would be a good idea to upgrade AnelloConsulting.com to not only the latest version of Drupal, but the first commercially supported version - Acquia Drupal. While most of my clients are still focused on 5.x, I have begun recommending to new clients that they use 6.x and consider using Acquia's support services.
Everytime I have to dig a little deeper into the views module, I'm always more and more impressed with the thought that went into the module by Earl Miles and the other authors. A recently had a request from a client to modify the "more" link that is shown at the bottom of blocks that are generated by views.