Errata (First Edition)
This page lists the errors found in the first edition of the book.
Chapter 16. Sessions, Page 257
Mon, 09/08/2008 - 1:01pm — gpkThe error is identical to this http://www.drupalbook.com/node/154.
Chapter 16. Sessions, Page 257
Mon, 09/08/2008 - 1:12pm — gpk(Middle sentence) The exception to this is if the requestor doesn't accept cookies; in this case no row will be written to the sessions table.
Actually if anything has been stashed in $_SESSION then a row will be written to the sessions table. If the requestor doesn't accept cookies (and hence won't have presented one to the site) then while it is true that in general in this case a row won't be written to the table, the reason for this is that it is unusual for page requests for anonymous visitors to store anything in $_SESSION.
Chapter 17. Using jQuery, Page 265
Sun, 04/29/2007 - 1:16pm — Joe Moracamisc/query.js
misc/jquery.js
wrong file name for jquery
Chapter 17. Using jQuery, Page 265
Tue, 10/02/2007 - 2:27pm — rockoysterLine 5 contains an extraneous ";" and reads:
});,
Line 5 should read:
}),
Original code results in PHP parse error
[Nope. Look at this carefully. The correct line 5 is })', because the curly bracket closes the function(){} and the right parenthesis closes the ready() method and the sinqle quote closes the string that is the first parameter for drupal_add_js(). -JV]
Chapter 19. XML-RPC, Page 294
Wed, 04/18/2007 - 1:46pm — jvandykxmlrpc_errorno()
xmlrpc_errno()
Typo in function name.
Chapter 19. XML-RPC, Page 294
Wed, 04/18/2007 - 1:49pm — jvandykremote site gave an error:
remote site said:
The output should reflect the code listing earlier on the same page.
Chapter 19. XML-RPC, Page 295
Sat, 06/16/2007 - 10:06am — soxofaanxmlrpc_xmlc_guess_lucky_number
xmlrpc_xmls_guess_lucky_number
function name should follow the function name suggestion on page 296, first paragraph below first note: 'xmls' for server functions, 'xmlc' for client functions
Chapter 19. XML-RPC, Page 295
Tue, 04/17/2007 - 12:56pm — jvandykversion = $Name$
version = "$Name$"
Special characters in .info files must be quoted. But note that defining a version in an info file is now strongly discouraged.
Chapter 20. Writing Secure Code, Page 301
Sat, 06/16/2007 - 10:12am — soxofaanASCII character 20
ASCII character 32
In url encoding, the "20" in "%20" is a hexadecimal representation, which is "32" in decimal representation. Most readers will read "20" as "twenty", instead of "thirty two". This should be made more clear.
Chapter 20. Writing Secure Code, Page 309
Sun, 06/24/2007 - 9:10am — soxofaanhttp://example.com/?'%20R%20type%20=%20'story
http://example.com/?q=insecure/'%20R%20type%20=%20'story
part of url was omitted