Sign in through GitHub

Please read for an updated status on RailsCasts:

Learn more or hide this

Daniel Brown's Profile

GitHub User: narteyb

Comments by Daniel Brown

Avatar

It seems like the Crop coordinates values are not being set.
This is what I get in my params hash after submitting:

"profile_photo"=>{"crop_x"=>"", "crop_y"=>"", "crop_w"=>"", "crop_h"=>""}, "commit"=>"Crop Photo", "user_id"=>"2", "profile_id"=>"2", "id"=>"7"}

Notice how all the crop_* are empty? What could be the reason?

I have both
attr_accessor :crop_x, :crop_y, :crop_w, :crop_h

attr_accessible :crop_x, :crop_y, :crop_w, :crop_h
set.

Avatar

I m trying to use this gem and run into some issues. I managed to get around most of them, but now I am getting a seg fault. I believe it is happening in the controller where I have this code

from [based on material from here](https://github.com/berk/will_filter)
@regions = Region.filter(:params => params)

``` here is the seg fault message I am getting

/home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/relation.rb:241: [BUG] Segmentation fault
ruby 1.9.3p362 (2012-12-25 revision 38607) [i686-linux]

-- Control frame information -----------------------------------------------
c:0186 p:0018 s:0821 b:0818 l:000817 d:000817 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/relation.rb:241
c:0185 p:0028 s:0815 b:0815 l:000814 d:000814 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/scoping/default.rb:41
c:0184 p:0024 s:0812 b:0812 l:001934 d:000811 LAMBDA /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/scoping/named.rb:180
c:0183 p:---- s:0807 b:0807 l:000806 d:000806 FINISH
c:0182 p:0022 s:0805 b:0805 l:0020c8 d:000804 BLOCK /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/relation/delegation.rb:37
c:0181 p:0007 s:0803 b:0803 l:002134 d:000802 BLOCK /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/relation.rb:241
c:0180 p:0396 s:0801 b:0801 l:000800 d:000800 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/scoping.rb:98
c:0179 p:0018 s:0792 b:0792 l:002134 d:002134 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/relation.rb:241
c:0178 p:0055 s:0789 b:0789 l:0020c8 d:0020c8 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/activerecord-3.2.9/lib/active_record/relation/delegation.rb:37
c:0177 p:---- s:0783 b:0783 l:000782 d:000782 FINISH
c:0176 p:0163 s:0781 b:0781 l:000780 d:000780 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/will_filter-3.1.9/app/models/will_filter/filter.rb:821
c:0175 p:0250 s:0777 b:0777 l:000776 d:000776 METHOD /home/danny/.rvm/gems/ruby-1.9.3-p362/gems/will_filter-3.1.9/lib/will_filter/extensions/active_record_extension.rb:45

-- C level backtrace information -------------------------------------------

Avatar

Never mind, I found the issue and fixed it.

Avatar

I first implemented this episode and it work. However, I am using simple_for in my project, so I switched from 'form_for' o 'simple_form_for' in the devise new registrations view.

When the user log in using Twitter, for example, they are redirected to the new registration form as eexpected, since I my project requires email and Twitter does not provide user email address.

The project is that the registration form is not pre-populated with the first and last name on first pass. However, when you lick on the 'log in with Twitter' link again, then the correct behaviour (pre-populating the first name and last name fields) happens.

My question is, how do I avoid having to click the link twice in order to get the correct behaviour?

Thnx.

Avatar

I have tried to follow this tutorial to implement it in my own project, but I am never able to get it work. After adding the new.js.erb and adding the js code shown in the video, when I click 'Add Post' link nothing happens. I have followed the trouble shooting steps recommended by Ryan, still no dice. Although, I did get a n/w status of 304 unmodified as opposed to the 200 ok that Ryan got in the video. Any ideas as to what I am doing wrong?