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.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.


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



Version Location Description Submitted By Date Submitted
Printed Page 259
Bullet point 1

Text reads: "Go to at Administer -> Site building -> Modules (admin/build/modules) and enable the following:" The "at" shouldn't be there.

None  Sep 04, 2011 
Printed Page 116
2nd paragraph (above trap icon)

"Views provides many exciting options to easily configure the display of your content. The settings for EACH view display can be configured all at once using the Defaults tab, or EACH display can have its own settings that override the vie defaults." Emphasis mine. Should the first "each" be "every"? As in: "Views provides many exciting options to easily configure the display of your content. The settings for every view display can be configured all at once using the Defaults tab, or each display can have its own settings that override the vie defaults."

None  Sep 03, 2011 
Printed Page 104
9.

The text as it currently reads is a non sequitur: "Leaving this setting unchecked will help reduce the likelihood that she is spammed by people applying for multiple jobs at once. This narrows down the list of potential users that can be selected." The setting being referenced has no effect on the selection list. The second sentence above is in the wrong place. It belongs after the first sentence in the same bulleted section.

None  Sep 03, 2011 
Printed Page 103
Figure 3-9

In the printed edition I have, the figures (images, screenshots, etc.) are printed with such a low DPI as to frequently be unreadable. The screenshot portion of Figure 3-9 (page 103) is almost *completely* unreadable. And the descriptive text to the right of the screenshot looks like it was printed on a dot-matrix printer whose ribbon needed replacing. :) (On the copyright page, my book lists [2011-02-04] to the right of the ISBN. Maybe that's the date of the printing.)

None  Sep 02, 2011 
Printed Page 95
Last sentence

The confirmed errata lists: "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" http://drupal.org/taxonomy/term/88 does not list all CCK field types. It lists "CCK (Content Construction Kit) related modules and plug-ins.". It's also unclear from the text why a link to "a full list of available CCK field types" is necessary, when a few sentences prior the text says, "The field types included in CCK 'core' are displayed in Table 3-1." Are we to assume that the (broken) link is supposed to go to a list of all field types available in both CCK "core" and contributed modules?

None  Sep 02, 2011 
Printed Page 49
Figure 2-32

Part of chapter 2 involved creating new user roles, users, and assigning permissions to those roles. Figure 2-32 *almost* exactly matches the permissions that we are actually supposed to set for those new user roles. The only difference is that the figure has the permission "use PHP for block visibility" check-marked whereas p53 says it's not to be checked. While the text doesn't say that the figure illustrates how we're supposed to configure the permissions[1], it would be nice for them to match, especially since they're so close already. [1] Beyond p52: "This screen, as seen earlier in Figure 2-32, is massive, and there's a lot to do here."

None  Sep 02, 2011 
Printed Page 47
First footprints note

The first sentence of the note reads: "All roles apart from 'anonymous user' receive the permissions of 'authenticated user' plus any other ROLES they're assigned." Emphasis mine. Since roles are assigned permissions and not other roles, I believe the second "roles" should be "permissions": "All roles apart from 'anonymous user' receive the permissions of 'authenticated user' plus any other permissions they're assigned."

None  Sep 02, 2011 
Printed Page 177
After clicking the Save button in step 4, and after applying the fix to the database schema that was necessary for me to get past the problem I reported in my previous submisison.

I'm running into two problems working through Chapter 4 of the O'Reilly book "Using Drupal". I'll submit each in a separate problem report. This is Problem #2. Let me start by providing relevant version information: "Using Drupal" book: The copyright page identifies it as Copyright 2009, Printing History: December 2008: First Edition. Drupal installation: For the exercises, I've installed using_drupal_source-2009-08-22_0.zip from http://usingdrupal.com/source_code. In order to make sure that the versions of Drupal core and the modules are the same as what existed when the book was written, at admin/build/modules I've made sure Core - optional>Update status is NOT enabled. Operating system: Windows XP, SP3 PHP: 5.2.9-2 Apache: 2.0.58 MySQL: 5.0.23 Problem 2: p. 177, Configuring CSS Injector To make sure I didn't have any typos in my CSS, I copied it from assets/assets/ch04-reviews/amazon.css unpacked from http://usingdrupal.com/sites/usingdrupal.com/files/using_drupal_source-2009-08-22_0.zip. Nevertheless, the result after inserting the CSS rule did not look like Figure 4-18 at the top of page 176. The Rating box was fixed up and appeared at the top right, but the information from Amazon and the text of the review was below it instead of floating around it. Since O'Reilly's Errata-submission page doesn't allow me to upload attachments, I've uploaded to my own webserver an image of what I'm seeing in my browser. Please take a look at the image at http://www.arlsoft.com/problem_reports/UsingDrupal-Ch4-CssInjector-FloatDoesntWork.gif to see what I'm seeing.

None  Apr 07, 2011 
Printed Page 177
After clicking the Save button in step 4.

I'm running into two problems working through Chapter 4 of the O'Reilly book "Using Drupal". I'll submit each in a separate problem report. This is Problem #1. Let me start by providing relevant version information: "Using Drupal" book: The copyright page identifies it as Copyright 2009, Printing History: December 2008: First Edition. Drupal installation: For the exercises, I've installed using_drupal_source-2009-08-22_0.zip from http://usingdrupal.com/source_code. In order to make sure that the versions of Drupal core and the modules are the same as what existed when the book was written, at admin/build/modules I've made sure Core - optional>Update status is NOT enabled. Operating system: Windows XP, SP3 PHP: 5.2.9-2 Apache: 2.0.58 MySQL: 5.0.23 Problem 1: p. 177, Configuring CSS Injector After I click the "Save" button in step 4, the next page reports an error on a pink background: user warning: Field 'file_path' doesn't have a default value query: INSERT INTO css_injector_rule (title, rule_type, rule_conditions, media, preprocess) VALUES ('Floating Amazon fields', 0, '', 'all', 1) in D:\Program Files\Apache Group\Apache2\htdocs\drupal_ch04c\includes\common.inc on line 3318. But below that on a green background it claims: Your CSS injection rule was saved. And below that, under the headers: Headers: Title File path Actions it shows the text, "No CSS injection rules have been set up yet." followed by a link labeled "Create a new rule." Due to this conflicting information, I ran some MySQL queries. SELECT COUNT(*) FROM css_injector_rule; reported: +----------+ | COUNT(*) | +----------+ | 0 | +----------+ which agrees with the error "No CSS injection rules have been set up yet." So it appears that the error on the INSERT was real, and nothing got inserted into css_injector_rule. I then ran: DESCRIBE css_injector_rule; which reported: +-----------------+------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-----------------+------------------+------+-----+---------+----------------+ | crid | int(10) unsigned | NO | PRI | NULL | auto_increment | | title | varchar(255) | NO | | | | | rule_type | int(10) unsigned | NO | | 0 | | | rule_conditions | text | NO | | | | | media | varchar(255) | NO | | | | | preprocess | int(10) unsigned | NO | | 0 | | | file_path | varchar(255) | NO | | | | +-----------------+------------------+------+-----+---------+----------------+ so it really does look like the error "Field 'file_path' doesn't have a default value" is correct. I fixed this by giving file_path a default value: ALTER TABLE css_injector_rule ALTER COLUMN file_path SET DEFAULT ""; At this point, I again created a rule at admin/settings/css_injector/add, and when I clicked "Save" it returned me to admin/settings/css_injector. This time it showed no errors and the table at the bottom showed the following rule: Title: Floating Amazon fields File path: sites/default/files/css_injector_1.css I don't know whether things would work better if I were to update some module to a later version, but the code you've distributed that's supposed to work with this book doesn't work.

None  Apr 07, 2011 
Printed Page 159
2

The amazon module that comes with the source code is no longer usable. Amazon requires two separate API keys to work, one public and one secret. The source code should be redistributed with the updated module.

Michael Kadin  Dec 29, 2010 
Printed Page 255
step 2 at bottom of page

The button is not titled "Create New Preset" button in 6.19. There it says "Save Preset".

Ken Wilson  Oct 22, 2010 
Printed Page 332
Image

According to the errata resolution (regarding missing the 'iCal' link on the calendar page : ----------------------------------------------------------------- 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 ------------------------------------------------------------------- I downloaded the tarball recently (a month or so ago) and it has 6.x-2.0-rc2! (not even rc3). I also am using the second edition. I tried to go get a newer calendar module, and the only one available is calendar-6.x-2.2, and when I try that (after updating to it) I get the following nasty error: Fatal error: Call to undefined function date_real_url() in C:\wamp\www\ch09\sites\all\modules\calendar\theme\theme.inc on line 513 Help! Mike

Mike G  Oct 10, 2010 
Printed Page 328
Step 1

I am following along using Drupal 6.19 and, when I arrive at this step, enabling the Views module crashes the site in its entirety. This makes it impossible for me to follow this chapter any further. To help in determining possible sources of the problem going forward, here is the current state of the modules in my Drupal installation. - Content 6.x-2.8 - Text 6.x-2.8 - Date 6.x-2.6 - Date API 6.x-2.6 - Date Popup 6.x-2.6 (Note: Required jQuery UI 6.x-1.4, wrapping jquery-ui 1.8.2) - Date Timezone 6.x-2.6 - Advanced Help 6.x-1.2 Version of Views and Views UI I am attempting to enable are 6.x-2.11 Also of note, I have been upgrading all the modules as they are first encountered and followed the chapter order religiously. This is the first problem encounter with the Views and Views UI modules. Are there possibly significant changes in the Date API, particularly considering the requirement for jQuery UI, causing a breakage?

Ken Wilson  Oct 07, 2010 
Printed Page 82
Hands-On, item 4

Similar to the unconfirmed errata regarding the renaming of FCKeditor to CKeditor: - if you download the latest version (version 3.3.1 as of this writing) Drupal 6 would no longer function correctly because all the filenames have been changed to remove the 'f'. Hence, not only is the path cited in item 4 changed to: /sites/all/modules/fckeditor/fckeditor/ckeditor.php (a minor issue) But clicking on Administer > Site Configuration > FCKeditor results in an error because it cannot find the file under the name it expects. - It is therefore essential to download what is now the older 2.x version - currently 2.6.6

Therese  Jun 10, 2010 
Printed Page 143
Figure 3-45

The "Fields" area shows only two fields for the Job Tab display. There are four fields in the Defaults and Page views. This figure is referred to from the first paragraph of page 141 before we eliminate the node reference to the Job in step 6 in the last paragraph. Since we never remove "User: Name Applicant," this, and "Content: Job Title (link)" are missing from figure 3-45.

Mark Eackloff  Jun 02, 2010 
Printed Page 139
Last paragraph (between Figures 3-41 and 3-42), second sentence.

This sentence could be easier to read if broken into two sentences. "Pulling up lists of job applications is simple to do," is a complete thought and should stand as it's own sentence terminated with a period, not a comma. The next part of the sentence is awkward. Instead of "we want to use a piece of data from the Job type that the tab is being shown on," should be replaced with "we want to use a piece of data related to the Job type shown." Or better yet, "we want to use the node ID related to the Job type shown."

Mark Eackloff  May 26, 2010 
Printed Page 121
Figure 3-23

Pages 100 through 108 create a job instance for Alumni Director in the Administion department. However in Figure 3-23, "Jobs in the Administration Department," the job seems to have disappeared. Yet there is nothing between page 108 and 121 where we delete that job instance.

Mark Eackloff  May 23, 2010 
Printed Page 131
Table 3-26

The Table showing the Argument settings says to use... Content: Text:Department ..but when using this option, it doesn't have the the settings for "Case" and "Case in path". I found these settings in a different Argument type "Node:Title" and it seems to work okay, but I'm not positive that it's the best solution.

Thomas  May 20, 2010 
Printed Page 159
page

Insert the product id field as instructed. When creating content getting errors. It seems like it doesn't find the look up item, but it is indeed a real amazon id: •warning: Invalid argument supplied for foreach() in /home/skywalkr2/cm-freedom.com/drupal_4/sites/all/modules/contrib/amazon/amazon.module on line 269. •Amazon Product ID : No Amazon product with the ID B000I21K18 could be located. •warning: Invalid argument supplied for foreach() in /home/skywalkr2/cm-freedom.com/drupal_4/sites/all/modules/contrib/amazon/amazon.module on line 269.

Chris  May 05, 2010 
Printed Page 134
Figure 3-36

Figure 3-36 should appear at the top of the page, _before_ the heading 'Job Applications View'. As it is, it's in a confusing position because the reader can be led into the mistake of assuming that this figure relates to the Job Applications View somehow (rather than Figure 3-37).

Alan Rew  Apr 04, 2010 
Printed Page 119
'Building Efficient Views' box

[9/09] printing, BTW. Terminology. Second paragraph in the box uses the phrase "Fields display type". Fields is not a display type. The (default) display types are Attachment, Block, Feed and Page. Maybe "Fields selection criteria" or "Fields specification" would be more appropriate. Accurate terminology is vital, especially for something relatively complex like Views, to avoid confusing somebody who's learning Drupal for the first time.

Alan Rew  Mar 31, 2010 
Printed Page 95
First sentence under the heading 'Fields'

Under the heading 'Fields' on page 95 (in [9/09] printing) the first sentence says "Functionally, CCK is set up into two end-user pieces." Firstly, I think it makes more sense to say "split up into" rather than "set up into". Secondly, the following pages go on to describe _three_ separate pieces of functionality (Fields, Widgets and Formatters) so it would be more helpful to say "three end-user pieces", and also to list them at that point, for example "Functionally, CCK is split up into three end-user pieces: fields, widgets and formatters."

Alan Rew  Mar 24, 2010 
Printed Page 96
Box: 'CCK or Taxonomy?', last bullet point, first sentence

The page number 96 refers to the [9/09] printing, by the way. A missing comma makes the sentence hard to understand on the first pass, especially as there is a line break after the phrase 'content type'. In the first sentence in the last bullet point "A general rule of thumb is that if you can remove the field and the content type still makes sense, ..." There should be a comma after the word 'field', so the sentence reads "A general rule of thumb is that if you can remove the field, and the content type still makes sense, ..." which stops the reader from temporarily thinking that the author means 'remove the field and the content type', before he reads past the line break and discovers that's not what the author meant. Hope that makes sense :-)

Alan Rew  Mar 24, 2010 
PDF Page 285
Language Switcher Step 2

reads: 2. Drag the block into the “Rightt sidebar” region, and then click the “Save blocks” button. Extra "t" in there, should be 2. Drag the block into the “Right sidebar” region, and then click the “Save blocks” button.

Shai Perednik  Mar 23, 2010 
PDF Page 284
2nd Paragraph

Under "Hands on: configuring Locale Features" > "Language Negotiation Settings". The sentence reads: "We are going to use the “Path prefix with language” fallback rather than the “Path prefix only” option,..." It should be: "We are going to use the “Path prefix with language fallback" rather than the “Path prefix only” option,..." as that's the full term used in the drupal config admin/settings/language/configure

Shai Perednik  Mar 23, 2010 
PDF Page 275
4th paragraph

Under Locale > Translations the second to last paragraph ends with this sentence. "The coverage for module translations is not very thorough, and as modules can be updated much more frequently than Drupal’s core translations, can become outdated quickly." I'm no grammar major but I think that last comma is out of place and should read: The coverage for module translations is not very thorough, and as modules can be updated much more frequently than Drupal’s core, translations can become outdated quickly."

Shai Perednik  Mar 23, 2010 
Printed Page 136-144
Figures 3-38, 3-40, 3-41, 3-45, 3-46

The Title field is shown inconsistently in the figures. The figure on the bottom of p.136 (should be labelled "Figure 3-38") shows the default Title for the "applications" view as having been set to "Applications" (non-italics) but this step was not included in the text. Table 3-32 then instructs the reader to perform the step for the "Page" display but Figure 3-40 shows no Title at all - default or overridden - even though figure displays the "finished" result. "Applications" is back however in Figure 3-41 (p.139 top) as the default (italicized) Title for the "Page" display, and in Figures 3-45 (p.143) and 3-46 (p.144) as the default Title for the "Job tab" display. (BTW, the list of Fields - and showing them in italics - in Figure 3-45 appears wrong for the "Job tab".) It seems more logical that Figures 3-38, 3-41, 3-45, and 3-46 are correct about the Title field, and that it's the text that should be corrected. It also appears that the first paragraph on p.143 is referring to Figure 3-42 (p.139 bottom) instead of Figure 3-41 (p.139 top). Figure 3-48 (p.146 bottom) gets Title right! If you're seeking perfection: Table 3-38 shows that Title with a lowercase "a".

pbyhistorian  Mar 01, 2010 
Printed Page 137
1st sentence

On the "Confirmed errata" page, there is a correction for pp.131-146 where references to Figures are off by one. The correction itself contains an error: 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... The surrounding text on these two pages suggest different Figures - that one of these two corrections is wrong. My newer printed edition contains all of the corrections in this entry, except that p.136 item #7 says "Figure 3-38" rather than "Figure 3-39". It seems that the error in the errata regarding p.136 was corrected for later printings but not corrected on the errata page. Those with older printings will be mislead by the errata page.

pbyhistorian  Feb 25, 2010 
Printed Page 163
Last line

First edition. "Rating" on the last line, and "Pros" and "Cons" on the first lines of page 164 should be indented.

RV  Jan 14, 2010 
Printed Page 163
Taable 4-7

First edition. "Allow user to clear view" should be: "Allow user to clear value", at least for Drupal 6.15

RV  Jan 14, 2010 
Printed Page 135
#5

First Edition. #5, first line: (...) and add the Post date sort should be replaced by: and assign Sort order: Descending to the node Post date.

RV  Jan 12, 2010 
Printed Page 135
Table 3-28

First Edition. In Table 3-28 the instruction "Title: Applications" (see Figure 3-38) is lacking.

RV  Jan 12, 2010 
Printed Page 91
2nd paragaph, last line

First edition. (...) browsing though available jobs should be: browsing through available jobs.

RV  Jan 12, 2010 
Printed Page 126
Figure 3-28

First Edition. Figure 3-27 shows the Live preview as if page 125 did not contain #6: Click the rearrange icon... (etc.).

RV  Jan 12, 2010 
Printed Page 104
#9

In the First Edition, page 104, there is talk about the "editor" role (to which faculty members are assigned). The assignment has not taken place (yet). What should be told, is that readers of the book must assign the roles themselves via Administer=>User management=>Roles, the same way as stated for additional users below on the same page.

RV  Jan 12, 2010 
PDF Page 410
Last sentence of second paragraph

At the bottom of page 410, it says "You can also find more information on theme functions in the Drupal handbook at http://drupal.org/node/11811." This page deals with Drupal 5, not drupal 6. Furthermore, it refers to _phptemplate_callback, for which I cannot find any documentation for any version after 5. Is this the correct link? Wouldn't a page like http://drupal.org/node/341628 be more appropriate?

Anonymous  Jan 08, 2010 
Printed Page 131-132
3rd paragraph, pg131

Text says "Here, we are asking it to display a list of department names in ascending order." Table 3-26 also shows this choice. On the screen shot on page 132 the choice "Summary, sorted descending" is ticked off. I did not get either of the Case options, or the "Transform spaces to dashes option in URL," option when I did this part. I'm using updated versions of Drupal as well as all the modules so it may be that there have been changes since the book came out. Drupal Ver. 6.15 Views Module Ver. 6.2.8 Functionally everything works and it even lists my own job listings that I added!

mike-at-orielly  Jan 07, 2010 
Printed Page 169
Figure 4-13

Under Fields is (field_product_id_asin)Amazon: List price Price then (field_product_id_asin)Amazon: Title Title. The order should be reversed.

Douglas Belcher  Jan 03, 2010 
Printed Page 176
Top

The image at the top of page 176 shows comments and user ratings. However, the theme selected does not give the option of creating comments. The only way to do this is to manually enter the url http://example.com/comment/reply/<nodenum>, which, of course, nobody would do. It would be better to select a theme that provides the <add comment> link at the bottom of each review to allow users to vote and add comments, which is what this site is all about. The problem is in sites/all/themes/contrib/nitobe/node.tpl.php. From the comments there, it looks like the omission might have been unintentional. To fix the problem, youcan replace this line in node.tpl.php: <div class="links"><?php /* print_r($node->links); //print $links; // @TODO delete this now? */?></div> with this line: <div class="links"><?php print $links; ?> </div>

Anonymous  Dec 30, 2009 
Printed Page 214
last paragraph

The text says that logging in as "editor" will allow you to see the administer menu option. I tried this and didn't see the menu item. I installed drupal using the install script from the source code, and after a little digging discovered that the user "editor" was not assigned the editor role by default.

chris  Dec 19, 2009 
Printed Page 82-84
Hands-On Section

The makers of FCKeditor have updated and renamed their product and refreshed their site. The current version of the software is called CKeditor and the new site is ckeditor.com. Previous versions of the software are still available on the site, but you may want to update the text and screenshots in future editions in order to reflect the new changes to the product.

chris  Dec 15, 2009 
Printed Page 139
Figure 3-41

Figure 3-41 shows the following under Basic Settings... ... Access: Editor Header: None ... My screen, based on working through the example using the version of Drupal produced for the book, shows an extra line between the two above: Exposed form in block: No It's possible that I have accidentally done something which results in this line displaying, but I can't find anything.

Anonymous  Dec 02, 2009 
Printed Page 137
Point 2.

Section 2. says: "Now we'll override our first setting ... then use the settings from Table 3-32" The settings in the table actually spefiy overriding *two* settings: not just the Access, as described, but also the Title. Suggest text changed to also mention overriding Title.

Anonymous  Nov 25, 2009 
Printed Page 121
Table 3-18

Table 3-18 Permissions for Views module shows views_ui module. Though I have views_ui enabled, I am not seeing permission on the corresponding screen. Is this a version difference? I am using 6.x 2.7

David Walton  Nov 10, 2009 
Printed Page 88
Second Paragraph

The text reads Mike and Jeanne won't know how to insert a URL into for an image, instead the administrator should make it possible for them to "browse, upload, and insert images from their computers." However, in following the provided instructions, this functionality is not established. Instead, it appears that only the profile names and default image sizes are updated while the action originally suggested remains unresolved.

Aaron Miller  Oct 24, 2009 
Printed Page 260
Step 4 -- table 7-13

In table 7-13, it should be Content: Photo (field_photo) instead of Content: Image: Image(field_photo) PS -- thanks for a great book. I have put two of your projects online already and they work great.

Gary Broyhill  Oct 09, 2009 
Printed Page 304
Step 3

You state that one of the results is not translated, but you don't say *how* to recognize this is the case (untranslated strings have the language code displayed with a strikethrough). It is almost impossible to see that this is the case by looking at Fig 8-31 as the resolution isn't high enough (and it's a lousy interface metaphor in any case, not that this is your fault.

MadOverlord  Oct 05, 2009 
Printed Page 265
Step 5

A step is missing here. In order to get the latest_photos block to display thumbnails instead of a gallery summary, you need to also delete the Arguments settings. You will note that figure 7-29 shows the arguments have been deleted, but there is no step that instructs the reader to actually delete it!

MadOverlord  Oct 05, 2009 
Printed Page xviii
Downloading installation instructions

One problem with the downloading instructions is that they are incomplete -- they do not take into account the very real possibility (certainty, at this point) that the using_drupal_source distribution is out of date. This means that as soon as someone starts using one of the example profiles, they're going to get hit with dire warnings that they need to update Drupal. And if they do so, and follow the instructions on how to do that (side note, the Drupal update process is a disaster waiting to happen!), they are going to nuke the profiles, and be stuck wondering what the hell happened to them. This can be avoided if an extra step is added between steps 2 and 3, as follows: 2a. If you have updated your Drupal installation to a more recent version, copy any missing files and folders from the using_drupal_source profiles folder into your drupal profiles folder.

MadOverlord  Sep 26, 2009 
Safari Books Online ?
in section 4.2.1

The step for creating the group field reads as following in the online addition: Because we want to group several of the fields in this content type together (the Pros and Cons, ratings, and so on), we'll first create a Field group to organize them. Under "New group," create a new group with a label of Section 4.13" and a group name of "summary" and save the form. I'm assuming there's a typo there and that the label is not supposed to be named "Section 4.13". I'm enjoying reading the book. Thanks, Mark

Mark Nicholson  Apr 17, 2009