I haven't had a chance to work on fixing multiple controller view paths recently. My original patch attempt was: http://dev.rubyonrails.org/ticket/8582
It was rejected due to the fact that it was fixing the symptom more than the problem. However, I think it's critical that this problem get fixed, otherwise the whole concept of view_paths is severely neutered and doesn't even live up to the use case advertised in the announcement on the official blog (ie. productization). The way view_paths currently work is only suitable as a sort of half-measure towards providing Engines functionality. That's a worthy goal, but I think the ability to modify view_paths per-request is at least as important if not more so. I will try to find time to work on a better patch, but I want to make sure this gets into Rails 2.0 because we don't want to support a broken interface later. How close are we to an RC? -- Gabe da Silveira http://darwinweb.net --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
