Errata for The Rails View

#49349: Example code's Gemfile doesn't set a version for Devise and 2.1.0 introduces breaking changes, causing the migration to fail. "~> 2.0.0" fixes the issue.--Jean-Charles Sisk

#50191: A few people have mentioned the problem with Devise.

One user (Jean-Charles Sisk) suggests using gem 'devise' '~ 2.0.0' in the Gemfile but this still throws a deprecation warning so I went back to '~ 1.5.4' for a clean install.

[DEVISE] You are using t.database_authenticatable and others in your migration and this feature is deprecated. Please simply use Rails helpers instead as mentioned here:

See the message here on github: github.com/plataformatec/devise/wiki/How-To:-Upgrade-to-Devise-2.0-migration-schema-style
--Ants

#51540: normalize.css "and place it into our app/assets/stylesheets directory". Since that stylesheet is "owned by outside entities" (text from Rails Guide on the Asset Pipeline), the stylesheet should be placed in vendor/assets/stylesheets. Same for modernizr on page 11 – although the reference there says only "assets/javascripts". That should be vendor/assets/javascripts.--slothbear

#49102: In the sample code the following line is used

<meta charset="utf-8">

the tag is never terminated it should probably say

<meta charset="utf-8" />
--Harald Scheirich

#49700: A designer/_designer.html.erb partial template is required for <%= render @project.designers %> to work, and the view containing it to render without errors. Also, there should be reference/link to the permissions page (either in the book, or as a site link), so that the reader is able to see the breadcrumbs in action without too much difficulty.--William Ko

#49085: When the text introduces the explicit alt attributes for images, it uses a wording that I think may suggest to the reader that the image tags are lacking alt attributes, and thus screen readers say "image, image, image"...

The image_tag helpers generates a default alt attribute with a humanized version of the image file name (alt is a mandatory attribute, that's why one is generated). So in general that would not be the case.--Xavier Noria

#49717: The if-else block (<% if @creation.default_image? %>) within _creation.html.erb on Page 69 does not continue from the state where it was last referenced on Page 65, where the following block has been refactored out of the creations index view (creations/index.html.erb):

<li class='creation'>
<p>
<%= creation_reference(creation) %>
<span class='client'><%= creation_client_name(creation) %></span>
</p>

Taking all that into account, the _creation.html.erb partial on page 69 should be as follows:

<li id='creation-<%= creation.id %>' class='<%= creation.file_type %>'>
<p>
<%= creation_reference(creation) %>
<span class='client'><%= creation_client_name(creation) %></span>
</p>
<%= controls_for_creation(creation) %>
</li>

--William Ko

#49734: The line: *= require formtastic
needs to come before the other sprocket directives that are meant to override the default styles that come with formtastic, like buttons (*= require buttons) and/or forms, depending on the original intent of the author.--William Ko

#49732: The styles used for section#sidebar to illustrate the popout mixin, are in conflict with those already defined on pages 24-25. Note that this is not immediately obvious unless the reader adds the additional section element to the sidebar vie to see the popout mixin in effect.

Adding further to the confusion, sidebar.css.scss in the accompanying code includes *both* versions of the section#sidebar definition. Although the latter declaration will override the former (thus the css can be parsed without problems), this is clearly not helping with comprehension.
--William Ko

#49731: The styles used to create the icons using sprites, are not working as stated in the book. I found that the following has to be added:

p.sprites {
height: 40px; // container must have proper dimensions, otherwise the icon will be clipping other elements

a.sprite-icon {
position: absolute;
}
}

Also, the offsets for approve-icon are wrong, and should be -80 as below:

.approve-icon
{
@include icon(-80px, -40px);
}--William Ko

#49095: running the cucumber test: artflow/js/features/session.feature fails with the following Error: ActionView::Template::Error: undefined method `with_status' for []:ActiveRecord::Relation--Romeo Giezendanner

#49176: "If we change the attribute to type="email", we end up with a space bar broken into three buttons: the space bar, the @ symbol, and a period. Any email address includes each of those at least once, so this change cuts down on having to hit the number button to get to additional symbols."

While the space can technically be used inside an email address (See rfc2822#page-47 for a really nasty example in section A.5), it wouldn't be fair to say that *any* email address includes a space at least once. Consider rephrasing to something like, "The symbols are ubiquitous in email addresses, so this change reduces the number of buttons we have to press."--Ben Taitelbaum

#49800: various problems with the code for the mobile chapter:

1. redirect_mobile in PagesController should redirect to project_creations_path instead of creations_path to be consistent with other links (under /projects/1) in the mobile views and related helper methods:

def redirect_mobile
if is_mobile_device?
redirect_to project_creations_path(Project.first)
end
end

Also, CommentsController and CreationsController should have set the instance variable @project for those links to appear as intended.

2. _header.mobile.erb is mentioned in the text but not used in the mobile views (creations/show, comments/index)

3. _creations.mobile.erb is not used for the final creations index view and should be renamed accordingly (_creations.v1.mobile.erb)
It should also be using creation.file.url instead of creation.url

4. edit.mobile.erb for creations would have made the mobile view example more complete

5. Since _footer.mobile.erb is empty, there should be no need for application.mobile.erb to render it at all (and yet missing _header.mobile.erb)--William Ko

#49730: In Section 7.1, it reads:

"When we set it up in Chapter 1,
Creating an Application Layout, on page 1, the page wrapper was 960 pixels
wide, the left column was 800 pixels wide, and the sidebar was 150 pixels
wide, which left us a gutter of 10 pixels between the two sides."

As a matter of fact, the mentioned css styles do not appear at all in Chapter 1.--William Ko

#49799: mobile-fu does not work properly with jquery-mobile without further customization:

Workaround:

Step 1: add the following before_filter to ApplicationController

class ApplicationController < ActionController::Base
before_filter :set_request_format

def set_request_format
request.format = :mobile if is_mobile_device? # && !request.xhr?
end
end
Step 2: use the following respond_to block in CommentsController#create

class CommentsController < ApplicationController
def create
@comment = @creation.comments.new(params[:comment])
@comment.user = current_user
@comment.save!

respond_to do |format|
format.any(:mobile) do
redirect_to creation_comments_url(@creation)
end
format.js
end
end
end--William Ko

#49003: You state that

"Since jQuery Mobile includes a style sheet and images, we need to tell Rails to serve them as well. We do that with a couple of provide directives in the same file:"

Rails 3.2 uses Sprockets 2.x where the "provides" directive has no function anymore. From sprockets-2.1.2/lib/sprockets/directive_processor.rb

# `provide` is stubbed out for Sprockets 1.x compat.
# Mutating the path when an asset is being built is
# not permitted.
def process_provide_directive(path)
end
--Michael Schuerig

#49823: assorted issues with Chapter 9 (vanity, deadweight)

page 209:
collecting should be set to true for development to observe meaningful results

page 210:
after_create filter should read as the following:

after_create :increment_subscription!

page 212: _form.html.erb

It appears that symbols and partial names cannot begin with numbers, so they should be changed to the following:

<% if ab_test('3_vs_5_plans') %>
<%= render 'plans3' %>
<% else %>
<%= render 'plans5' %>
<% end %>

page 216:
/creations/index should be just /creations

As a general comment, proofreading for this chapter has been exceptionally poor. The example is incomplete and should be more than just a dangling partial form that is not used anywhere else (and wouldn't have worked anyway due to the naming issue as mentioned above). The reader has to fill in the missing controller/view code to get a working example of vanity. --William Ko