one quick and dirty way to fix controller problems like these is to
include the “/” in the beginning of your RAILS methods.
normally you may have
link_to :controller => “admin/main”, :action => “do_something”, :id =>
This would be changed to
link_to :controller => “/admin/main”, :action => “do_something”, :id =>
and that forces the routing to start at the root.
hope that helps
Anton A. wrote:
Philip H. said the following on 02/09/2007 06:02 PM:
controller in my admin area.
I’m having a similar-but-different problem.
I’m working on a wiki with webs (books in i2 parlance), so the normal
(do I use “:requirements” to make sure?)
so the admin interface for doing things that the normal wiki user can’t
http://sitename.com/admin/web for the list
http://sitename.com/admin/web/Web for a specific web
http://sitename.com/admin/web/Web/WikiWordTopic for a specific topic
and drill down for its attributes.
Yes, I still have things to sort out like what the urls are for
the user to login and return to the access controlled topic (or is that
via cookies), edit a topic … and of course what all that looks like in
Philip could you post the line from your routes.rb, please, to
If you move the controllers to app/controllers/admin do you have to
Or, to ask it all another way, is there a different way to
both the code and the URL?
(such as …/do_something/1?admin perhaps)
If the box says ``Windows 95 or better’’, it should run on Linux, right?
(Seen on Usenet)