I was starting to lose hope when Alpha 5 came out, and was despondent by the time Alpha 7 did. I'm plugging along with the book, half way through the first draft, but at least 25% will need to be revisited to complete examples that hit brick walls because of things just not working as they should, yet, such as custom fields not appearing in the Views sort criteria field list.
Some would say that I'm crazy using Drupal 7 Alpha 5 to relaunch my blog, but I needed D7 up and running for the new book anyway, and some would say anyone who has churned out code as long as me must be crazy anyway, so it doesn't much matter. Sure, it's bleeding edge, and not ready for prime time, but it works well enough at this point, and a couple months some daytime soaps won't kill anyone.
In a Drupal view, one of the presentation options for a selected field is to have the field be a link to its node. What if you need the label to also be a link? No problem! Another option is to rewrite the output, so you can manually create the links using HTML, and specify the replacement pattern of [nid] for one. The only problem is that when a field is a link to its node, the URL that appears is the path alias, mydomain.com/my-content, but when using [nid] in a manually constructed link, the resulting URL is mydomain.com/node/##.
...Green's book is without a doubt the definitive practical guide to using the Views 2.x module in Drupal 6...
I created a view the other day, a simple view with one display, and change the Pager setting to Full. I had the view set for 50 records per page, and there were hundreds of records. When the first page loaded, there was no pager present.
And so began the head scratching.
I created a high level template (views-view--mypage.tpl.php) and dumped the $pager variable, preceded by *****. All I had on my output was *****. It would've been nice if I had a CSS display:none for the pager, but that's not the case.
So, what's the answer?