ruby-on-rails-3.2

In order to ensure that my application is not vulnerable to this exploit , I am trying to create a controller test in RSpec to cover it. In order to do so, I need to be able to post raw JSON, but I haven't seemed to find a way to do that. In doing some research, I've determined that there at least used to be a way to do so using the RAW_POST_DATA header, but this doesn't seem to work anymore: it "should not be exploitable by using an integer token value" do request.env["CONTENT_TYPE"] = "application/json" request.env["RAW_POST_DATA"] = { token: 0 }.to_json post :reset_password end When I look

I'm trying to use y object in Rails 3.2.6/Ruby 1.9.3 console to get nicely formatted yaml output for an ActiveRecord object, but for some reason it isn't working for me. I've used it in the past, but somewhere along the way it broke. I get the following output when I try: NameError: undefined local variable or method `yaml' for main:Object The y method is actually an extension to the Kernel object put in place by the Syck YAML parser/emitter . Here are the last few lines of lib/ruby/1.9.1/syck.rb : module Kernel def y( object, *objects ) objects.unshift object puts( if objects.length == 1 YAML

I'm working through the Railscast on implementing Devise and OmniAuth (along with the Devise documentation ) -- currently, I've got a site going where visitors can sign up using their facebook accounts or by filling out a form. I'm running into trouble when users that sign up via OmniAuth try to edit their profiles, though. Devise looks for the user's current password when they submit changes to their profiles, but those that logged in with facebook don't know their passwords (they're set automatically in the user model): def self.find_for_facebook_oauth(auth, signed_in_resource=nil) user =

I am trying to precompile assets using the command rake assets:precompile RAILS_ENV=production , but I always get the error below. ** Invoke assets:precompile (first_time) ** Execute assets:precompile /usr/bin/ruby /usr/bin/rake assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets --trace ** Invoke assets:precompile:all (first_time) ** Execute assets:precompile:all ** Invoke assets:precompile:primary (first_time) ** Invoke assets:environment (first_time) ** Execute assets:environment ** Invoke environment (first_time) ** Execute environment ** Invoke tmp:cache:clear (first_time) **

What are advantages and disadvantages of using namespace in ruby on rails. For example: I've many controllers like CompanyLocations CompanyXXXX CompanySports CompanyActivites CompanyQQQQQ I want to put all these controllers in Company folder. What is the rails best practice for this ? Jenorish You have to create a subfolder inside your controller/ directory, and the same in your views/ directory. Your controller file should look like module Company class SportsController < ApplicationController def index end end end ...or class Company::SportsController < ApplicationController def index end

I'm using Rails 3.2 and have a migration that contains the code: add_column :users, :gift_aid, :integer, :default => 2 # reset columns User.reset_column_information ... code here to load legacy data from sqlite3 database ... # now create a user with the loaded column data user = User.create( ...other cols..., :gift_aid => migrated_gift_aid_column_data, ...other cols... ) and I get unknown attribute: gift_aid when running the migration. User.column_names shows the same list before and after the call to reset_column_information . Oddly when I manually drop the column in mysql and re-run the

I want to populate a new feature with dummy data, but don't want to use the db/seeds.rb file as it already has seeds other data irrelevant for this feature. To run the default seeds.rb file, you run the command rake db:seed . If I create a file in the db directory called seeds_feature_x.rb , what would the rake command look like to run (only) that file? zeantsoi Start by creating a separate directory to hold your custom seeds – this example uses db/seeds . Then, create a custom task by adding a rakefile to your lib/tasks directory: # lib/tasks/custom_seed.rake namespace :db do namespace :seed