Link (in Safari Online version at least) to Countdown module is incorrect: Countdown (http:drupal.org/project/countdown/)

Note from the Author or Editor:
Confirmed. page 337, para 1: CHANGE: http:drupal.org/project/countdown/ TO: http://drupal.org/project/countdown/

In figure 3-16 it says Path Setting > File Path to type in Resumes. I always thought that for file paths you're better off not using capitalization. I'd suggest changing this to resumes.

Note from the Author or Editor:
Yep, resumes should be lower-cased in Table 3-16.

"Discerns between "spam" and "ham," and displays a CAPTCHA (Completely Automated Public Turning test to tell Computers and Humans Apart), " should be "Discerns between "spam" and "ham," and displays a CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart), " ie. Turning test should be Turing test (ps loving the book so far :)

Note from the Author or Editor:
Yes, that was dumb. :P Nice catch! Error is in p68, para 2.

2nd sentence in the second last paragraph reads: "And, unlike the CAPTCHA provided by a most websites, ..." should be "And, unlike the CAPTCHA provided by most websites, ..."

Note from the Author or Editor:
Confirmed. Nice catch *again*! :) Error is on p68, last paragraph.

At the bottom of the Job Application form, the last text field is labeled: "Salary:" should be something like: "Resume:"

Note from the Author or Editor:
Confirmed. That darn copy and paste gets you every time! :P

"Click Save to finish setting up the content type with the options from Table 3-7 to prefix the salary with a $ sign and give it a description." should be something like "Click Save to create the Salary field. Finish setting up the content type with the options from Table 3-7 to prefix the salary with a $ sign and give it a description." or to make things a bit clearer Put "Click Save to create the Salary field." above table 3.6 (where the salary field is created). and after table 3.6 "Finish setting up the content type with the options from Table 3-7 to prefix the salary with a $ sign and give it a description."

Note from the Author or Editor:
Good catch. This was an area that got must've been missed when CCK's user interface completely changed in like RC8 :P and we had to update all the hands-on instructions accordingly. Since I got to watch in awe our production editor Loranah painstakingly position all figures and tables so that they wouldn't end up in weird places or some pages wouldn't end up with a huge swath of white space, I think it's probably best to go with the first suggestion, even though I agree that the second would be more clear. Page 104, para 1: CHANGE: "7. Click Save to finish setting up the content type with the options from Table 3-7 to prefix the salary with a $ sign and give it a description." TO: "7. Click Save to create the Salary field. Finish setting up the content type with the options from Table 3-7 to prefix the salary with a $ sign and give it a description."

CHANGE: "Chapter 4: Job Posting" TO: "Chapter 3: Job Posting" (reported by Drew Gorton -- thanks!)

"Some examples are sorting by the created0 date..." should be "Some examples are sorting by the created date..."

Note from the Author or Editor:
Confirmed. Darn you, slippery zero, darn you. Page 120, para 1.

change: "...database of content and a single script, as shown in Figure 1-3" to: "...database of content and a single script, as shown in Figure 1-4" Figure 1-4 is the figure showing the single script and database

Note from the Author or Editor:
No, the figure reference is correct. But likely this is a combination of sub-optimal placement of Figure 1-4 and the wording of the sentence in question in relation to Figure 1-3. CHANGE: "...could be replaced with a database of content and a single script, as shown..." TO: "...could be replaced with one or more database-driven scripts, as shown..."

change: "Figure 1-4 illustrates how a content management system such as Drupal integrates all of these features." to: "Figure 1-5 illustrates how a content management system such as Drupal integrates all of these features." Figure 1-5 appears to be more illustrative of the features described in this paragraph than 1-4.

Note from the Author or Editor:
No, the figure reference is correct. Let's try: CHANGE: Figure 1-4 illustrates how a content management system such as Drupal integrates all of these features. TO: Figure 1-4 illustrates how a content management system such as Drupal uses a single database and script to integrate all of these features.

the phrase "Spotlight: Themes" is enclosed in double quotes; the second double quote is a left double quote--it should be a right double quote (close quote).

Note from the Author or Editor:
Confirmed.

Steps 1 and 2 start above Figure 2-15 then repeat again after the figure and continue on through step 3.

Note from the Author or Editor:
Oh, sheesh. Copy and paste strikes again! Beneath Figure 2-15, please REMOVE steps 1 and 2.

