Using Drupal

Errata for Using Drupal

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Safari Books Online
ch9.12
second module listed

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/

Anonymous  Nov 30, 2008 
Safari Books Online
000
3.8. Hands-On: The Views Module, Table 3-26 & Figure 3-34

Hi, I follow along with the Safari Version of your book (so I don't know the page numbers). In views: when I try to set the argument for "Jobs in the %1 Department" I don't get the options concerning the URL, that you get. I don't get the options you show in Fig 3-33 (Glossary mode / Case / Case in path / Transform...) I thought maybe it's a missing module and switched on path and pathauto and token, but nothing changed. Then I updated the core and cck, but the options don't show. When I go to the job listings I get an ugly url: http://localhost/drupal/jobs/Health%20Sciences Is this a bug or am I missing something? I am using the using_drupal_source (version 1), MAMP (the latest), MacBook Thank you Lena Doppel

Note from the Author or Editor:
Elevating to "Serious technical mistake." I've confirmed that this is the case, and the options presented don't match the screenshot/instructions. Unfortunately, it looks like these options were removed in a later release candidate of CCK for select lists (they're still there for plain text fields). There is currently nothing we can do from the source code updating side of things to solve this. It's possible we could re-work the text, but I'd rather see this bug fixed in CCK and then update the source code with a newer, fixed version of the module accordingly. We've filed a patch with the CCK maintainers at http://drupal.org/node/359661. Will keep an eye on this and update the source code as warranted.

Lena Doppel  Dec 18, 2008 
Safari Books Online
-
Figure 3-16

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.

Marieke  Mar 03, 2009 
Safari Books Online
-
Figure 3-45

Looking at figure 3-45 it shows that, after all the changes have been made, the "Fields" only contain Node:Post Date and Node:Title. However, four different items were configured in the previous stages (Node: Post Date, Node: Title, Content:Job and User:Name) and only one was removed at the end (Content: Job). According to this, the "Fields" view should contain - Node:Post Date - Node: Titel - User: Name

Marieke  Mar 05, 2009 
Safari Books Online
?
?

I just submitted an errata about the iCal icon not showing up on my Events calendar in chapter 9 and then I went to your solution, http://events.usingdrupal.com/, and you don't have the icon either. Thanks, Mark p.s. - I'm enjoying

Note from the Author or Editor:
Aha! I finally got this one sorted out. It was a combination of a bug in Calendar, us not having the cleanest source code (leftover files from an earlier version of Calendar) and listing the wrong Calendar version in the Appendix. Whew. I am updating our source code tarball and we need to make the following edits to the book text: **Page 330, Table 9-14: REMOVE the entire row for: Node: Updated date **Page 331, item #6: CHANGE: We need to add some filters so that only our published content shows in the calendar. Do this by clicking the + (plus) icon next in the Filters section and select the Node: Published and Node: Type filters. Complete the filter configuration according to Table 9-15, clicking Update for each one. INTO: We need to add a filter so that only our event content shows in the calendar. Do this by clicking the + (plus) icon in the Filters section and select the Node: Type filter. Complete the filter configuration according to Table 9-15 and click Update. ** Page 331, Table 9-15: REMOVE the entire row for: Node: Published ** Page 454, Chapter 9: CHANGE: Calendar 6.x-2.0-rc3 INTO: Calendar 6.x-2.0-rc4

Mark Nicholson  Apr 27, 2009 
Safari Books Online
Safari
Section 2.12.1, second bullet point

"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.

Anonymous  Dec 01, 2008  Feb 01, 2009
Safari Books Online
ch 2.12.1
Section 2.12.1, second last paragraph

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.

Anonymous  Dec 01, 2008  Feb 01, 2009
Safari Books Online
fig3.5
Section 3.3, Figure 3.5

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

Anonymous  Dec 02, 2008  Feb 01, 2009
Safari Books Online
section 3.4
Section 3.4, between Table 3.6 and Table 3.7, first sentence

"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."

Anonymous  Dec 02, 2008  Feb 01, 2009
Safari Books Online
Fig3.11
Fig 3.11

In the salary text field it says "50,000" Entering it gives me the error "Only numbers are allowed in Salary." so it should be "50000"

Note from the Author or Editor:
Confirmed. Good catch, thanks!

Anonymous  Dec 02, 2008  Feb 01, 2009
Safari Books Online
fig 2-57
Fig 2-57 (in Section 2.16)

In the 3rd stage ->table titled "Filtered HTML input format" -->the 3rd and 4th rows both have the line: "<script>alert('i cAn pwn U');</script><br />" Should have the script tag stripped: "alert('i cAn pwn U');<br />"

Note from the Author or Editor:
Yep, confirmed. Thanks!

p w  Dec 08, 2008  Feb 01, 2009
Printed
Page xviii
End of first paragrah under "Download Drupal 6"

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

Angela Byron
Angela Byron
 
Jan 24, 2009  Feb 01, 2009
Safari Books Online
3.7.2.4
section 3.7.2.4, last sentence

"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.

Anonymous  Dec 03, 2008  Feb 01, 2009
Printed
Page 6
Last paragraph.

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..."

Ray  Jan 27, 2009  Sep 01, 2009
Printed
Page 7
1st paragraph under heading "The Content Revolution"

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.

Ray  Jan 27, 2009  Mar 01, 2009
Printed
Page 17
2nd item from the bottom

The description below the "Path (core)" module is cut off mid-sentence. Description reads "Allows entry of friendly URLs such as http://www.example.com/about rather than" (i.e. it doesn't say rather than _what_).

Note from the Author or Editor:
Rather than.. um... bunnies? Good catch. Please replace with: "...such as http://www.example.com/about rather than http://www.example.com/node/1."

Graham Lawlor  Jan 04, 2009  Feb 01, 2009
PDF
Page 17-18
This chapter introduces the following modules:

Comment (core) module is missing from list of core modules.

Note from the Author or Editor:
On Page 17 in the list of modules, we need to add the Comment module. Final result should be: Node (core) Allows you to post content and create your own content types Comment (core) Allows users to create replies to node content. User (core) Handles...

laserled  Jul 05, 2009  Sep 01, 2009
Safari Books Online
25
Section 2.5.1, 1st paragraph

(couldn't get the page no. in the safari version) it says "But if you return to those pages, you'll see that the URL is something like http://www.example.com/about?. Wouldn't it be great if we could instead give these pages nice search engine-friendly URLs like http://www.example.com/node/1?" should be "But if you return to those pages, you'll see that the URL is something like http://www.example.com/node/1. Wouldn't it be great if we could instead give these pages nice search engine-friendly URLs like http://www.example.com/about"

Note from the Author or Editor:
Confirmed. We noticed this at QC2 but looks like it didn't get fixed in time. Page 41, para 1. Change to: (add trailing ? at end of PW's suggestion) "But if you return to those pages, you'll see that the URL is something like http://www.example.com/node/1. Wouldn't it be great if we could instead give these pages nice search engine-friendly URLs like http://www.example.com/about?"

Anonymous  Nov 30, 2008  Feb 01, 2009
Printed
Page 26
2nd paragraph, second line

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.

Lara Burton  Dec 30, 2008  Feb 01, 2009
Printed
Page 33
Between fig 2-15 and Fig2-16

Items 1 and 2 are repeated in the following way: 1 2 1 2 3

Note from the Author or Editor:
Yep, these are duplicated. The second 1 & 2 on this page should be removed. So, 1 and 2, then figure 2-15, then 3, then regular text and figure 2-16.

AbhiAtAus  Mar 26, 2009 
Printed
Page 33
Before and after Figure 2-15

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.

Will Brown  Jan 24, 2009  Mar 01, 2009
Printed
Page 33
1st paragraph - step 1

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.

Ray  Feb 01, 2009  Mar 01, 2009
Printed
Page 43
Step 3

I used Stuffit Expander 2009 on Windows 2000. When I click the Expand All button, Stuffit creates a .tar file from the .tar.gz. Then I have to Expand All again to create the uncompressed folder admin_menu from the .tar file. Two expansions instead of one. (The Extract button didn't work any better; it extracts the contained files without creating folders--you lose the folder hierarchy.) Another thing, the wording of step 3 is vague. It might lead one to believe that the extracted file--rather that the downloaded file--is of the form admin_menu-6.x-1.3.tar.gz. So given MY experience (your's may be different) a better way to state step 3 is: 3. The filename of the downloaded file will be of the form admin_menu-6.x-1.3.tar.gz. Extracting this file creates a new file of the form admin_menu-6.x-1.3.tar (it loses the gz suffix). Extracting this new file creates the uncompressed folder admin_menu and it's contents.

Note from the Author or Editor:
Hm. I'm not crazy about the idea of adding specific instructions for different tools, but I do agree that the sentence is worded awkwardly. How about this: CHANGE: Current Step 3 TO: "Once downloaded, the file name will be something like admin_menu-6.x-1.0.tar.gz. Extract this file using your tool of choice, such as WinZip or StuffIt Expander. When finished, the module's files should appear in a folder called admin_menu."

Ray  Feb 01, 2009  Mar 01, 2009
Printed
Page 44
item 10.

Would not call this an error, since I'm using a newer version than the book was written for, but on item 10. on page 44, using Drupal 6.8 and admin_menu-6.x-1.1 the default to collapse module administration page menus may have been changed. Mine did not collapse so I did not have to do step 11-13 to uncollapse.

Note from the Author or Editor:
Yeaaahh... This is one of those awkward things where the version of the module that the book was written against (1.0) *does* exhibit this behaviour but, presumably because it made no sense ;), this was taken out in 1.1 and above. So this will probably get reported as errata frequently, given that the instructions around there state to download the newest version of the module from Drupal.org. The fixing of this though requires a couple of hefty changes. :\ * Figure 2-29 needs replacing. Least invasive is probably to simply replace the bottom call-out with "The module also optionally allows all module package fieldsets to be collapsed to save space." * Page 44, step 10: CHANGE: "Immediately, you’ll see two effects of this module, as pictured in Figure 2-29. First, there is now a navigation bar across the top of the page that contains administration tasks. Second, all of the package fieldsets on the modules administration page have collapsed. Although this might be a useful feature for a seasoned Drupal website builder who knows under which package to find modules, it’s certainly not going to be very useful for people who are just learning Drupal! Let’s look for a place to shut off this functionality, without losing the useful administration bar." TO: "Immediately, you’ll see the effects of this module, as pictured in Figure 2-29. There is now a navigation bar across the top of the page that contains administration tasks." * Page 45, step 11: BEFORE: "Go to Administer (admin) and click the “By module” tab (admin/by-module) to view a list of all enabled modules and the administrative features they expose to Drupal." ADD: "Almost any module that you install will expose configuration settings that can be used to modify the way a module behaves or how your visitors can interact with it, and Administration Menu is no exception." Page 45, step 13: CHANGE: Click the “Administration menu” link (admin/settings/admin_menu) and uncheck the “Collapse fieldsets on modules page” setting, then save the form using the “Save configuration” button. TO: 'Click the “Administration menu” link (admin/settings/admin_menu) and take a look at the options offered there. Among other things, you can choose to collapse all module package fieldsets on the module administration form, which can help save space after you are familiar with the packages in which all the various modules live.' * Page 45, step 14: REMOVE step 14. I hugely apologize in advance to our wonderful production editor, Loranah. :(

Jeff Phillips  Dec 16, 2008  Feb 01, 2009
Printed
Page 63
Figure 2-39

This is a "continuity" error. Figure 2-39 shows "Story" in the list of Content Types. However, this Content Type was deleted from the tutorial web site earlier in the chapter (in Step 11 on p. 32). The only available Content Types at the point should be Blog Entry and Page.

Note from the Author or Editor:
Crap. ;) Right you are. Figure 2-39 needs to be replaced with new one (I've uploaded at http://img.skitch.com/20090223-ki4fi5t89u7bpucppisy9a198w.png, doing my best to keep the same dimensions.. thanks, Firebug!)

Anonymous  Feb 16, 2009 
Printed
Page 69
3rd paragraph

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!

Paul Venuti  Jan 21, 2009  Feb 01, 2009
Printed
Page 74
After the last paragraph (1.)

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!

steveadamo  Jan 21, 2009  Feb 01, 2009
Printed
Page 80
Second warning snippet

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.

steveadamo  Jan 21, 2009  Feb 01, 2009
Printed
Page 82
Hands-on first paragraph

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!

steveadamo  Jan 21, 2009  Feb 01, 2009
Printed
Page 83
Figure 2-57

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.

Franny  Mar 25, 2009 
Printed
Page 85
Figure 2-60 caption

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

gengel  Apr 02, 2009  Sep 01, 2009
PDF
Page 86
Table 2-22

Since it is the intention that authenticated users can upload images, the

Anonymous  Aug 13, 2009 
Printed
Page 87
The suggestion snippet

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!

steveadamo  Jan 21, 2009  Feb 01, 2009
Printed
Page 89
Summary section, second paragraph

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!

steveadamo  Jan 21, 2009  Feb 01, 2009
Printed
Page 95
End of page

The page ends with a sentence saying a list of all CCK field types is available at: http://drupal.org/project/Modules/category/88 What I am actually seeing at that URL is a list of all modules. It's the same as http://drupal.org/project/Modules/

Note from the Author or Editor:
The URL should be changed to http://drupal.org/taxonomy/term/88

gengel  Apr 08, 2009  Sep 01, 2009
Printed
Page 99-100
Last paragraph on 99.. beginning of pg 100

First off I figured this out but I thought I would let you know in case you get it a lot. Thanks for the answer on the last one. I'm just reporting to help, Generally these things are easy to get around. I was doing chapter 3: Job posting board. (On Mac OSX, MAMP) and using the install that i downloaded from the 'Using Drupal' site, when i went to turn on the parts of the CCK Package and then hit 'Save configuration' I just got a white screen. (Is this the famous white screen?) Anyhow, I updated everything to 6.8 and did it again and it worked fine. Thanks!

Note from the Author or Editor:
This is an evil, sinister, sneaky little problem. :P MAMP by default ships with a php.ini with display_errors = Off. If display_errors were set to On, what you would see when you enable both Content and FileField is a PHP fatal error: Call to undefined function content_notify(). (see http://drupal.org/node/301398) This was fixed in FileField 6.x-3.0-alpha6, so I'll be rolling a new version of the source code tonight with this instead. In terms of required text changes: Appendix C, page 451, under the "Chapter 3" heading... Appendix C, page 453, under the "Chapter 7" heading... and Appendix C, page 454, under the "Chapter 10" heading... CHANGE: FileField 6.x-3.0-alpha5 TO: FileField 6.x-3.0-alpha6

Jeff Phillips  Dec 17, 2008  Feb 01, 2009
Printed
Page 106
Paragraph following figure 3-10

"Log in as editor, password oreilly, and create a new Job piece of content..." I installed Drupal with the Chapter 3 profile, and at this point in the instructions there was no "Create content" link when logged in as editor, so as editor I could not yet create job content. I had to first log in as admin, then go to the Administer » User management » Users. There I found that the Roles column displayed a dot for the editor user and all users with surname "Faculty". What the dots signify I do not know. So I assigned the editor role to the editor user. Furthermore, I had to assign the editor role to all users with surname faculty so they would show up in the Contact field of the Create Job form (figure 3-11). After all that I was able to log in as editor and create Job content as described on page 106. Later when I re-installed Drupal, I had the same problem and the same solution. This is either a peculiar problem with my installation or an important omission.

Note from the Author or Editor:
I've confirmed this is a problem with the source code, and have asked Nate to look into it. Marking as confirmed to get no more duplicate reports, but this isn't a problem with the book's text so no changes need to be made.

Ray 1  Feb 08, 2009 
Printed
Page 109
Step 4

Perhaps this is becauing I'm using Drupal 6.9 (I think the book's example were prepared using 6.4), but the button to be clicked in Step 4 should be the "Save" button (not "Continue").

Note from the Author or Editor:
Right you are. It even shows that in the screen shot. Sorry about that! p 109, step 4, change "Continue" to "Save"

sarcanon  Feb 17, 2009  Mar 01, 2009
Printed
Page 111
2nd paragraph

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)

Anonymous  Aug 24, 2009 
Printed
Page 111

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.

Jeff Phillips  Dec 17, 2008  Feb 01, 2009
PDF
Page 111
Second Last paragraph from bottom

Unclear description: "An important thing to note here is how our node reference field (Job) appears when given a value. The default behavior is a link to the original piece of content that is referenced. Clicking on this link will take us to the Alumni Director job node." Problem: - "Node refrence" link/pulldown does not display" Using Version: Drupal 6.8 CCK 6.x-2.1 * Tried assigning default value, more content etc. * When editing in admin mode does not display even in "Display Fields" admin/content/node-type/job-application/display

Note from the Author or Editor:
Hm. Maybe we could clarify this further like: CHANGE: An important thing to note here is how our node reference field (Job) appears when given a value. The default behavior is a link to the original piece of content that is referenced. Clicking on this link will take us to the Alumni Director job node." TO: An important thing to note in this figure is how our node reference field (Job) appears when given a value. The default behavior is a link to the original piece of content that is referenced. Clicking on the Alumni Director link from this application will take us back to the Alumni Director job. There are other ways to display node reference fields as well, which can be explored in the "Display Fields" tab on the Job Application type (admin/content/node-type/application/display)."

ibandyop  Dec 19, 2008  Mar 01, 2009
Printed
Page 134-146
Images

The image at page 134 which displays the headline: "Jobs in the Athletics Department", doesn't seem to be reference anywhere. This cause the image references to be one number lower than it should for the remaining chapter.

Note from the Author or Editor:
Starting with page 131 and continuing to 144, image captions and placements are off by one. On page 131, last paragraph CHANGE: The final view screen should look as pictured in . TO: The final view screen should look as pictured in Figure 3-34. After that, all image references need to be incremented by one. The captions are all correct, though the placement of images is sometimes not close to where the reference should be. Page 131, last paragraph: CHANGE: Figure 3-34 TO: Figure 3-35 Page 133, first paragraph: CHANGE: Figure 3-35 TO: Figure 3-36 Page 134, first paragraph: CHANGE: Figure 3-36 TO: Figure 3-37 Page 136, item #7 (first sentence): CHANGE: Figure 3-38 TO: Figure 3-39 Page 137, first paragraph: CHANGE: Figure 3-38 TO: Figure 3-39 Page 137, item #2: CHANGE: Figure 3-39 TO: Figure 3-40 Page 138, item #4: CHANGE: Figure 3-40 TO: Figure 3-41 Page 139, first paragraph: CHANGE: Figure 3-41 TO: Figure 3-42 Page 139, second paragraph: CHANGE: Figure 3-42 TO: Figure 3-43 Page 140, item #3: CHANGE: Figure 3-43 TO: Figure 3-44 Page 141, first paragraph: CHANGE: Figure 3-44 TO: Figure 3-45 Page 142, item #7: CHANGE: Figure 3-45 TO: Figure 3-46 Page 143, second paragraph: CHANGE: Figure 3-46 TO: Figure 3-47 That's the end of the misnumbered image references. What would be Figure 3-48 is missing entirely however. Page 144, item #2: REMOVE: and shown in Figure 3-47, The Figure 3-48 reference and image is correct.

Jakob Svendsen  Jan 12, 2009  Feb 01, 2009
Printed
Page 137
In the callout

"Providing this kind of node-level access control requires the use of a node access module...or Organic Groups (http://drupal.org/project/og) (covered in Chapter 10). Organic Groups doesn't appear to covered at all in the book.

Note from the Author or Editor:
Sigh. :( Yes, that was a left-over from when Organic Groups /was/ covered in the book. Ressin' fressin' release cycles. :P Please remove: " (covered in Chapter 10)"

Kevin McDermott  Dec 27, 2008  Feb 01, 2009
PDF
Page 140
Upper half of figure 3-43

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

David Cortesi  Jan 31, 2009  Jun 01, 2009
Printed
Page 141
Table 3-36

"Relationship: field_job_nid" displays as "Relationship: Job"

Note from the Author or Editor:
It doesn't in the version of Views that comes with the book, but since other people might be confused about this, I've confirmed this errata as a "Question or request for clarification." No action to take to the text (currently, at least).

Dave Hirschman  Jan 28, 2009 
PDF
Page 141
Last paragraph

"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..."

David Cortesi  Jan 31, 2009  Mar 01, 2009
Printed
Page 143
1st paragraph

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

Elijah Lynn  Mar 23, 2009  Sep 01, 2009
Printed
Page 144
Table 3-38

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"

Dave Hirschman  Jan 28, 2009  Mar 01, 2009
PDF
Page 147
3rd paragraph

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

ptommy  Feb 05, 2009  Mar 01, 2009
PDF
Page 148
3rd paragraph

"Here are the modules that we referenced in this chapter: • Address module: http://drupal.org/project/address" But it's not referenced anywhere in that chapter. It also appears not to exist at all!

Note from the Author or Editor:
remove the line "Address module: http://drupal.org/project/address" from the page.

ptommy  Feb 05, 2009  Mar 01, 2009
PDF
Page 163
Table 4.7

"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)

Fernando  Dec 18, 2008  Feb 01, 2009
PDF
Page 167
Final paragraph

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.

David Cortesi  Feb 03, 2009  Mar 01, 2009
Printed
Page 168
Table 4-12

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'.

Michael G  Mar 06, 2009 
Printed
Page 173
Item 1.

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

Dave Hirschman  Jan 31, 2009  Mar 01, 2009
PDF
Page 173
Item 2., 3rd para from bottom

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.

David Cortesi  Feb 03, 2009  Mar 01, 2009
PDF
Page 176
Last paragraph

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...

David Cortesi  Feb 03, 2009  Mar 01, 2009
PDF
Page 179
summary

Another module you say you reference but I can not find the reference anywhere in the text: Subscriptions: http://drupal.org/project/subscriptions

Note from the Author or Editor:
Remove the Subscriptions line from the page.

ptommy  Feb 07, 2009  Mar 01, 2009
Printed
Page 186
Table 5-1 and Figure 5-2

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.

Jeff Phillips  Dec 20, 2008  Feb 01, 2009
Printed
Page 190
section 1.

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,"

Dave Hirschman  Feb 01, 2009  Mar 01, 2009
Printed
Page 195
3rd para

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]."

Patrick Warren  Aug 11, 2009  Sep 01, 2009
Printed
Page 198
section 2.

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

Dave Hirschman  Feb 01, 2009  Mar 01, 2009
Printed
Page 204
Table 5-5

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.

Dave Hirschman  Feb 01, 2009  Mar 01, 2009
PDF
Page 205
Step 2 & 3

Step 2 calls for setting the name and description while step 3 assumes the 'Edit view "tracker_edits"' page is up. However, that won't happen unless one first clicks Next. Recommend you add ", then click Next" to the end of step 2, after "Table 5-6"

Note from the Author or Editor:
Good call. Step 2 on page 205: CHANGE: ...enter the values shown in Table 5-6 TO: ...enter the values shown in Table 5-6, then click Next.

David Cortesi  Feb 06, 2009  Mar 01, 2009
PDF
Page 206
Step 9

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.

David Cortesi  Feb 06, 2009 
PDF
Page 212
table 6.1

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

Note from the Author or Editor:
Confirmed, thanks!

Fernando  Dec 18, 2008  Feb 01, 2009
Printed
Page 217
Item 4. in list under 'Assign Triggers' Heading. (3rd line from bottom)

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

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

Jeff Phillips  Dec 22, 2008  Feb 01, 2009
PDF
Page 217
steps 1-4

In this section you have us assign the 'notify' and 'placate' actions to the generic action "saving new post." This leads to a problem when doing step 11 on p.223 and the following paragraph on 224: 'create a story or two.' The first thing I did was log in as user and create a draft story, but was surprised to get the 'placate' message. I double-checked and the new story was indeed in draft state. The message (and presumably the email too (altho that doesn't seem to work out of a localhost server) was sent because of the generic trigger on p.217. I went to sitebuilding: Triggers and removed these generic actions; I verified that the specific workflow actions (fig. 6-11) were unaffected; and now I could save a new draft and not get a message. Don't know how best to handle this -- but the generic actions of p.217 are redundant vis-a-vis the workflow actions of p.222-4.

Note from the Author or Editor:
The following text should be added to the end of step 10, on page 222: "It's also a good idea to remove the actions we assigned on the Node Triggers page (admin/build/trigger/node). Now that actions are triggered by workflow states, we don't need the old ones."

David Cortesi  Feb 09, 2009  Mar 01, 2009
Printed
Page 220
Step 4

When we updated the Workflow module in the source code to get rid of the nasty red errors people were experiencing, it appears that the module has changed its "workflow" (ha, ha) and initially directs you to create states first before showing you the overview page. Step 3: AFTER: ...click the "Add workflow" button. ADD: The next screen prompts for a series of workflow "states." We'll return here in a moment. For now, click back to Administer > Site building > Workflow. Step 4: CHANGE: We are brought to the main workflow listing page shown in Figure 6-9, ... TO: Notice that the main workflow listing page has changed, as shown in Figure 6-9, ...

Angela Byron
Angela Byron
 
Jan 24, 2009  Feb 01, 2009
Printed
Page 222
step 10

Chapter 6, page 222 I also encountered the problem written up as errata by another user when clicking on the "actions" link: warning: Missing argument 1 for trigger_access_check() in /Users /jephilli/Sites/drupal/modules/trigger/trigger.module on line 129. This warning also shows up when I go to admin/build/trigger/node, and the tab for workflow is not there. I tried installing the latest version of workflow (v1.1) and that seemed to work alright.

Note from the Author or Editor:
Tonight I'll be releasing a new version of the source code which has Workflow module 1.1 instead, which should help prevent readers from running into this anymore. Thanks so much, Mark in SF! This affects the book text in the following way: Appendix C, page 453, paragraph 1: CHANGE: Workflow 6.x-1.0-rc1 TO: Workflow 6.x-1.1

Mark in SF  Jan 11, 2009  Feb 01, 2009
Printed
Page 222
item #7

In item #6, you are on the Workflow list screen, and then in item #7, you go to the Workflow transitions screen. However, you are not told how to navigate to that screen. I had to hunt around to find where to go.

Note from the Author or Editor:
Confirmed. Step 7: BEFORE: Fill out the workflow transitions by... ADD: The next step is identifying who is allowed to move a piece of content from one workflow state to another. Click the Edit link on the "Article publication" workflow (admin/build/workflow/edit/1) to view the workflow's transition settings.

Wonder95  Jan 23, 2009  Feb 01, 2009
Printed
Page 224
After completeion of Hands-On: Creating a Workflow

After completing the set up the workflow, and setting up the actions to be triggered, I tried creating a new story node. The "Notify Editor" and "Placate Author" actions were triggered as hoped, but the tokens (%title, %username, etc.) were not replaced. I got emails like this: user submitted a new %node_type titled "%title" for approval at Twin City Arts --- %teaser --- To review the full article and publish or delete it, visit %node_url And this message: %title has been submitted for review Just to be thorough I installed a fresh copy of D6.8, and workflow 1.1 to see if it was some weird versioning problem (or I'd just pushed the wrong button somewhere and broke the original site :P). I turned on the workflow and triggers modules and went though the same steps and got the same result: no string replacement. Hopefully the authors can clarify this?

Note from the Author or Editor:
Yay, Mark in SF, who tracked down this pesky bug: "Email & message actions do not replace %title, %username, etc. if fired from workspace defined triggers. Bottom line is it's a bug in the core that hopefully will be fixed: "As said in #4, this issue (as well as other bug reports in Drupal 6) first needs to be fixed in the Drupal 7 branch and will then be backported to Drupal 6. Only if the change is too different in Drupal 6 and 7 should we have two separate issues, otherwise Drupal 7 should get the fix first." http://drupal.org/node/253711 http://drupal.org/node/339591 Would be nice to advise your readers of this so they don't think they've done something wrong :)" I agree, so I am adding a note to the source code page on http://usingdrupal.com/source_code. But there's nothing to really fix in the book content, per se, since eventually this bug will be fixed in core and we can update the code then.

Mark in SF  Jan 11, 2009 
PDF
Page 236
Last paragraph

"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.

David Cortesi  Feb 11, 2009  Mar 01, 2009
PDF
Page 240
table 7.1

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

Fernando  Dec 18, 2008  Feb 01, 2009
Printed
Page 253-257
Various

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

Angela Byron
Angela Byron
 
Jan 24, 2009  Feb 01, 2009
Printed
Page 256
tip at bottom of page

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

Dave Hirschman  Feb 04, 2009  Mar 01, 2009
Printed
Page 260
step #5

The custom pagers for the photo gallery in Chapter 7 do not work as described. Instead of paging through the photos in the one term, they page through all photos regardless of term. This is because the custom pager refers to the gallery view and uses the Taxonomy: Term ID argument, but the default view doesn't have it (it's added in the page view in #5 on page 260). Once the "Taxonomy: Term ID" argument is added to the defaults for the view, the pager works as it should.

Note from the Author or Editor:
Hey! NICE debugging! Thanks! I talked with Nate about this and he said the way to fix this is: On Page 260: ADD The first sentence of Step #4 to the beginning of Step #5 ("To display the photos in a particular order...") REMOVE step #4. --- Extra added side-note that O'Reilly people may ignore. :D Omitting this step will plop the argument into the default display so that it doesn't exhibit this problem. Arguments not working with a non-default display is a bug in Custom Pagers (http://drupal.org/node/309831, if you're keen to jump in there.)

Wonder95  Dec 31, 2008  Feb 01, 2009
PDF
Page 263
Caption 7-29

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."

David Cortesi  Feb 13, 2009  Mar 01, 2009
Printed
Page 266
Step 1.

The instructions indicate to enable both Custom Pagers and Token, however Token apparently needed to be installed in a previous exercise regarding the enabling of Imagecache. (Enabling token was *not* in those instructions, however Drupal enabled it with Imagecache anyway.)

Note from the Author or Editor:
Actually, it looks like ImageField was the one requiring this. The newer version on Drupal.org no longer does, but it doesn't hurt anything to enable it early. Page 239, step 1: UNDER: - Core - optional page * Taxonomy ADD: - Other package * Token (this should be indented a level, like "Taxonomy" is) Page 266, step 1: REMOVE: * Token

Brian Beam  Jan 19, 2009  Feb 01, 2009
Printed
Page 284
Top of Page, first paragraph after heading.

Seem to be some letters or words missing from the first sentence of page 284. Following the heading "Hands-On: Translatable Content" the text begins: "an configure multilingual support for each content type... etc." Words or letters presumed missing at the beginning of this sentence. Thanks! -j-

Note from the Author or Editor:
What, you mean that's not abundantly clear? ;) Let's go with: CHANGE: an configure multilingual support... TO: Now, we can configure multilingual support...

Jeff Phillips  Dec 25, 2008  Feb 01, 2009
PDF
Page 323
Page bottom, under "Attendance Tracking"

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

Alf Jørgen Bråtane  Jan 11, 2009  Feb 01, 2009
Printed
Page 357
Table 10-2

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

Jeff Phillips  Jan 09, 2009  Feb 01, 2009
Printed
Page 365
Figure 10-21

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

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

Jeff Phillips  Jan 09, 2009  Feb 01, 2009
Printed
Page 366
top

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.

m.paul  Aug 08, 2009  Sep 01, 2009
PDF
Page 382
First para under ".info Files"

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.

David Cortesi  Feb 16, 2009 
Printed
Page 395
4ths line (after step 4)

If the users browser is caching CSS files, the dotted borders will not appear until the browser reloads the altered CSS file. On Firefox this can be accomplished with a control-F5. I believe more advanced options are available to serious themer.

Note from the Author or Editor:
I agree that this is a good thing to point out to readers. After the sentence, "Your page will now appear with dashed lines around the nodes, as shown in Figure 11-8." could we please add "If it does not, try force-refreshing your browser, typically by holding down the Shift key on the keyboard while pressing the Reload button in the browser's toolbar." (I believe this is pretty standard across browsers/platforms, unlike Ctrl+F5 which doesn't seem to work on a mac)

Mark  Jan 20, 2009  Feb 01, 2009
Printed
Page 406
Step 1

Step 1 instructions state: "Find the file at modules/comments/comment-wrapper.tpl.php and copy it into our theme directory at sites/all/themes/custom/newmarine." No such directory exists - "sites/all/themes/custom/newmarine" Please advise

Note from the Author or Editor:
sites/all/themes/custom/newmarine should be sites/all/themes/newmarine

Jerry Kaup  Nov 23, 2009 
Printed
Page 409
item 4. in steps for 'Overriding a template variable)

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!

Jeff Phillips  Jan 19, 2009  Feb 01, 2009
Printed
Page 451
Under "Chapter 2" heading

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"

Angela Byron
Angela Byron
 
Jan 15, 2009  Feb 01, 2009