Mount Refinery::Core::Engine, :at => '/refinery'įind me in app/views/static/ Match '/mktgeistuser/sign_up', :action=>"new", :controller=>"devise/registrations" Match '/mktgeistuser/sign_in', :action=>"new", :controller=>"devise/sessions" Match '/mktgeistuser/sign_out', :action=>"destroy", :controller=>"devise/sessions" Then I added a static page where to put the login/logout links to test and added the following routes:ĭevise_for :mktgeistuser, :controllers=> do The problems starts when I go on and create the new kind of users:Ĭreate db/migrate/20121019201721_devise_create_mktgeistusers.rb Which creates everything as it should be. Refinerycms testRefineryPlusDevise -d mysql The next step was to create a brand new Refinery installation by doing the following: So I created first an application without refinery (only with devise) to make sure that everything works (from the authentication side). I want to keep separate Refinery users and other kind of users, call them mktgeistusers that will need to register and login in order to access to some protected pages. I'm trying to use Refinery as CMS for an application. "I have a problem that doesn't seem so difficult at first, but actually I can't solve.
0 kommentar(er)
