creating subdirectories inside the controller directory is just gonna create problem some time or another. I'm not surprise to see this problem.

On 9/24/06, Michael Koziarski <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I'm still battling this one and am yet unsure whether this is a bug or not.
> It would be great if someone could put me out of my misery  and confirm
> whether this is bug or not?
>
> With the latest testing to characterise the problem it seems to be something
> to do with (a) controllers a sub-directory down &/or (b) url_for usage in a
> layout perhaps.  That is in the sense that I have a "url_for" which resolves
> find when the context is one controller but throws an error when in the
> context of another.

If you want your url_for calls to work from both the top level, and
controllers in modules,  you need to use:

:controller=>'/the_controller'

Otherwise it assumes it's a relative link and generates links
accordingly.   Another (simpler) option is just to use a named route.



--
Cheers

Koz

gcc -O0  -DRUBY_EXPORT   -rdynamic -Wl,-export-dynamic -L.   main.o  -lruby-static -ldl -lcrypt -lm   -o ruby
Everyone is trying their hardest to do their job but management has set it up so that it's impossible.
Take the control over your money, track your expenses http://justbudget.com

Mathieu
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core
-~----------~----~----~----~------~----~------~--~---

Reply via email to