Forum: Rails Engines Engines 1.2 experimental branch is now the release branch

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2007-01-03 16:40
(Received via mailing list)
... 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:

If you *must* maintain compatibility, use the following SVN URL to
access to old 1.2 release:

It's worth mentioning now that the current releases of the login and
user engines will also not work with the new 1.2 branch for the
moment. While I've tried to avoid change wherever possible, to fit
better with Rails 1.2 the next release of Engines is a different beast
- hopefully the advantages of the new codebase outweighs the hiccup of
bringing your plugins into sync.

Developers, please examine the code to find out how to make your
plugins compatible; I'll be posting more in the very near future
describing the changes in detail - feedback gratefully requested!

1ed9cf3ba6dca9248d79d03f77de79ea?d=identicon&s=25 Daniel =?ISO-8859-1?Q?V=F6lkerts?= (Guest)
on 2007-01-03 18:57
(Received via mailing list)
Hi James,

thanks a lot for your reply. Great Work!


14619cc9314db27483a304b4dd323f3b?d=identicon&s=25 Michael Moen (Guest)
on 2007-01-06 19:30
(Received via mailing list)
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:

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.

05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2007-01-19 16:30
(Received via mailing list)
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 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 and

- James
This topic is locked and can not be replied to.