Damaris Fuentes wrote:
> Taking a look through Google I found that some people have the same
> problem, but most of them because they have changed from Webrick to
> Mongrel. Apparently, console with mongrel does not show the "puts"
> messages. However, I am working with webrick.
I'm getting th
Taking a look through Google I found that some people have the same
problem, but most of them because they have changed from Webrick to
Mongrel. Apparently, console with mongrel does not show the "puts"
messages. However, I am working with webrick.
Damaris Fuentes wrote:
> On the server console
On the server console.
I run the server by means of "jruby script/server", in development mode.
At the server console just appears the information of the HTTP requests.
James Byrne wrote:
> On Jul 10, 5:33�am, Damaris Fuentes
> wrote:
>> Ok, I will take a look to these ways for debug.
>> Howeve
On Jul 10, 5:33 am, Damaris Fuentes
wrote:
> Ok, I will take a look to these ways for debug.
> However, I still don't understand why my "puts" don't work.
> My non-Active record models are not in the app/model directory, but in
> an app/engine directory (is someone else work), can be this the p
Ok, I will take a look to these ways for debug.
However, I still don't understand why my "puts" don't work.
My non-Active record models are not in the app/model directory, but in
an app/engine directory (is someone else work), can be this the problem?
Or can be something related with jruby?
Älph
You should debug through test parameters. Here's a site link to help:
http://www.thechrisoshow.com/2008/5/4/five-tips-for-testing-rails
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
It is just I want to see objects attributes I have from my model classes
in the output, this is why I do the "puts" or "p", but it does not work.
For example, I have a SearchEngine class, I have a def search() function
that returs some results, and I want to see these results before sending
the
Well, there are a few different ways to debug your app. What are you
trying to find out?
In the model you can put:
class ModelName < ActiveRecord::Base
puts caller
..
..
end
That will give you the call stack everytime the model is hit.
If you want to debug params within your views you can
8 matches
Mail list logo
