Does anyone know how to filter the long output from Rails tests? For example, for a simple failed route test, the output goes on for page after page. This is affecting @RailsTutorial readers (including its author).

The videos are embedded in the course at learnenough.com/course/ruby_… Once you click through to a page that has a corresponding video, you’ll see a player at the top of the screen. Let us know if that works!

You should merge those changes into the subsequent branches as well: $ git checkout following-users $ git merge user-microposts $ git checkout master $ git merge following-users At that point, everything should work!

The way to avoid this kind of error in @Rails is to use the “pluralize” method (as covered in Chapter 7 of the @RailsTutorial). railstutorial.org/

We do use Cloudflare. We even have a tutorial that covers it (learnenough.com/custom-domai…). Cloudflare doesn’t handle such things automatically, though, and it also took some time to figure out it was a DDoS. The DDoS targeted a specific part of the site (search) to overload the DB.

Yup. 👍

Good catch! Listing 3.32 is part of an exercise, and (as noted in Chapter 1) exercise answers aren’t generally incorporated into the main text (railstutorial.org/book#sec-e…). Hope this helps!

Just added a note to the @RailsTutorial about maximum password length. TL;DR: has_secure_password adds an automatic validation for a max password length of 72.

I appreciate your concern. The Rails 5 version is linked from railstutorial.org/book and is also mentioned in the recently published announcement post (news.learnenough.com/ruby-on…)

Here’s the solution in case you still get stuck.