hi! I'm migrating to Rails 1.2.1 (from 1.1.6), but now I'm getting a 404 (Not Found) page for every url I call! Not even the error messages I got before are shown on this page anymore. So I took a look into development.log, but there everything is ok, WebRick sends Http 200 OK. The routes.rb I left as the standard: map.connect ':controller/:action/:projectid' And I call http://localhost:3000/project/list/1, which works, but I don't see the result, I get a Not Found! Thanks for your help.
on 2007-01-28 17:15
on 2007-01-28 22:54
I see the same thing in 1.2.1. In firefox I see a page that says only "You are being redirected" with a link that points to my logon page (a redirect_to in the code). In IE 7, I saw only 404's. I just rolled back using "gem uninstall rails" and now my app is happy again. I got to the 404 problem only after a bunch of other painful migration work. At first in Rails 1.2.1 on Windows, my previously working app first would kill the webserver unless I used config.cache_classes = false in development.rb. No useful error messages at all. I got things running again by removing all areas of my app (models, plugins, libs, helpers), and adding them in one by one (I was unsure exactly where the problem was). The Selenium on rails plugin seems to have been the culprit and I suspect it is related to the new require rules, but I haven't nailed down the file and line and won't be looking at 1.2.1 again for quite some time. Once I got server to run, I still had the problem above. Please let me know what you find if you resolve the 404 problem. Also, are you using IE or Firefox? In other words, does your experience match mine? Good luck! Eric
on 2007-01-29 11:09
I see the error in Firefox and IE. I'm switching the Rails version in environment.rb with RAILS_GEM_VERSION = '1.2.1', which brings up that error. The strange thing is, the routing seems to work, because the action is being executed. But somehow the rhtml is not being compiled, but the 404 page. Alright, it seems to be a common problem, so I'll wait and use the old version.
on 2007-02-01 05:03
Did you at some point use the salted hash login generator on your app? I had. It uses @request which is now gone and replaced by simply "request". I thought I had cleaned out all the deprecations from my code, but apparently not. So search for all deprecated items in your code, like @request and @session. For me, it was blowing up because I missed an @request in user_system in the area where the redirect occured. I also had extended kernel with a debug function of my own making. This seemed to have been an issue for me as well. Dependencies.rb did not seem to like that very much. Now I seem to be running ok. Good luck! Eric