Glad it worked out. f is defined in the user model. Did you check
that you'd set all your file permissions correctly (755 for folders
and 644 for .rb files)?. Not sure if that would cause this problem
but I think incorrect permissions can cause some issues.
Jason
On 24/02/2009, at 3:03 PM, KtyKat223 wrote:
>
> I took a little of everyones advice. I downloaded from source and
> installed everything fresh. rails 2.2.2 ,ruby 1.8.6, etc... and I will
> have you know my css prob is solved!! Yay!! Of course thats not the
> end of my woes. no I have a new error to deal with. now i can't access
> the admin area.
>
> NoMethodError in Admin/users#index
>
> Showing app/views/admin/users/index.html.erb where line #8 raised:
>
> undefined method `f' for nil:NilClass
>
> Extracted source (around line #8):
>
> 5: <% @results.each do |p| %>
> 6: <div class="<%= cycle('odd','even') %> search_row left">
> 7: <div><%= icon p, :small %></div>
> 8: <div><%= link_to h(p.f), p %></div>
> 9: <div><%= mail_to h(p.email), p.email %></div>
> 10: <div><%= link_to_remote "#{ p.is_active ? 'deactivate' :
> 'activate' }", {:url => formatted_admin_user_path(p, 'js'), :method
> => :put}, {:id => p.dom_id('link')} %></div>
> 11: </div>
>
>
> But I'm pretty sure once I figure this out all will be fine. If I can
> figure it out.
>
> On Feb 22, 11:28 am, Jonathon Brenner <[email protected]> wrote:
>> If possible, you should always build from source. In the much
>> cited "Great
>> Ruby Shootout<http://antoniocangiano.com/2008/12/09/the-great-ruby-
>> shootout-decembe...>
>> ",
>> compiled Ruby was twice as fast as the apt-get version. As always
>> though,
>> YMMV.
>>
>> On Sun, Feb 22, 2009 at 2:19 AM, Jason Keenan
>> <[email protected]>wrote:
>>
>>
>>
>>> Here's a link (http://www.petercooper.co.uk/installing-ruby-186-
>>> from-
>>> source-on-ubuntu-feisty-fawn-49.html) with instructions on
>>> installing
>>> from source. Not sure what flavour of ubuntu you are using. This
>>> one's for feisty fawn.
>>
>>> As far as definitely saying 1.8.6 is what you want, I can't
>>> guarantee
>>> that this is your issue but I can say that lovd works with this
>>> version and that the errors you mentioned, with a brief bit of
>>> googling, seems to be the problem. There are also an infinite number
>>> of possibilities in regards to what your problems might be. I'm
>>> not a
>>> linux guru. I personally would tend to try and find a guide that
>>> other people have commented as having worked and follow it verbatim
>>> if I was going from scratch, but that's because I'm not confident
>>> about fixing up issues myself. If you are comfortable with
>>> installing
>>> and setting up a server with apache then half your battle is won.
>>
>>> Jason ;)
>>> On 22/02/2009, at 5:12 PM, KtyKat223 wrote:
>>
>>>> Srry about the multiple posting!!! My browser got "stuck on stupid"
>>>> for a moment.
>>
>>>> On Feb 22, 1:10 am, KtyKat223 <[email protected]> wrote:
>>>>> So your definitely saying it's best to go with 1.8.6 b/c
>>>>> lovdbyless
>>>>> isn't ready for the newer versions.? any recommendations on the
>>>>> best
>>>>> place to download it from then? I wouldn't want to download
>>>>> something
>>>>> that could possibly be comprimised. And again, THANK YOU for
>>>>> all your
>>>>> help and advice!! It is greatly appeciated!!
>>
>>>>> On Feb 21, 11:47 pm, Jason Keenan <[email protected]> wrote:
>>
>>>>>> Yes it does seem to say 1.8.7 on the rails site. It was 1.8.3
>>>>>> that
>>>>>> was the problem one.
>>
>>>>>> Having a bit of a google around it seems that there are some
>>>>>> changes
>>>>>> in 1.8.7 that break some rails apps. So technically it seems
>>>>>> like it
>>>>>> might be a lovd-by-less problem.
>>
>>>>>> For lovd-by-less I think you should go with 1.8.6. I think
>>>>>> there are
>>>>>> some added things in 1.8.7 and as everyone migrates to 1.9
>>>>>> lovd will
>>>>>> most likely go with it.
>>
>>>>>> Jason
>>>>>> On 22/02/2009, at 2:12 PM, KtyKat223 wrote:
>>
>>>>>>> P.S I just saw on rubyonrails.org they're recommending
>>>>>>> 1.8.7 .?.?
>>>>>>> thats probably why the ubuntu repository has only v 1.8.7 . But
>>>>>>> if you
>>>>>>> still recommend 1.8.6 I'll find and install it from somewhere
>>>>>>> else.
>>>>>>> I'll just work on my other prob for the time being.
>>
>>>>>>> On Feb 21, 10:06 pm, KtyKat223 <[email protected]> wrote:
>>>>>>>> just removed ruby 1.8.7 and went to install 1.8.6 . It's not
>>>>>>>> there.
>>>>>>>> the repository only has v 1.8.7 and apparently 1.9 . so now i
>>>>>>>> need to
>>>>>>>> find an outside source to download 1.8.6 . I just hope that
>>>>>>>> doesn't
>>>>>>>> cause probs with installing the nessesary gems. Oh well, back
>>>>>>>> to the
>>>>>>>> begining with trying to get it to work!
>>
>>>>>>>> On Feb 21, 8:40 pm, Jason Keenan <[email protected]>
>>>>>>>> wrote:
>>
>>>>>>>>> Hi,
>>
>>>>>>>>> A quick look at google hinted that, as mentioned, your ruby
>>>>>>>>> version
>>>>>>>>> could be causing this problem. Rails recommends 1.8.6 and I'm
>>>>>>>>> pretty
>>>>>>>>> sure actually warns against 1.8.7. I found thishttp://
>>>>>>>>> www.bluehostforum.com/showthread.php?
>>>>>>>>> t=13893whichisn'texactlythe
>>>>>>>>> same but sounds familiar.
>>
>>>>>>>>> As far as making apache work with ROR, there are a ridiculous
>>>>>>>>> amount
>>>>>>>>> of tutorials out there. The main problem is deciding which one
>>>>>>>>> you
>>>>>>>>> want to go with. I think you'll find that your local
>>>>>>>>> development
>>>>>>>>> version is working because it's getting served by either
>>>>>>>>> webrick or
>>>>>>>>> mongrel and never touching apache.
>>
>>>>>>>>> Like you said, make sure your shebang lines are correct in
>>>>>>>>> your
>>>>>>>>> dispatch.fcgi and dispatch.rb files and make sure
>>>>>>>>> your .htaccess
>>>>>>>>> file
>>>>>>>>> is set up properly.
>>
>>>>>>>>> For the css, make sure that the SITE = RAILS_ENV ==
>>>>>>>>> 'production' ?
>>>>>>>>> 'lovdbyless.com' : 'localhost:3000' line in your
>>>>>>>>> global_variables.rb
>>>>>>>>> file reads SITE = RAILS_ENV == 'production' ?
>>>>>>>>> 'mypublicfacingurl.com' : 'localhost:3000' so that the browser
>>>>>>>>> can
>>>>>>>>> find the css file.
>>
>>>>>>>>> Jason
>>
>>>>>>>>> On 22/02/2009, at 5:50 AM, KtyKat223 wrote:
>>
>>>>>>>>>> While working with it I actually set all the permission on
>>>>>>>>>> it at
>>>>>>>>>> 775.
>>>>>>>>>> I was going to drop them to where they needed to be once I
>>>>>>>>>> knew
>>>>>>>>>> everything would work properly. the only logs I get when I
>>>>>>>>>> try
>>>>>>>>>> to get
>>>>>>>>>> apache to serve the site are the apache error log
>>
>>>>>>>>>> [Sat Feb 21 12:47:22 2009] [warn] (104)Connection reset by
>>>>>>>>>> peer:
>>>>>>>>>> mod_fcgid: read data from fastcgi server error.
>>>>>>>>>> [Sat Feb 21 12:47:22 2009] [error] [client 127.0.0.1]
>>>>>>>>>> Premature
>>>>>>>>>> end of
>>>>>>>>>> script headers: dispatch.fcgi
>>>>>>>>>> [Sat Feb 21 12:47:28 2009] [notice] mod_fcgid: process /
>>>>>>>>>> var/www/
>>>>>>>>>> lovdbyless/public/dispatch.fcgi(5130) exit(communication
>>>>>>>>>> error),
>>>>>>>>>> terminated by calling exit(), return code: 255
>>
>>>>>>>>>> and once in a while in the fast cgi crash log in the
>>>>>>>>>> lovdbyless
>>>>>>>>>> logs
>>
>>>>>>>>>> # Logfile created on Fri Feb 20 15:42:52 -0500 2009 by /
>>>>>>>>>> [20/Feb/2009:15:42:52 :: 13156] starting
>>>>>>>>>> [20/Feb/2009:15:42:52 :: 13156] stopping gracefully
>>>>>>>>>> [20/Feb/2009:18:59:29 :: 25203] starting
>>>>>>>>>> [20/Feb/2009:18:59:29 :: 25203] stopping gracefully
>>
>>>>>>>>>> And when i say server Yes it is one I'm setting up my
>>>>>>>>>> self. It
>>>>>>>>>> belongs
>>>>>>>>>> to a friend of mine and I'm doing this as a favor for him.
>>>>>>>>>> It's an
>>>>>>>>>> actual rack mount server. A little older model but it is a
>>>>>>>>>> very
>>>>>>>>>> nice
>>>>>>>>>> one (more than enough for what he'll be using it for) and
>>>>>>>>>> it was
>>>>>>>>>> still
>>>>>>>>>> in the box unopened when he got it. Right now it works
>>>>>>>>>> fine with
>>>>>>>>>> everything he needs on it except for an error in a part of
>>>>>>>>>> the
>>>>>>>>>> online
>>>>>>>>>> store thats on it. but while I was figuring that out I was
>>>>>>>>>> fooling
>>>>>>>>>> around with this for the space on the server i get to use. It
>>>>>>>>>> is a
>>>>>>>>>> complete fully functioning web server (except for the
>>>>>>>>>> ecommerce
>>>>>>>>>> site
>>>>>>>>>> till I figure that 1 lil prob out). But as I said earlier,
>>>>>>>>>> this
>>>>>>>>>> is the
>>>>>>>>>> first time I've done anything with ROR. and any advice is
>>>>>>>>>> more than
>>>>>>>>>> welcome. Especially since I have found extremely little info
>>>>>>>>>> anywhere
>>>>>>>>>> about getting ROR to play nicely with apache. As far as being
>>>>>>>>>> explicit
>>>>>>>>>> I'm not sure what info your looking for although I'm pretty
>>>>>>>>>> sure,
>>>>>>>>>> while I was typing this, I just found the reason rails won't
>>>>>>>>>> start. I
>>>>>>>>>> Just realized that the place the dispatch.fcgi header is
>>>>>>>>>> pointing to
>>>>>>>>>> doesn't exist. I just need to find where ruby is on this
>>>>>>>>>> machine
>>>>>>>>>> and
>>>>>>>>>> point it there. Hopefully that will fix the rails failing to
>>>>>>>>>> start
>>>>>>>>>> prob. because when i run the command
>>
>>>>>>>>>> ruby dispatch.fcgi
>>
>>>>>>>>>> the output is "perfect" if there is such a thing. I wonder if
>>>>>>>>>> that
>>>>>>>>>> might be why the CSS wont work in production? or from a
>>>>>>>>>> client even
>>>>>>>>>> while in developement?
>>
>>>>>>>>>> On Feb 21, 9:15 am, Jason Keenan <[email protected]>
>>>>>>>>>> wrote:
>>>>>>>>>>> Hey there,
>>
>>>>>>>>>>> Check the log to see if there is anything there. I had some
>>>>>>>>>>> problems
>>>>>>>>>>> with the latest version of rails too. With a failed to start
>>>>>>>>>>> message,
>>>>>>>>>>> nothing in the logs though cause, funnily enough, it
>>>>>>>>>>> fails to
>>>>>>>>>>> start.
>>
>>>>>>>>>>> For the CSS, make sure you have your production domain
>>>>>>>>>>> set in
>>>>>>>>>>> global_variables.rb
>>
>>>>>>>>>>> For the failed to start bit, make sure you have the correct
>>>>>>>>>>> permissions set on the files. All the folders should 755 and
>>>>>>>>>>> files
>>>>>>>>>>> should be 644 except dispatch.fcgi from memory which should
>>>>>>>>>>> also be
>>>>>>>>>>> 755. I installed straight from git and there were
>>>>>>>>>>> unfortunately
>>>>>>>>>>> some
>>>>>>>>>>> permission glitches. You will also need to adapt
>>>>>>>>>>> your .htaccess
>>>>>>>>>>> file
>>>>>>>>>>> in the public folder to suit your setup.
>>
>>>>>>>>>>> When you say 'your server', is this one you've set up
>>>>>>>>>>> yourself
>>>>>>>>>>> from
>>>>>>>>>>> scratch or a hosting service. If you've set it up
>>>>>>>>>>> yourself then
>>>>>>>>>>> you'll have some fun getting it working easily. If the
>>>>>>>>>>> latter, the
>>>>>>>>>>> tips above might help. You probably need to give a more
>>>>>>>>>>> explicit
>>>>>>>>>>> description of what you are doing or have done.
>>
>>>>>>>>>>> Jason :)
>>
>>>>>>>>>>> On 21/02/2009, at 4:26 PM, Steven Bristol wrote:
>>
>>>>>>>>>>>> On Fri, Feb 20, 2009 at 9:14 PM, KtyKat223
>>>>>>>>>>>> <[email protected]>
>>>>>>>>>>>> wrote:
>>
>>>>>>>>>>>>> I guess it's my turn to finally ask a question. After all
>>>>>>>>>>>>> I did
>>>>>>>>>>>>> figure
>>>>>>>>>>>>> out everything else on my own! It took me two days of
>>>>>>>>>>>>> workarounds to
>>>>>>>>>>>>> install everything I needed to run LovdByLess on my
>>>>>>>>>>>>> server. I
>>>>>>>>>>>>> have it
>>>>>>>>>>>>> running fine in development mode while accessing it on the
>>>>>>>>>>>>> localhost.
>>>>>>>>>>>>> But when I run it in
>>
>> ...
>>
>> read more ยป
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Lovd by Less" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/lovdbyless?hl=en
Who loves ya baby?
-~----------~----~----~----~------~----~------~--~---
