Errata

In Chapter 5
section: Cross-Page Testing

There are a number of minor mistakes with the example which will cause it to fail or not work if followed word for word.

1:
views/tours/hood-river.handlebars

the href link in <a class= "requestGroupRate" href= "/request-group-rate">
should either be "./request-group-rate"
or "tours/request-group-rate", the current example resolves to localhost:3000/request-group-rate which does not match with the routing in meadowlark.js

2:
The cross site test for oregon coast tour should not have the referrer as "'http://localhost:3000/tours/hood-river'" as it then won't fail the test, "We?ll see that one of our tests is failing?it failed for the ?Oregon Coast Tour? page, which should be no surprise, since we haven?t added that page yet.". It doesn't fail the test, as the test is wrong. Catch22- Who tests the tests!!


3:
The command "mocha -u tdd -R spec qa/tests-crosspage.js 2>/dev/null" when run on osx will result in a silent failure, unless the user has added mocha as a global node module using - npm install mocha -g (is this just my setup causing these problems?)

Note from the Author or Editor:
Fixed.

The image tag example incorrectly uses an "href" attribute rather than the correct "src" attribute.

Note from the Author or Editor:
Duplicate; corrected in prior errata.

res.send(body), res.send(status, body)

In Express 4, res.send(status, body) is deprecated.

res.status(status).send(body) should be used.

Note from the Author or Editor:
Corrected.

On line 6 of code example 6-12, there is an extra single quote after the string '</tours>', which throws the rest of the code example into reverse-string limbo and breaks the syntax highlighting for the (color) example in the PDF.

Note from the Author or Editor:
Corrected.

There should be no right paren after '/api/tours' in Example 6-11:

app.get('/api/tours'), function(req, res){
res.json(tours);
});

Note from the Author or Editor:
Corrected.

Original text:

