Errata for Crafting Rails Applications

#47953: Running with:

ruby 1.9.2p312 (2011-08-11 revision 32926) [x86_64-darwin10.8.0]
Rails 3.0.10
capybara (1.1.2)

rake test fails with:

encoding error : output conversion failed due to conv error, bytes 0xFF 0xC3 0xBF 0xC3
I/O error : encoder error

Change in test/integration/navigation_test.rb

From:
assert_match /Prawn/, page.body
To:
assert_match /Prawn/, page.source

rake test passes clean

Suspect capybara internals change - Gemfile could be pinned to the older version of Capybara that works as advertised (or not).--Rick Lloyd

#47603: latest test run doesn't pass ...

rubyrails:pdf_renderer (ruby-1.9.2@rails310)$ rake test
rake/rdoctask is deprecated. Use rdoc/task instead (in RDoc 2.4.2+)
`include Capybara` is deprecated please use `include Capybara::DSL` instead.
Loaded suite /Users/yves/.rvm/gems/ruby-1.9.2-p290@rails310/gems/rake-0.9.2/lib/rake/rake_test_loader
Started
encoding error : output conversion failed due to conv error, bytes 0xFF 0xC3 0xBF 0xC3
I/O error : encoder error
F.
Finished in 0.360567 seconds.

1) Failure:
test_pdf_request_sends_a_pdf_as_file(NavigationTest) [/Users/yves/Developpement/Projects/CRAFTING/pdf_renderer/test/integration/navigation_test.rb:15]:
Expected /Prawn/ to match "".

2 tests, 6 assertions, 1 failures, 0 errors, 0 skips

Test run options: --seed 63768
rake aborted!

--yves dufour

#46891: "After running `rake test`, all tests should be green again", but they're not! We've now made a template for our mail form to use, but never told it to use it, as far as I can tell. I'm not quite sure where to specify this, either.--chadoh

#46892: """
== The Resolver's Cache
As your learned in the code on page 71 ActionView::Resolver’s find_all method…
"""

I'm on page 63, so I haven't read page 71 yet. ;-)--Chad Ostrowski

#47175: I tried "Hello Rack" application with Rack 1.2.3, which was installed by Bundler for Ruby on Rails 3.0.7. (I understand that the book is based on Ruby on Rails 3.0.3 and maybe it's using a different version of Rack.)

An error occurred:
ERROR Rack::Lint::LintError: Response body must respond to each

So I enclosed the body string in an array, i.e.:
[200, { 'Content-Type' => 'text/html' }, ['Hello Rack!']]

Then the "Hello Rack" application worked correctly. --Tadatoshi Takahashi

#46512: The Rack application on this page does not run on Ruby 1.9.2. The error is "Response body must respond to each". Ruby 1.9 (unlike 1.8) apparently doesn't provide an each method on string objects.

The Rack Specification states the body value in the environment argument "commonly is an Array of Strings, the application instance itself, or a File-like object".

A possible fix is to change the following line from this:
[200, { 'Content-Type' => 'text/html' }, 'Hello Rack!'] to this:
[200, { 'Content-Type' => 'text/html' }, ['Hello Rack!']]
thus making the body string into an array of strings.

This allows the application to run without error and with no change to the expected output.--Steve Morris

#49335: I cannot get why this source code appears here.

>>
Download responders/2_responders/test/dummy/app/views/layouts/application.html.erb
<p class="notice"><%= notice %></p>
<p class="alert"><%= alert %></
<<--Yasuo Honda

#47359: Hi,

I may have missed something but when I run "bundle exec rails g responders:install" nothing happens and I have "Could not find generator responders:install.".

I think the reason is that the new files were not declared in lib/responders.rb (require "responders/install/install_generator") I then have the following error :
install_generator.rb:3:in `<module:Generators>': uninitialized constant Rails::Generators (NameError)

Perhaps because require "rails/generators/base" is missing in lib/responders/install/install_generator.rb but then I have the following error :
railties-3.0.9/lib/rails/generators/base.rb:228:in `inherited': undefined method `subclasses' for Rails::Generators:Module (NoMethodError)

Undoubtedly I missed something, but I am stuck here...

Regards
Alex--Alex

#46617: On:

autoload :App, "translator/app"

It should be:

require 'translator/app'
autoload :App, "translator/app"

The missing require will cause an "uninitialized constant Translator::App" exception on startup.
--Fabio Kreusch