I have started with an extension that defines a route that is supposed to be visible only from the front-end of my Radiant site.
It provides a user authentication screen much like the back-end authentication screen and saves the user in a session. (Already disabled SiteController "sessions :off" line.) I am using the same user table as is used by Radiant. My plan is to change the default Radiant user table adding lower level privileges that do not allow such users to see the back-end interface. If this is too complicated, I may end up creating a separate table of external_users though that is not my preference. Ultimately, I will map several custom controllers for handling Rails CRUD interactions with the authenticated user--basically, a simple Rails app. Here's the route mapping I use: map.user_login 'user/login', :controller => 'user', :action => 'login' Anytime I type in "http://mysite.com/user/login"; I end up being redirected to the back-end login. If I login to the back end, THEN I am able to access this front-end login screen, but that's not the intended use. Any idea what part of Radiant is intercepting my request and redirecting it to the back-end login? -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
