Photos and slides are a one-to-one relationship, but the figure shows slides to photos as one to many.

The test database should be photos_test, not photos_development.

The contents of Figure 3.2 are actually what Figure 3.1 is supposed to have. Whatever is supposed to be in Figure 3.2 does not appear anywhere in the chapter, as far as I can tell.

"...you can implement one-to-one relationships with belongs_to or has_one."

This implies that you use one or the other macro. According to the API (http://apidock.com/rails/ActiveRecord/Associations/ClassMethods) you need to use both, and the issue is which one goes where. The answer (as the text correctly states) is, "The belongs_to association is always used in the model that has the foreign key."

reload! is insufficient to load the newly installed plugin, acts_as_list. I had to restart the script/console.

If you are using Rails 2.3.2 (current as of this writing) and you use the downloaded example files, you will need to rename photos/app/controllers/application.rb to photos/app/controllers/application_controller.rb. Otherwise you receive an error message: uninitialized constant ApplicationController. This rename was not necessary in the chapters where we used just the console.

Since we have changed the routes.rb file, we'll need to restart the server in order for the changes to be picked up.

The code is like this

module SlideshowsHelper
def thumbnail_tag(slide)
image_tag("photos/#{slide.photo.thumbnail}",
:style=>"vertical-align:middle") if slide
:class => "photos") if slide
end
end

instead of

module SlideshowsHelper
def thumbnail_tag(slide)
image_tag ("photos/#{slide.photo.thumbnail}",
:style => "vertical-align:middle",
:class => "photos") if slide
end
end

In the explanation of the new add_photo method in app/controllers/slideshows_controller.rb,

"slideshow_id = session[:slideshow].id"

This line of code does not appear in method given in the text, nor is it in the end-of-chapter example code.

TestCase has been moved from Test::Unit::TestCase to ActiveSupport::TestCase in v. 2.3.2. Make this change in /test/test_helper.rb.

Even though I am using SQLite my test.sqlite db was empty until I did this (rake db:test:clone). That is, Rails did not "build the database structure before each test run" as the text stated. I am using Rails 2.3.2.

In order to print the has enabled by the mods in greeting_controller.rb, one has to create a database in their database application. If this is not done, the has will not be displayed. An error about being unable to get to a database will appear.

There is a typo in some instruction on page 13 that make the instructions not work. On line 10, it states:

Point your browser to http://localhost:3000/greetings/index

It should read

Point your browser to http://localhost:3000/greeting/index

The Figure 3-1 does not represent "Rails supports single-table inheritance between an entity (Person) and a subclass (Photographer".

The Figure 3-2 does not present what text supposed to explain.

I believe under the Class: Photographer < Person portion of the diagram, type should be "Photographer".

States "the code dealing with pagination...has been removed", I do not believe there was any pagination code in there to start. Also see the photos-after-chapter-4 under example code.

Unless the pagination change is automatic when we changed variable names around from categories to all_categories in the controller, but this is not obvious at all to a novice.

One of my clients is reading the book to learn rails and found a bug
in the sqlite installation process. It says to unzip the file into
C:\WINDOWS\system. These instructions work fine in Windows XP, but my
client is using Windows Vista. In order to get this to work in Windows
Vista, we had to copy the file into C:\Windows\System32 instead. Not
sure what the easiest way to format that is in the book, but we should
keep this in mind.

"...file to C:\Windows\system." should say "...file to C:\Windows\system32."