Errata

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
PDF
Page 163
Changing this is easy: ... [step] 1. [at the top of the page]

Next to the ?medium? style, click ?edit.?
should be . . .
Next to the ?large? style, click ?edit.?

Note from the Author or Editor:
This is already correct in the PDF I have. It should be confirmed and corrected if not in the current customer version.

 Richard Pilkington  Apr 06, 2014  May 08, 2014
ePub
Page ebook
ebook

Chapter 4 promised to be a chapter about building an on-line photo gallery. It's about building a record review site. Nothing to do with a gallery.

Note from the Author or Editor:
In the Preface, page xvi of the book and PDF, the summary of Chapter 4 should be updated to say:

Chapter 4, Media Management
This chapter helps you build a record review site, with images and videos, using core?s Image module along with several contributed media modules.

 stu ducklow  Apr 14, 2013  May 08, 2014
PDF
Page 402
Below headline "Taking it further"

It is stated that "In this chapter, we have covered the basics of setting up an online storefront and shopping cart using the Ubercart package of drupal" when the "Commerce Module" was actually used for this task.

Note from the Author or Editor:
Update the text to say:

...an online storefront and shopping cart using the Drupal Commerce package for Drupal. ...

 M. Johansen  Nov 02, 2012  May 08, 2014
PDF
Page 343
step 3

"Multilingual package" should be "Multilingual - Internationalization"

Note from the Author or Editor:
This change is correct.

 Eduardo Cavazos  Jul 06, 2012  May 08, 2014
PDF
Page 337
step 1

"Multilingual package" should be "Multilingual - Internationalization"

Note from the Author or Editor:
This needs to be changed as indicated

 Eduardo Cavazos  Jul 05, 2012  May 08, 2014
PDF
Page 330
Table 8-3

The field 'Menu link' should be 'Menu link title'.

 Eduardo Cavazos  Jul 05, 2012  May 08, 2014
PDF
Page 324
step 6

There is an extraneous period in this sentence after "module":

The list will update as you type, and it should
bring up the string ?Translate field properties,? which is provided by Internation-alization?s ?Field translation? module. as its description.

 Eduardo Cavazos  Jul 05, 2012  May 08, 2014
PDF
Page 262
first bullet list

"GMap" should be "OpenLayers".

GMap is not mentioned in the chapter, but OpenLayers is. (Could be a remnant from a previous version as GMap is outdated.)

