I have narrowed my problem in a prior topic (I'm having trouble with
Routes) to the fact that I get the problem, below only when I reload my
page. Clicking on links to go to the pages I want ... I seem not to
have problems.
Given that it seems to be a reload that is generating an "/undefined"
path somewhere ... can anyone suggest what I should be looking for to
fix the problem?
Processing ApplicationController#index (for 127.0.0.1 at 2010-02-04
16:53:40) [GET]
You are using warden. Does the issue occur without warden?
If not, the first thing you can do is to update to the latest version of
warden (0.9.0). If that doesnt solve the problem, maybe post an issue at
github if you feel it is warden related.
http://github.com/hassox/warden/issues
You are using warden. Does the issue occur without warden?
If not, the first thing you can do is to update to the latest version of
warden (0.9.0). If that doesnt solve the problem, maybe post an issue at
github if you feel it is warden related.
Issues · wardencommunity/warden · GitHub
Well ... I upgraded. Jeez, that was hard. Devise changed several of
its interfaces and it was a joy and a half tracking all(?) of them down.
Anyway ... same problem.
I have no idea how I would pull out warden and still have anything left
working.
So ... I'm gonna go heads down and learn FireBug and see what the hell
is going on.
You are using warden. Does the issue occur without warden?
If not, the first thing you can do is to update to the latest version of
warden (0.9.0). If that doesnt solve the problem, maybe post an issue at
github if you feel it is warden related.
Issues · wardencommunity/warden · GitHub
Well ... I upgraded. Jeez, that was hard. Devise changed several of
its interfaces and it was a joy and a half tracking all(?) of them down.
If you have comprehensive tests, then the tests tell you where things
changed.
If you don't have comprehensive tests, write some *now*, before you
write any more application code. Then get in the habit of doing all new
development test-first.
Anyway ... same problem.
I have no idea how I would pull out warden and still have anything left
working.
Stub the methods you need?
So ... I'm gonna go heads down and learn FireBug and see what the hell
is going on.
Firebug won't help unless this is a JavaScript issue, which it almost
certainly is not.
Well ... I upgraded. Jeez, that was hard. Devise changed several of
its interfaces and it was a joy and a half tracking all(?) of them down.
If you have comprehensive tests, then the tests tell you where things
changed.
If you don't have comprehensive tests, write some *now*, before you
write any more application code. Then get in the habit of doing all new
How would tests catch the fact that some Devise helper methods moved to
a new file any better than actually running the code?
The tests exercise the code for you. You can just run your whole test
suite and get a report on what broke where, rather than having to track
down all your method calls by hand. If you're using autotest, this is
done for you every time a file changes.
Developing without tests is fragile and negligent IMHO.
Ralph Shnelvar wrote:
So ... I'm gonna go heads down and learn FireBug and see what the hell
is going on.
Firebug won't help unless this is a JavaScript issue, which it almost
certainly is not.
FIrebug, apparently, has the ability to actually see the messages going
back and forth.
Firebug has the ability to see HTTP requests, but unless you're using
Ajax, this is of no use in your situation. You already get to see this
in the Rails logs.
I know you said it is a logging option ... but I can't find it.
Then read the logger docs. It's in there.
I'm at debug level ... and I can't tell when messages are being
triggered and wht the exact contents are.
Messages don't get triggered. What do you mean here?