Errata for Agile Web Development with Rails (4th edition)

#49315: After db:migrate is run and navigating to localhost:3000/products:

Routing Error

No route matches [GET] "/products"
Try running rake routes for more information on available routes.

rake routes produces:

Scott-Elliss-MacBook-Pro:depot sellis$ rake routes
products GET /products(.:format) products#index
POST /products(.:format) products#create
new_product GET /products/new(.:format) products#new
edit_product GET /products/:id/edit(.:format) products#edit
product GET /products/:id(.:format) products#show
PUT /products/:id(.:format) products#update
DELETE /products/:id(.:format) products#destroy--Scott Ellis

#48922: Provide instructions on how to avoid this up front (when running the "rake test" command for the first time). I am running the versions in the book/pdf that are required (rails/ruby/etc.).

gems/turn-0.9.3/lib/turn/minitest.rb:23:in `<top (required)>': MiniTest v1.6.0 is out of date. (RuntimeError)
`gem install minitest` and add `gem 'minitest' to you test helper.
--Paul J Solomon

#49168: In the book :
---------------
<div class="field">
<%= f.label :description %><br />
<%= f.text_area :description, rows: 6 %>
</div>
---------------
May be :
---------------
<div class="field">
<%= f.label :description %><br />
<%= f.text_area :description, :rows => 6 %>
</div>--Kevin Le Dû

#49082: Chapter 9: The 3rd statement being added to the line_items_controller to build @line_item causes an MassAssignmentSecurity::Error in rails version 3.2.3 on ruby 1.9.3p125 on Mac OSX 10.6.8. This same error occurs in the functional test on page 112. The fix is to replace ...build(product: product) with ...build(product_id: product_id. Apparently line_items.build can't figure out which attributes to set when building the instance.--Terry Cline

#49325: Functional tests failing with MassAssignementSecurity::Error. Fixed by adding the following:

to product.rb:
attr_accessible :product_id, :title, :description, :image_url, :price

to line_item.rb:
attr_accessible :product_id, :id, :cart_id, :created_at, :updated_at--Scott Ellis

#49118: When running rake test:functionals, even using the sample code, the following error occurs:

test_should_create_line_item(LineItemsControllerTest):
NoMethodError: undefined method `line_items' for 980190963:Fixnum
/home/user/rails/depot/app/controllers/line_items_controller.rb:45:in `create'
--Adam

#49083: In the migration method 'up', where we create a replacement item, the migration gets an error when rake db:migrate is run: "Can't mass assign attributes: quantity". The fix is to add :quantity to the attr_accessible declaration in line_item.rb. Rails 3.2.3, ruby 1.9.2 on Mac OSX 10.6.8.--Terry Cline

#49186: After building the up-migrate it fails with "Can't mass-assign protected attributes: quantity" until :quantity is added to LineItem model's attr_accessible.--David J. Schmidt

#49279: I experienced the same MassAssignmentSecurity::Error reported by Terry and David. Terry's solution caused this error:

undefined local variable or method `product_id' for #<LineItemsController:0x007fc04e8b5680>

David's solution seemed to work, but always added the book with id = 1 to the cart regardless of which book was chosen.

This solution worked for me:

@line_item = @cart.line_items.build(product_id: product.id)--Eric Theise

#49072: The CSS example at [p. 129.9] in depot_i/public/stylesheets/depot.css
doesn't match (media-origin.pragprog.com/titles/rails4/code/rails30/depot_i/public/stylesheets/depot.css).
--Shannon -jj Behrens

#48816: In the modifications to depot_n/app/views/line_items/create.js.erb, $('#cart tr').length will never equal 1 due to the <tr> which includes the total. Setting the value to less than 1 seems to solve the problem entirely.--Alexander Bradley

#48928: At some point in Chapter 11, all indexes broke, because the side bar expects @cart to be set. Unless I missed where this must be added (e.g. in the higher-level app controller, possibly in a before_filter), please fix this. Caused more time to be wasted in finding this...--Paul J Solomon

#48671: Figure 27 on chapter 12 shows links to Orders, Products and Users on the sidebar, but those links aren't added until chapter 14. Figure needs to be changed.--Ahsan Sharafuddin

#48654: It says that labels don't need explicit translations. This does not seem to work for rails 3.2.1. The name and email labels are just displaying Name and Email regardless of language. --Thijs de Vries

#48565: It appears the "proper" way to deploy with bundler, is to include the line
'require "Bundler/capistrano"'
in the deploy.rb file. Then the five lines at the end of the file (starting with 'after "deploy:update_code", :bundle_install' can be removed. As written in the book, deployment will fail with an "Unable to find gem "XXXX"" message when gems are added to the project.--Steven Finnegan

#48682: In database.yml configuration for production environment adapter for database is set to 'mysql'. However, as we are using 'mysql2' in our Gemfiles, adapter should be also changed to 'mysql2' for rake to work correctly.--Alexey

#49362: Please verify this...

The book says:
Idiomatic Rails developers use a variable named after the template (article in this instance). In fact, it’s normal to take this a step further. If the object to be passed to the partial is in a controller instance variable with the same name as the partial, you can omit the :object parameter. If, in the previous example, our controller had set up the article in the instance variable @article, the view could have rendered the partial using just this:
<%= render(partial: "article") %> <h3>Add Comment</h3>

However, I happened to bump into this in the layouts_and_rendering Rails Guides... (the URL was not allowed -- sorry).

under 3.4.4 Passing Local Variables it says:

In previous versions of Rails, the default local variable would look for an instance variable with the same name as the partial in the parent. This behavior was deprecated in 2.3 and has been removed in Rails 3.0.

It then continues:

If you have an instance of a model to render into a partial, you can use a shorthand syntax:
<%= render @customer %>

Assuming that the @customer instance variable contains an instance of the Customer model, this will use _customer.html.erb to render it and will pass the local variable customer into the partial which will refer to the @customer instance variable in the parent view.

--Perry Smith

#48557: Index contains set_primary_key method which doesn't appear anywhere in the book (which is good since this method is deprecated since rails 3.2.0). Pages: 450, 452, 458.--Jan Dudulski