Note from the Author or Editor:
- Remove GMap from the list.
- Between Location and Signup, add a new list item:
OpenLayers (http://drupal.org/project/openlayers)

 Eduardo Cavazos  Jul 04, 2012  May 08, 2014
PDF
Page 244
step 4

Step 4 instructs the user to click "Save field settings". However, the user is also told to do this in step 3.

Note from the Author or Editor:
Update text in Step 4:

4. On the second settings form we can use most of the defaults. Change the field values as shown in Table 6-8.

 Eduardo Cavazos  Jul 04, 2012  May 08, 2014
PDF
Page source code
install.php

On the "Select an installation profile" step of the 'install.php' script, the description for 'Chapter 6: Event management' is:

"Select this profile to install a product review site.".

It should be:

"Select this profile to install an event management site."

Note from the Author or Editor:
Fixed this in the source code. It will be rolled in with other changes in the next release.

 Eduardo Cavazos  Jul 03, 2012  May 08, 2014
PDF
Page 219
step 1

"Site building" -> Modules

should just be:

Modules

 Eduardo Cavazos  Jul 03, 2012  May 08, 2014
PDF
Page 184-185
step 3, step 4, step 5

With the currently available book source code, CKEditor is already installed. Steps 3, 4, and 5 are unnecessary.

Note from the Author or Editor:
Update the text for step 3:

...mix and match editors per text format. For our site, we're going to keep things simple and just use one editor everywhere. If you are using the source code, you can skip to step 6 now, since you already have CKEditor downloaded. If you are not using the source code provided with the book, then you will need to download CKEditor yourself, by clicking the Download link next to CKEditor.

Eduardo Cavazos  Jul 02, 2012  May 08, 2014
PDF
Page 183
step 2

"Wysiwig" should be "Wysiwyg"

 Eduardo Cavazos  Jul 02, 2012  May 08, 2014
PDF
Page 163
step 2

"Add effect" should be "Update effect"

 Eduardo Cavazos  Jul 01, 2012  May 08, 2014
PDF
Page 161
step 4

After pressing 'delete', a second confirmation screen appears, during which another 'Delete' button must be pressed to continue. Step 4 should mention this.

Note from the Author or Editor:
On page 161, step 4, edit the following:

... by clicking "delete" next to that effect, and then the Delete button on the next screen. Watch how the preview image changes in response.

 Eduardo Cavazos  Jul 01, 2012  May 08, 2014
PDF
Page 148
first bullet list

The "Chaos Tools" module is mentioned on page 124 but is not shown in the list.

Note from the Author or Editor:
Add an item to the unordered list, between Automatic Nodetitle and Display Suite, for:

Chaos Tools (http://drupal.org/project/ctools)

 Eduardo Cavazos  Jul 01, 2012  May 08, 2014
PDF
Page 136
1st paragraph

If you need more fields then the uid add the content: author relationship.

"then" should be "than"

 Eduardo Cavazos  Jul 01, 2012  May 08, 2014
PDF
Page 101
step 2

"managed fields" should be "manage fields"

 Eduardo Cavazos  Jun 30, 2012  May 08, 2014
PDF
Page 77
step 6

The sentence:

Return to the Appearance settings page by going to the administrative toolbar and clicking Appearance->Settings, and click the Settings link next to the Bartik theme (admin/appearance/settings/bartik).

should read:


Return to the Appearance page by going to the administrative toolbar and clicking Appearance, and click the Settings link next to the Bartik theme (admin/appearance/settings/bartik).

Note from the Author or Editor:
Update should be made as stated.

 Eduardo Cavazos  Jun 30, 2012  May 08, 2014
PDF
Page 70
step 4

In the administrative toolbar, go to Administer -> Structure -> Menus -> Navigation -> ?List links?

Should be:

In the administrative toolbar, go to Structure -> Menus -> Navigation -> ?list links?

I.e. there is no "Administer" button. Also "List" should be lowercase.

Note from the Author or Editor:
Yep, this should be updated as stated.

 Eduardo Cavazos  Jun 30, 2012  May 08, 2014
PDF
Page 39
step 2

"Enter the article?s Title, Body, and other settings provided in Table 2-1"

That should be "Table 2-2".

Note from the Author or Editor:
Yep. This needs to updated exactly as reported.

 Eduardo Cavazos  Jun 29, 2012  May 08, 2014
PDF
Page 23
Figure 2-3

"Close overlay and return to frontend site" should surround the 'X'. It is currently offset slightly above the 'X'.

Note from the Author or Editor:
Good catch. We'll have that fixed in the next update.

 Eduardo Cavazos  Jun 29, 2012  May 08, 2014
PDF
Page 146
Figure 3-54

In this screenshot the "Access" parameter in block settings is set to "Roles | editor," it should be set to "Permissions | View publish content."

The last paragraph on the previous page instructs the reader to do just this so the screenshot being off isn't a game changer, just a minor inconsistency.

Note from the Author or Editor:
Yep, good point. We'll update the screenshot in the next update.

 Austin Dempewolff  May 14, 2012  May 08, 2014
PDF
Page 151
module list

The chapter does not specify which version of the Media module is covered. I know this is going to change over time, but the current recommended version of the Media module is 7.x-1.0-* and the 7.x-2.x is only available in "unstable" or "dev" versions. A reader (such as myself) might assume that the chapter is written using the currently recommended 7.x-1.0 version and then get horribly confused (guess how I know) because the chapter is actually written to the 2.x version (I picked "dev" which is newer than "unstable" and there are significant changes.

Note from the Author or Editor:
Yep, you're right, we should probably say something about this, instead of assuming people are using the source code with the correct version.

EDIT:
On page 164, add a sentence to the end of the first paragraph under Spotlight: Media:

The Media module has been under active development and improvements are still in progress as of this writing. There are two distinct versions of the module. While the 1.x version is currently stable and recommended, we are using Media 2.x here due to its improvements, and the fact that it will ultimately be the normal version going forward.

 Steve Prior  Mar 13, 2012  May 08, 2014