J Smith wrote: > > Hi all. > > I just finished upgrading a small Rails toy application to Rails 1.1 and > it seems that LoginEngine no longer works. I have upgraded the Engines > plugin using an svn checkout of the rel_1.1.0, and while the Engines > plugin seems to work fine (as does the UserEngine), the LoginEngine simply > doesn't do much of anything any more. > > For instance, if I try to login, I'm simply redirected back to the login > page, even though the username and password is correct. There are no > flashes or anything indicating a bad login. Upon a successful login, none > of the user information that would normally be stored in the session ends > up getting stored. Other forms, such as the forgotten password form, are > similarly broken. > > I tried messing around with the user_controller.rb, but any changes I make > are just ignored. In fact, purposefully inserting syntax errors into the > file or renaming it completely doesn't even seem to have any effect on the > situation. > > I have no idea why the controller is just being ignored outright. I can > make changes to the views and they appear fine, but it's like the > controller isn't even there. > > Anybody seeing anything remotely similar? > > If it helps, I'm using Ruby 1.8.4, Rails 1.1, Apache 1.3.34 and FastCGI > 2.4.0. I'm experiencing the problem both with FastCGI enabled and plain > ol' non-Fast-CGI. Engines, UserEngine and LoginEngine are all up-to-date > checkouts. > > Cheers. > > J
Well, I was able to get around this problem, but it seems that what I was experiencing was something similar to ticket #53. I ended up copying the contents of user_controller.rb from UserEngine and pasted it into the user_controller.rb script for LoginEngine and moved the UserEngine file out of the way. Now everything seems to work. Is this a legitimate bug, or am I doing something ridiculously wrong? I have checked and re-checked my configuration and removed and reinstalled the Engines, UserEngine and LoginEngine several times, but this was the only way I could get everything to work properly again. There seems to be something screwy with how Engines is doing the overriding of the controllers, as if methods were being ignored or something. Am I alone in seeing this? I guess that would indicate that I'm the problem here and not Engines, but I've exhausted my debugging ability to come up with this workaround... J _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
