All Comments

Thanks a lot!!! :D

nice work done by you

Hi... this is such a cool resource. do you ever plan to revive it? romy

*1* gem 'jquery-rails' and gem 'rails3-generators' no longer needed. *2* Specify Compass version by gem 'compass', '~> 0.12.alpha.0' *3* DO NOT USE Compass INIT. Create your own css.scss in app/assets/stylesheets, with CSS frameworks you want @import '_blueprint'; @include blueprint; *4* Add your scss to the Assets Pipeline

I found a new solution for this. In my case I was trying this out on pic-tales.com .. and figured it out that my server timezone was set improper so that created that problem. Found this out by debugging use_nonce[ first line]. worked with charm after changing timezone!!

Good point there Jeff. Using File.join will avoid some potential bugs.

I don't like the code in the fixture method. Bad practice to hard-code path separators. def fixture(file) File.new( File.join(fixture_path, file) ) end would be better

Actually, back in Post #1 during the initial installation, I chose not to put the stylesheets in the app directory. With Rails 3.1, thought, the app directory should be that standard.

Your sass file should be app/stylesheets/application.sass. Perhaps I'm using a more recent version of compass, or just a different config, but that's the default on my configuration. Thanks, Steve

Thanks again Steve. Update added.

Great points there Steve. Thanks for the tips.

1. Same comments as before with your scaffolding (references, scaffold.css). You'll need to update your migration snippet if you go with references. 2. You forgot to update your posts controller like you did in a previous lesson: @post = Post.new(:sequence => Post.all.size + 1) should be @post = Post.new(:sequence => Post.count + 1)

1. Why not use post:references rather than post_id:integer? You'll get the belongs_to :post for free in the section model. 2. When running the scaffold, tell your readers to *not* overwrite scaffold.css or else they'll lose the changes from the previous post. Steve

Using rails 3.0.7. Problem with your javascript defaults, which reference non-existent rails.js. So I'm using: config.action_view.javascript_expansions[:defaults] = %w(jquery jquery-ui jquery_ujs) Thanks, Steve

Excellent points -- speeding up the test suite begins to matter as the number of tests go up. Autotest is a good tool to leave running in the background so there will be less downtime while waiting for tests to re-run. --Walter

Excellent write-up, one of the best I have seen so far -- it covers integration testing in depth and keeps up with the RSpec Book by Chelimsky, which I happened to review while working through your examples today. Keep up the good work! --Walter

this is nice....

The part about CSRF Protection in Rails 3.0.4 is CRITICAL! I was trying to log in with Google and found myself logged out after the redirect. Finally figured out the cause was in Devise when handle_unverified_request is called the session is destroyed. Not sure what the permanent fix is but your method saved me.

Thanks. I'm glad you like it. About race conditions, I'm not too familiar with the issue, but maybe this will help http://guides.rubyonrails.org/active_record_querying.html#locking-records-for-update

Hi congrats for your blog it's very useful. I'd like to know would manage race-conditions in rails, here is an example http://stackoverflow.com/questions/4939349/find-or-create-and-race-condition-in-rails-theory-and-production/4940469#4940469

It's Looks nice tute to go with Capybara..!!

I'm still not sure what was causing that bug. I doubt it was OmniAuth and would guess that OmniAuth would work with either Ruby 1.8.7 or 1.9.2 without a problem if you weren't using memcached.

Thanks for the info Graham. I'll check it out.

Does the bug in the last section mean that you can't use multiple versions of ruby with omniauth?

On the subject of avoiding having to type `bundle exec` all the time, I cooked up a short shell script that automatically prepends it to common Ruby commands (e.g. ruby, rake, rspec, shotgun) when you're in a bundled project. You can find it on GitHub: https://github.com/gma/bundler-exec

Thanks Clemens. Typo corrected.

Typo: If you need to undo the scaffolding, use 'rails destroy scaffold announcement'. should be: If you need to undo the scaffolding, use 'rails destroy scaffold post'. Cheers!

David, I'm not quite sure what you're referring to, but Barista does automatically compile CoffeeScripts into JavaScripts in development mode. The default is that you have CoffeeScripts in app/coffeescripts and the javascripts will be in public/javascripts (although these can be changed through configuration).

I was just reading through this gem the other day. I wish it worked more like the integration compass has when generating stylesheets from scss... actually writing the javascript file into public/javascripts. I'm using this and compass on a new app, and it bothers me that the same concept (generating [stylesheets|javascript] from a proto-language) is handled two different ways.

I had no idea I was such a wise, elderly sage. Good intro to BDD, and I must say I was quite surprised to find myself such a central character in a random post I clicked to from RubyFlow. ;)

Thanks again Dave. In show.html.haml, when I edited that snippet, I put some comments in showing the edited parts. I was using Ruby syntax for comments. I have changed it to HAML comments "-#". Also, fixed the other typo. About the source code, I've been thinking about putting it on Github with a commit after each post. I've created an empty repository at https://github.com/aRailsDemo/arailsdemo. I'll try to get some of the code on there.

Thanks Dave for picking that up. It's been corrected.

Getting this error at the end of Part #3 Can the source code be shown somewhere so I can compare ? Thanks, Dave >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Haml::SyntaxError in Posts#show Showing C:/Ruby192/RailsApps/arailsdemo/app/views/posts/show.html.haml where line #2 raised: Illegal element: classes and ids must have values. Extracted source (around line #2): 1: %h1= "\##{@post.sequence} #{@post.title}" 2: # %p= raw @post.description 3: %p= sanitize @post.description # edited 10/27/10 4: 5: - for section in @post.sections

Typo: app/views/posts_form.html.haml should be app/views/posts/_form.html.haml

Should the root :to => not be "posts#index" ? Cheers Dave

This comment was made after logging in through the site's Twitter account...

User comments coming soon...