Susan Harkins (240) [Avatar] Offline
#1
Please list errors in the published version of Sails.js in Action here. If necessary, we'll publish a comprehensive list for everyone's convenience. Thank you!

Susan Harkins
Errata Editor
Manning Publications
384963 (2) [Avatar] Offline
#2
page 5; directs reader to 'https://brushfire.io/'
brushfire.io refused to connect

Tried insecure page, it comes up, but network traffic does not match description, response is illegible in Dev tools and appears to be erlang
as a result, cannot track discussion in pages 6-12. No POST for example when submitting form
177646 (1) [Avatar] Offline
#3
A note for Sails 1.0:

Example 7.2 will not work if the user does not heed the following point from the Sails migration guide:

If your app relies on [action shadow routes](http://next.sailsjs.com/documentation/concepts/blueprints blueprint-routes#?action-routes) (where every custom controller action is automatically mapped to a route), you’ll need to update your config/blueprints.js file and set actions to true. This setting is now false by default.

Might be nice to call this out for when Sails 1.0 final hits.
bigtunacan (12) [Avatar] Offline
#4
384963 wrote:page 5; directs reader to 'https://brushfire.io/'
brushfire.io refused to connect

Tried insecure page, it comes up, but network traffic does not match description, response is illegible in Dev tools and appears to be erlang
as a result, cannot track discussion in pages 6-12. No POST for example when submitting form


Came to post this as well. This is something that could be corrected by updating the DNS settings and adding a valid ssl cert instead of an update to the book if that were more convenient.
bigtunacan (12) [Avatar] Offline
#5
Page 46 it says

~/firstApp $ sails generate controller life?


That question mark at the end should not be there.