Using Drupal Unconfirmed Errata

Errata

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

Version	Location	Description	Submitted By
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
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
Printed	Page xviii 5th paragraph	I just took the time to markup my book with all the errata online. This is a wonderful facility, allowing my book to be FAR more error-free than technical books of the past. However, this errata has two major problems: 1) many of the issues were resolved before my "first edition" was printed, and 2) for a number of reasons, including #1, the page numbers are almost all wrong. I think readers might appreciate a table of corrections, sorted by real printed page number, with the chit-chat removed. (In one case, I marked up a suggested correction, only to read the author's reply that it wasn't an error.) If anyone would like such a list, I'll take the time to produce it. I can be reached at alastair.dallas@gmail.com.	Alastair Dallas
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
Printed	Page 65 Table 2-20	Either it was absent or I missed a previously given explanation (quite possible!) as to the significance of parent menu items parenthesised <thus>. Maybe it should be explained? It took me a while to work out what I'd done wrong? In this table we have "<Primary links>" which occurs way down the drop-down list after "Primary links". Perhaps it would be worth explaining that the former attaches the Blog(s) to the invisible top-level page menu whereas the latter loses Blogs in the bowels of administration menu items.	Iain Houston
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
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
Printed	Page 131 2nd Paragraph	The 2nd sentence is hugely misleading. It is unclear whether you mean for us edit the default settings or the Page display, and since you use the words "page display", most people are going to select the Page rather than the Defaults -- especially since Fig 3-34 shows what appears to be the Page display being edited (you have to look really carefully to notice that the Arguments the Page is using are defaults because they are italicized). In fact, if you leave the default arguments blank and enter overriding arguments on the Page settings, you don't get the desired results -- nothing actually changes. Sentence 2 should start "Add an argument to the Defaults by clicking on the (+)..." and Fig 3-34 should be changed to show that the Defaults are being edited, not the Page.	MadOverlord
Printed	Page 136 Figure 3-38	Under basic settings in Figure 3-38 it says for "Title", "Applications". I didn't see instructions to enter that anywhere. So basically it says "Title: Applications" in the book but not in the instructions.	Elijah Lynn
Printed	Page 140 Step 3	This step implies that the relationship is being added to the specific view, when in fact, because you're clicking "update default display", you're adding the relationship to the defaults. This is probably what you intend for the user to do, but you should clearly state that this is the intended and desired result. An even better way to do it is to have the user switch to the defaults and add the view directly. Quite frankly, the fact that you can destroy your defaults when editing any view by forgetting to click the override button is a human factors disaster. What were they thinking?	MadOverlord
PDF	Page 151 Product Information - 2nd paragraph	It is not a mistake by itself, it is the result of the changing conditions of the environment. I'm also reporting it as a PDF version problem, but needless to say, this affects all versions. Chapter 4 requires the Amazon module to access product information. Since August 2009, Amazon has changed is API conditions, the following fragment was taken from the Amazon module project page (http://drupal.org/project/amazon). "As of August 2009, Amazon.com requires that all access to its data use a site-specific API key. To use this module, you must sign up for an Amazon API account and request an access key. This process is free, but without it, the module won't do anything." So, this pretty much invalidates an important part of the chapter's exercise. This should be no problem to most of the users that go check the module's page early in the chapter (as I did), but those who don't do might have a hard time with it. Great book! Best regards! H	Hugo R. Gomez
Printed	Page 212 Final paragraph	'Logging in as editor and visiting Administer>Content Management>Content (admin/content/node) will show you those articles and allow you to read and publish them.' If you're using the Using Drupal sample code installation, this won't work until you have visited Administer>User Management>Users (admin/user/user), clicked 'edit' for the 'editor' role, and checked the 'editor' checkbox under 'Roles:' (you must be logged in as 'admin' to do this of course).	Michael G
Printed	Page 224 Step 10	Currently reads: 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 It's not "a good idea"; it's absolutely essential for the proper behavior of the site. Otherwise you get emails on draft creation. Change "It's also a good idea to" to "Finally," and add to the end "; if this is not done, then emails will be sent whenever a new node is created, even if it's a draft."	MadOverlord
Printed	Page 241 number 5	Step five lists file fields one should see at this stage, and suggests the order they should be placed in. Title Photo Caption Menu settings My problem is, I don't know where the "Caption" file field is coming from (its not listed in my results). As well, I have 'file attachments' in my list: Title Photo Menu Settings File Attachments Granted i'm not using the 'photo gallery' installation profile... Does this mean that in the photo gallery profile, an additional file field has been created called 'Caption'?	Anonymous
Printed	Page 242 Table 7-2	I have the Dec. 2008 edition of Using Drupal, in case the page numbers don't match. Anyway, unless I'm mistaken, in Table 7-2 the "Select a field type" should be File not Image. Image is not even a selection in the drop-down for this item. Thanks, great book!	Gary Broyhill
Printed	Page 242 Table 7-2	In Table 7-2 it shows the setting for Select a field type to be Image. However, when I did this I did not have a field type of Image to choose. What I did have was a type File which, by the way, worked just fine with a widget type of Image. Did this perhaps change after the book was published? I am running Drupal 6.13 and the most current version of the ImageField & FileField modules. Thanks.	Bill R
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
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
Printed	Page 300 Step 4	Should read: 4. Go to Administer -> Site configuration -> Languages (admin/settings/language), and click on the Multilingual system tab (admin/settings/language/i18n), where you will see... (at least, this is what you have to do if you've been a good little boy or girl and updated all your modules to the latest versions as you go along. I don't know if this is true for an un-updated installation)	MadOverlord
Printed	Page 304 Step 1	The modules are in the Multilanguage section, and are called Content type translation and String translation	MadOverlord
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
Printed	Page 307 Step 1	"Multilingual Taxonomy" now called "Taxonomy Translation"	MadOverlord
Printed	Page 309 Step 10	After completing all of these steps, the Forum words stubbornly refuse to change languages (both on the mainpage, ie: something like http://localhost:8888/ja/forum [I installed Japanese], and subtopic pages). However, when you create a new forum topic, the forum popup does change depending on the language. So "Raptors" becomes "Raputazu" (in katakana, I got lazy). This clearly indicates that the taxonomy has been translated. But when you post the topic, it gets listed, once again, under (Homu [in japanese]) >> Forums >> Types of Birds even when you are in Japanese mode. So either the instructions are wrong, or the latest versions of the Forum software have a bug (I have been updating the modules as I went along)	MadOverlord
Printed	Page 325 Step 2	In the Event Management chapter, if you are being a good sysadmin and updating modules as you go along, but get lazy and don't update the date module immediately after activating it, you set up a time bomb for youself. What happens is that later on, when you activate views, the entire site crashes with a PHP error, as follows (displayed in the logfile, not in the results from the webserver -- all you see in the browser is a blank screen, which is very disconcerting) PHP Fatal error: Cannot redeclare date_api_views_data() (previously declared in /Applications/MAMP/htdocs/sites/all/modules/contrib/date/includes/date_api.views.inc:123) in /Applications/MAMP/htdocs/sites/all/modules/contrib/date/date_api.views.inc on line 60 What I would suggest is that the first few times you discuss turning on modules, you point the user to the appendix about updating them, and emphasize that if they are going to update modules as they go along, they need to do it after they turn on any set of modules. Furthermore, in the appendix, you might want to add a troubleshooting page or two that explains the most common ways a drupal installation can get munged, how to figure out what the likely culprit is (by checking the log files), and what to do in order to try and fix it. So in the above case, the log file shows that the problem is in the date module (and indeed, updating the date module fixed the issue)	MadOverlord
Printed	Page 341 chapter 10 - preface	there is no access admin access for the ubercart, why didn't you just suply the full ubercart example as a download and install?	Anonymous
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	Jerry Kaup