On 7 Oct 2008, at 01:49, Robby Russell wrote:
> > On Mon, Oct 6, 2008 at 4:57 PM, Pratik <[EMAIL PROTECTED]> wrote: >> >> On Mon, Oct 6, 2008 at 9:31 PM, comopasta Gr >> <[EMAIL PROTECTED]> wrote: >>> I'm currently having the admin part of one of my apps accessible >>> by pure >>> username and password + role management checking. >>> >>> I was planning to add namespaces for it. Then I came accross this >>> (a bit >>> old but still...): >>> http://glu.ttono.us/articles/2006/08/30/guide-things-you-shouldnt-be-doing-in-rails >> >> That article is very old. I'd recommend namespacing controllers for >> something like admin panel. It has worked great for me. > > > Agreed. We use an /admin namespace on several of our really large > client projects. It works quite well. > > The only issue that we've really run into is with namespaces and model > names. Some weird stuff can happen (especially within tests) if you > have a namespace of Admin and a model named Admin. We've since used > Administrator to as an appropriate model name to distinguish the two. > Might that be weird stuff like it trying to resolve a constant like Admin::SettingsController by looking inside the Admin model class ? I've got apps with /admin namespaced controllers on several apps. Fred > Good luck! > > Cheers, > Robby > > -- > Robby Russell > Chief Evangelist, Partner > > PLANET ARGON, LLC > design // development // hosting > > http://www.planetargon.com/ > http://www.robbyonrails.com/ > aim: planetargon > > +1 503 445 2457 > +1 877 55 ARGON [toll free] > +1 815 642 4068 [fax] > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
