I haven't tried the layout suggestion, I'm not sure I understand what to 
do with it.
Here is what I'm trying to do. I have my own controller called called 
say 'mike'.  All my pages need to have a header even if users are not 
logged in.  On the home page I need to display the header and below it 
the login screen.  Once they log in they should see the entire page 
including the header which will always be there.
I have tried using <%= render_component(:controller => 'user', :action 
=> 'login') %> at the bottom of my _header.rhtml, this shows the login 
screen where I want it but when I click on login button or Register for 
an account | Forgot my password links, it complains that it can't find 
action mike/login, why did the login screen all of the sudden pickup my 
controller name instead of using user/login.  I can change the links to 
point to the user controller but not the login button.  After a while of 
reading the Engines documentation and other wikis, I created an 
app/views/user directory and put login.rhtml there, created an empty 
user_controller.rb in my app/controllers directory.  Then something 
strange started happening all all pages render as blank and I get like 
20 pages of errors in my webrick window, I can't even see the top most 
message because there are so many errors.  Not sure why that happened. 
For now I'll just stick with putting a link to the user/login screen and 
users will go to that plain login page and then be routed back to my 
page.  I have also tried putting the user/login page as the first page 
and attaching my header to the top of it but I can't find the header 
because it's not in the views/user/ directory.
So far the login_engine works great for me with the exception of being 
able to include it inside my own views.  I probably need to read up and 
experiment more with it.
Thanks for your help.
Mike

-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
engine-users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org

Reply via email to