In Bart's case it was because his routes were grabbing the url parameters and not passing them to the appopriate controller, and his last post describes an adequate fix. Engine or not, every controller would have to be explicitly 'noted' in the routes file to avoid being interprettetd as a 'book_url_name' parameter.
So - it's not really a bug in the engine. It's the fact that you have a set of routes which supercedes the typical :controller/:action/:id default in such a complete way that ANY controller needs to be handled as a special case. Perhaps the Riki/Wiki engine route documentation might be clearer about this, and I'm sure that patches to such documentation will be greatly appreciated. - james On 2/16/06, Ryan Tate <[EMAIL PROTECTED]> wrote: > This infinite loop happened to me too. It's clearly a bug in the > engine. If you want to wall off people from /login by default, that's > fine, if strange. But then don't redirect them there if they don't > have permissions. > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org > -- * J * ~ _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