change: (admin/build/menus) to: (admin/build/menu) That's what's in the address bar when I did it

Note from the Author or Editor:
the change noted is correct and needs to be done at both #1s on that page.

Very small typo here when talking about Revision Moderation: "Revision Moderation [is] a simple utility module that ensures that the approved version of a module ..." That last word should be "node". Thanks!

Note from the Author or Editor:
D'oh. Confirmed. Thanks!

Under the Hands-On: Branding the Site section, the process starts with step 1, and on the following page (75) jumps to step 3. It doesnt appear as though anything is actually missing (step 2), the numbering sequence is just off by one.

Note from the Author or Editor:
Confirmed. Yet another "I hate you MS Word" moment. Thanks for the report!

The second warning snippet begins with "The most important filter of all is HTML filter,". It should most likely be "The most important filter of all is the HTML filter,".

Note from the Author or Editor:
Confirmed. Thanks! Actually, could we do: The most important filter of all is the "HTML filter," which strips... There is no "HTML" filter, and I can see people getting confused by this without the quotes.

The second sentence (starting with You should download...) ends with the quote "Hands-On: Working with Modules" section. It's a silly thing to point out, but the closing " is actually an opening quote (it's facing the wrong direction). :)

Note from the Author or Editor:
Hey, every "silly" thing that gets fixed makes the book easier to read. :) Thanks for pointing it out. Confirmed!

In the graphic, at 'Line break converter' and 'HTML corrector' stages, the <script> tags are back in the text.

Note from the Author or Editor:
This is correct. Do we need to submit a new graphic or is this something you can edit out? In the HTML corrector box, the <script> and </script> tags need to be removed.

Caption for fig. 2-60 reads wrong.

Note from the Author or Editor:
CHANGE: Directory structure for the FCKeditor website INTO: Directory structure for the FCKeditor module

The suggestion snippet references a file path for the FCKeditor module as "sites/modules/fckeditor/", whereas it should be "sites/all/modules/fckeditor/".

Note from the Author or Editor:
Yes indeed. Thanks!

The second paragraph in the Summary section is currently "Here is a list of modules were referenced in this chapter:", while it should read "Here is a list of modules we referenced in this chapter:".

Note from the Author or Editor:
Confirmed. Thanks a lot!

After logging in with the username user and password oreilly, the form at Create content&#8594;Job Application (node/add/job) should look as shown in Figure 3-15. (node/add/job) should be (node/add/application)

P. 111 Table 3-17 delete any own application content edit any own application content should both be changed to delete own application content edit own application content removing the 'any' looks like a cut and paste error. :)'

Note from the Author or Editor:
Confirmed.

In the text between the two sets: "mdule" s.b. "module"

"Click the Fields fieldset section title" is confusing, as the word "fieldset" doesn't appear in the views/edit/applications page. Probably "fieldset" is residual from an edit and s.b. deleted?

Note from the Author or Editor:
remove the word fieldset from the sentence "Click the Fields fieldset section title..."

This should be added to the big list for coherence. Page 143, first paragraph: CHANGE: Figure 3-41 TO: Figure 3-42 You already have: Page 143, second paragraph: CHANGE: Figure 3-46 TO: Figure 3-47 But not the first one I entered.

Note from the Author or Editor:
Yep, Page 143, first paragraph: CHANGE: Figure 3-41 TO: Figure 3-42

In Table 3-38 it says that Title is "Jobs I've Applied For", but in Figure 3-48 Title is displayed as "My Applications."

Note from the Author or Editor:
Change the text in Table 3-38 that currently says "Jobs I've applied for" to instead be "My applications"

http://drupal.org/project/auto_nodetitle) <- A closing parenthesis without the opening one (It's also on the link)

Note from the Author or Editor:
remove the end paranetheses from http://drupal.org/project/auto_nodetitle) The line should read: Automatic Node Titles, http://drupal.org/project/auto_nodetitle

"allow user to clear view" should be "allow user to clear value" Also, "Number of options" Should be "number of stars" Then also, lower in the page, after the following paragraph, in the bullet list of arainged fields; the terms "rating, pros, cons" should be indented to reflect being children of the Summary group.

Note from the Author or Editor:
Confirmed all of the above. Thanks! Table 4-7: CHANGE: Allow user to clear view TO: Allow user to clear value CHANGE: Number of Options TO: Number of Stars Bottom page 163 - top page 164: CHANGE: * Summary * Rating * Pros * Cons TO: * Summary * Rating * Pros * Cons (Rating, Pros, and Cons should be indented)

