Hi Michael, This was a result of the fact that plugins can be 'enginized' as part of the plugin loading process now, which occurs before routing is started up. Previously this wasn't an issue because Engines.start was called after routing was configured. There's a fix in the release branch; see http://dev.rails-engines.org/tickets/258 for more details.
Documentation is forthcoming; for the moment, your best bet is to get familiar with the source code. I'm posting details about the new behaviours/features at http://rails-engines.org and http://interblah.net. - James On 1/5/07, Michael Moen <[EMAIL PROTECTED]> wrote: > > On Jan 3, 2007, at 7:39 AM, James Adam wrote: > > > ... which means things are going to break if your running the Rails > > 1.2 release candidate. You can find the new 1.2 release branch here: > > > > http://svn.rails-engines.org/engines/branches/rb_1.2 > > James- I grabbed the 1.2 engines plugin and Edge Rails, but I'm not > sure where to look for Docs related to the new versions. > > I have a simple plugin that I want to setup to work with Engines or > the appable_plugin (not sure if this one does views). The > appable_plugin works if I manually put the views in place, but with > Engines all I get are routing errors. I'm sure I'm missing something > simple, but I'm not sure where to look with all the new changes. > > Thanks in advance for your time. > > Michael- > > _______________________________________________ > 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