$.ajax({
url: action,

Changed to

$.ajax({
data: $(this).serialize(),
url: action

Note from the Author or Editor:
Good catch. This has been corrected.

Instead of:

<label for="fieldEmail" class="col-sm-2 control-label">Email</label>
<div class="col-sm-4">
<input type="email" class="form-control" required
id="fieldName" name="email">
</div>

It should be:
<label for="fieldEmail" class="col-sm-2 control-label">Email</label>
<div class="col-sm-4">
<input type="email" class="form-control" required
id="fieldEmail" name="email">
</div>

Notice the id of the input element is "fieldEmail".

This errors occurs several time before.

Note from the Author or Editor:
Corrected.

Just like to say I think this is a truly great book, by the way.

This whole section of including the "bootstrap-flash" functionality doesn't quite hang together. Firstly, you say at the top of the page "so make sure you have Bootstrap linked in." I had to do quite a bit of research about what Bootstrap actually is! Secondly you don't say where the Bootstrap bits and pieces should be put.
Thirdly, you omit to include code for VALID_EMAIL_REGEX or NewsletterSignup.
Getting confused at this point, I downloaded your chapter 9 "code-state" from github... but it doesn't provide a working implementation with this "bootstrap-flash" incorporated.
So then I downloaded your chapter 11 "code-state" (next one). After a bit of tweaking I was able to use this. And after a bit of tweaking I was able to copy its structure so that the boostrap stuff was where you put it, and my version of meadowlark.js included the necessary extra code.
But I had to copy across your version of main.handlebars because with the version I had developed, although the appropriate "bootstrap-flash" messages were displayed, they couldn't be dismissed (this despite me trying to understand and tweak the code from looking at your main.handlebars)...

Note from the Author or Editor:
The sample code in this chapter is intended to be more of a sample than a complete ready-to-use implementation. It sounds like that wasn't clear in the text, so I have updated the text to indicate the nature of these code samples. I also included an implementation of VALID_EMAIL_REGEX based on the W3C HTML5 email regex. I'm also taking notes from this errata for more substantive changes in the next edition.

The command(s) in the paragraph states:

body-parser (npm install --save body-parser, app.use(require(bbody- parser)());)

Note the typo in 'bbody'. It should be:

body-parser (npm install --save body-parser, app.use(require(body- parser)());)

Also, please add a newline like the rest of the middleware (makes it a bit clearer):

body-parser (npm install --save body-parser,
app.use(require(body- parser)());)

Note from the Author or Editor:
Corrected -- left on one line for formatting reasons.

the code as stated generates an error because the variable "http" is not defined anywhere at this point (if one is following along, or even if one downloads the chapter 11 code from github).
Presumably should be replaced by
app.listen(app.get('port'), function() {
console.log('Express started in ' + app.get( 'env') + 'mode on http://localhost:' + app.get('port') + '; press Ctrl-C to terminate.');
});

Note from the Author or Editor:
While http.createServer and app.listen are essentially interchangeable, I do agree that the book's use of these two methods is inconsistent. I replaced the calls to http.createServer with app.listen, except for Chapter 18, where I explicitly import https (as far as I know, there's no secure equivalent to app.listen).

in this chapter 12 (Production concerns) you started getting me rather confused because for some reason you revert to using the "http" var, which has not been used since the Meadowlark site was first started being built.

To begin with this was not a problem, but on p. 136, when you go into recovering from en error in a cluster, you define a var "server" which has then to be referenced if a worker fails.

I worked around this like this, but obviously I don't know whether it's the right solution...:

var server;
function startServer() {
server = app.listen(app.get('port'), function() {
console.log('Express started in ' + app.get('env') + ' mode on http://localhost:' + app.get('port')
+ '; press Ctrl-C to terminate.');
});
}

Note from the Author or Editor:
Corrected.

these lines cause an error:

fs.existsSync(dataDir) || fs.mkdirSync(dataDir);
fs.existsSync(vacationPhotoDir) || fs.mkdirSync(vacationPhotoDir);

... for the simple reason that require( 'fs' ) hasn't been used in the Meadowlark project.
In fact simple experimentation shows that you have to first go require( 'http' ) for require( 'fs' ) to work. Why, I have no idea!

Note from the Author or Editor:
Corrected. I added a reminder to make sure the fs library is imported. Its not necessary to import http before importing fs, as Mike suggests.

if(err) return res.redirect(303,'/error');

This line should be removed, otherwise the second error handler (which is more extensive) would never fire.

Note from the Author or Editor:
Corrected.

On this page one is hoping to see some magic with the Mongodb cloud-based database.
Instead, I got an error about undefined variable not having an attribute "length".
This refers to this line: if(vacations.length) return;, in "Vacation.find..." with the initial raw data (3 records).
And in fact, you don't introduce this variable "vacations" at all, either in meadowlark.js or in vacations.js.
Nor do you in fact say where the "Vacations.find..." function is supposed to go (I assumed meadowlark.js).
I haven't yet found a solution to this but I assume "vacations" should be introduced at some point as an empty array... also I'm far from clear about how, exactly the function parameter is fed to the Vacation.find method...

Working around the above problem I put
if(typeof vacations !== 'undefined'){
return;
};
... but this then caused a similar error: "Cannot call method 'map' of undefined" (part of the route functionality for '/vacations').

Note from the Author or Editor:
Corrected. The vacations variable is the second argument passed into the callback. The fact that its undefined indicates that there was an error; the problem with this code is there is no error handler, which I have corrected.

In the chapter "Security" you are describing how to purchase a private key. At the end of the chapter the generated private key is downloaded (via HTTPS) from the signing company.

In my opinion the public/private key-pair should always be generated by yourself and only a certificate signing request (CSR) should be sent to the signing authority. Otherwise you can't be sure that you are the only one knowing this private key.

I haven't checked with all certificate signing providers, but with all the providers I had business with, they accept only CSRs, and don't generate a private key for you.

Note from the Author or Editor:
Corrected.

The second call to app.get() passes the callback function to passport.authenticate() instead of to app.get(). That doesn't work. Unfortunately the lack of a JS type checker makes the error difficult to find.

Existing code:

registerRoutes: function(){
app.get(...);
app.get('auth...', passport.authenticate('facebook',
{ failureRedirect: ...},
function(req, res){
// we only get here on successful authentication
...
}
));
}

Correction by moving a ')':

registerRoutes: function(){
app.get(...);
app.get('auth...', passport.authenticate('facebook',
{ failureRedirect: ...}),
function(req, res){
// we only get here on successful authentication
...
}
);
}

Note from the Author or Editor:
This has been corrected in the text (along with some other improvements to the authentication flow), and the companion repo (on branch 'refactor', soon to replace branch 'master').