In: check both the “Content: Amazon item: Amazon product ID (field_product_id)” and “Node: Voting results relationships." the word "relationships" does not appear and should be deleted.

Note from the Author or Editor:
Quote is in the wrong place. CHANGE: ...and "Node: Voting results relationships." TO: ...and "Node: Voting results" relationships.

The 'Value' column of the table reads 'Vote tag: Default vote'. This, I assume, should have the word 'Default' removed to read 'Vote tag: Vote'.

It says "enable the Core: Search Module". Should be "enable the Core - optional: Search Module."

In the text "2. Go to Administer&#8594;Site building&#8594;Views (admin/build/views) and click the Edit link for our Product finder view." the word "finder" introduces an ambiguity. The view is named "products" while "Product Finder" is the Title of a page view we added to it. When you say "our Product finder view" it is not clear if you want us to work on the default or on the Product Finder page view. Presumably the default; if so delete "finder".

Note from the Author or Editor:
number 2. should say "Go to Administer > Site building > Views (admin/build/views) and click the Edit link for our Product view.

The text 'Go to Administer&#8594;Content management&#8594;Content types (admin/content/node-type), click the “edit” link, and then click the “Display fields” tab (admin/content/node-type/review/display)' has an ineffective URL, "(admin/content/node-type)," which leads only to a replay of the admin/content page. It should be admin/content/types. It would be good also to insert the phrase "for the Product review type" after the word "link." Yeah, it's pretty obvious at this point that we don't want to work on the fields of Page or Story. But still.

Note from the Author or Editor:
Nice catch. CHANGE: Go to Administer->Content management->Content types (admin/content/node-type), click the "edit" link, and then click the "Display Fields" tab... TO: Go to Administer->Content management->Content types (admin/content/types), click the "edit" link for the Product review type, and then click the "Display Fields" tab...

Table 5.1 Says 'Name Wiki page' Figure 5.2 shows 'Name Wiki' Very minor incongruity.

Note from the Author or Editor:
Confirmed, thanks! Figure 5.2 needs to be updated. Name should be "Wiki page" rather than "Wiki" to match surrounding text.

It says to click "Add input filter." It should be "Add input FORMAT."

Note from the Author or Editor:
This is correct, except the corrected word "format" should be in lower case: "Add input format,"

Minor minor issue, but could throw off those new to Drupal Later part of paragraph reads: For instance, you can set up a pattern for naming the path of all new blogs to be

Note from the Author or Editor:
CHANGE: ... so that you automatically get something like "blog/2007/june/08/my-first-blog-post," as shown in Figure 5-10. INTO: ... so that you automatically get something like "blog/2007/june/08/my-first-blog-post." Figure 5-10 shows the automatic alias set by Pathauto for a wiki page, titled "Help," which is using the pattern "wiki/[title-raw]."

Says "Do the same for our user" - should be "users".

It says "Access .... Type: by Role". But first you see "Defaults: Access restrictions" with a radio button to select "Role". Then when you click "Update" it shows "Role:" with a check box for each role. Click "authenticated user" and then click update again.

Note from the Author or Editor:
Confirmed. Table 5-5 is kind of useless, actually. However, removing it would change all future tables' numbers which is a huge PITA. So let's do this: CHANGE: (Current Step 4) TO: Limit the visibility of this view to authenticated users by entering the Basic settings shown in Table 5-5, and clicking Update. Select the authenticated user role in the following configuration screen and click Update once more.

Step 9 says, "When finished, you should see..." but you won't, because during and after step 8, the Page display is active. Figure 5-18, from the lack of italic attribute-names, is the Defaults display. Yeah, I know, pick-ee pick-ee pick-ee. Just the same, I recommend you reword step 9 to say "When finished, the Defaults display should resemble..."

Note from the Author or Editor:
Pick-ee is good! :) Probably best to replace that figure with the proper one. I've uploaded a replacement for Figure 5-18 to http://img.skitch.com/20090223-89txcymew25rm5uran2n5bfmkh.png.

"Access system administration pages" should be "access administration pages"

Note from the Author or Editor:
Confirmed, thanks!

Very minor error... says "Placate writer" should say "Placate author"

