Contrary to the instructions on this page, there is no option to format the View as "Row style: Node (teaser)". No "Node" options whatsoever are available.

Similarly, there is no option to filter by "Node: Type = Profile" or "Node: Published = Yes".

There is also no available option to sort by "Fields: field_pagecount."

Figure 8-21 shows setting the display options on the Chapter content type and shows several fields the chapter never told you to create. Figure 8-18 does the same. I know the book isn't supposed to detail every single step but I ran into problems when I tried to figure out how to follow here and would have appreciated some instruction. For example one of the fields not described is Internal name and this field is referenced on this page where you are told to enter a value into it when you create your first Chapter.

The tip on page 258 (Chapter 13, Putting a site online and deploying new features) does not work. The Features revert command needs some helper code wrapping around it, called straight it will fail.

Location of html.tpl.php is in:

/modules/system directory.

At the bottom of the page, in the Note it says "See additional material and ask question questions about..."

listing 16-29: The code doesn't seem to be working at all. I'm working on Linux (Ubuntu); there is the code here:
<?php
/**
* Implements theme_contact_site_form().
*/
function dgd7_contact_site_form($variables) {
// Hide the subject field. It's not required.
hide($variables['form']['subject']);
// Change the labels of the "name" and "mail" textfields.
$variables['form']['name']['#title'] = t('Name');
$variables['form']['mail']['#title'] = t('E-mail');
// Create output any way you want.
$output = '';
$output .= ''. t("We'd love hear from you. Expect to hear back from us in 1-2 business days.") .'';
$output .= render($variables['form']['name']);
$output .= render($variables['form']['mail']);
$output .= '';
// Be sure to include a rendered version of the remaining form items.
$output .= drupal_render_children($variables['form']);
// Return the output.
return $output;
}

On line 3:

//add the jQuery UI dialog to all elements with id of dialog

...author meant class, not id - sorry Jake! :)

Wrong jQueryUI for the droppable example

(near bottom of page)
"With a debugger (see dgd7.org/ide), you can try to watch all the functions..."
(The requested page "dgd7.org/ide" could not be found.)

grep -nHR --include=*.module 'View site reports' modules

I am using the MINGW32 Git Bash command line tool in Windows Vista. The above command produces the following errors:

grep: invalid option -- R
grep: unrecognized option '--include=*.module'

The second paragraph under the "Enable" section states:
"Drupal will not allow you to enable a module if all dependencies are not present in your site files.",
which means if none of the dependencies are present. While this is true, the text should read:
"Drupal will not allow you to enable a module if not all dependencies are present in your site files."

"... and massaging you Views using this ..." should read
"... and massaging your Views using this ...".

The instructions for creating a filter to limit the content to articles written by Bob is written as follows: "Select User from the Filter select box and select the User: Name filter from the list."

In my 7.10 installation of Drupal I don't see "User" as a choice in the Filter select box. I ended up using "Author uid" as the filter criteria. Perhaps I don't have the necessary module installed or enabled or perhaps Drupal changed this along the way.

The directions for handling zero results specify to click "Add and Configure". The only buttons are "Apply" and "Cancel".

"Click Before under Attachment position"... It sounds like I need to click something before doing something else.

Page 79 refers to an "Event" content type, but there is no such content type.

The git commit message
git commit -m "Diff module for helping show differences between features and content."
would be clearer as

The description of the User module and the introductory paragraph for the next set of core modules are formatted as a single bulleted paragraph, and the list of modules that follow (from Aggregator onward) are indented an extra level, giving the false impression that they're subsidiary to the User module.

In the text about the Token module, the possessive "URL's" is used instead of the plural "URLs".