Note from the Author or Editor:
Silly typos! Thanks! :)

"The files directory is configured at Administer&#8594;Settings&#8594;File System" is incorrect, the menu structure as I'm sure you know is Administer > Site Configuration > File System.

Body field label should say caption.

Note from the Author or Editor:
Confirmed, thanks! Table 7-1: CHANGE: Body field label: [blank] TO: Body field label: Caption

Just found a couple of small places in Chapter 7 where the text here deviates from our internal team conventions of placing the word "package" after the name of each section on the modules page. Page 253, step 2: CHANGE: - ImageCache [the initial bullet] TO: - ImageCache package Page 257, step 1: CHANGE: - Other TO: - Other package CHANGE: - Views [the initial bullet] TO: - Views package

"Administer->Site Settings-> ..." should be "Administer->Site Configuration-> ...

The caption of Figure 7-29 does not seem accurate. Compare to caption of Fig 7-28. This does not show the Front page, but the view for it. The wording of 7-29 is at least awkward: "The block view used on the front page"?

Note from the Author or Editor:
Correct -- looks like copy/paste strikes again. The caption Figure 7-29 should read: "The block display of the Latest Photos view."

The link to the Signup module says: http://drupal.org/projects/signup, instead of http://drupal.org/project/signup. This results in a broken link. I have done this myself several times, and now I feel I am in good company! :) The error was found in the PDF sample, UsingDrupalch9.pdf.

Note from the Author or Editor:
Darn, you're right! Thanks for the report. :) In the "real" book this is on page 313, last para, first sentence. CHANGE: http://drupal.org/projects/signup TO: http://drupal.org/project/signup

Table 10-2 Setting Class ID Value T-shirt Minor typo. should be 't-shirt' (no capital t) since module says "This name may consist only of lowercase letters, numbers, and underscores."

Note from the Author or Editor:
Jeff further clarified this in a follow-up errata: Table 10-2: CHANGE: Class ID - T-shirt TO: Class ID - tshirt Additionally, page 359 needs the following changes: Step 8: CHANGE: admin/store/products/classes/T-Shirt/edit TO: admin/store/products/classes/tshirt/edit Step 9: CHANGE: admin/store/products/classes/T-Shirt/attributes TO: admin/store/products/classes/tshirt/attributes CHANGE: admin/store/products/classes/T-Shirt/attributes/add TO: admin/store/products/classes/tshirt/attributes/add Step 11: CHANGE: admin/store/products/classes/T-Shirt/options TO: admin/store/products/classes/tshirt/options Step 14: CHANGE: admin/store/products/classes/T-Shirt/attributes TO: admin/store/products/classes/sticker/attributes CHANGE: admin/store/products/classes/T-Shirt/attributes/add TO: admin/store/products/classes/sticker/attributes/add Step 15: CHANGE: admin/store/products/classes/T-Shirt/options TO: admin/store/products/classes/sticker/options

Minor Typo - Second box from bottom, Change 'complet' to complete'

Note from the Author or Editor:
D'oh. :( Confirmed. Thanks!

Table 10-11 is shown as 'permissions for the event content type'. I assume the word 'event' is incorrect

Note from the Author or Editor:
NOTE that this is actually on page 364. The description for table 10-11. CHANGE: Permissions for the event content type. INTO: Permissions for the store.

Missing paren at end of para: "under the theme configuration screens (see Chapter 2." n.b. this might well be changed to a specific xref to Figure 2-44.

Note from the Author or Editor:
Confirmed. How about we change this to "(see the Theme Configuration section of Chapter 2)" with a x-ref to that heading? Figure 2-44 is probably the most appropriate, but that whole section deals with this topic.

Really easy one here. in step 4. when we are putting our function in to override the way submitted value is printed out, on the line: $vars['submitted'] = t('Posted on') . should add a space after posted on inside the quotes, such as: $vars['submitted'] = t('Posted on ') . so that our text and our date don't run together. Thanks!

Note from the Author or Editor:
D'oh! You are absolutely right. :) Thanks for the report!

In the errata submissions, there's currently a HUGE entry tagged as a "Question" about Administration Menu module. I can't seem to edit that one anymore because of the way that it was tagged, but if that gets fixed in the 2nd printing, we also need to change this here to match. CHANGE: "Administration menu 6.x-1.0" TO: "Administration menu 6.x-1.1"