# \[ANN\] Engines plugin 1.0.6 **URL:** \ **Category:** Engines\ **Created:** [January 31, 2006, 6:01pm UTC](https://www.ruby-forum.com/t/ann-engines-plugin-1-0-6/99486 "2006-01-31T18:01:03Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![nitr0z](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/ba9def/32.png) [@nitr0z](https://www.ruby-forum.com/u/nitr0z)\ **Post date:** [January 31, 2006, 6:01pm UTC](https://www.ruby-forum.com/t/ann-engines-plugin-1-0-6/99486/1 "2006-01-31T18:01:03Z")
Greetings folks: A new version of the Engines plugin is now available. As always, you can find it at: [http://opensvn.csie.org/rails\_engines/plugins/engines](http://opensvn.csie.org/rails_engines/plugins/engines) (the default which will be picked up by script/plugin) [http://opensvn.csie.org/rails\_engines/engines/tags/rel\_1.0.6](http://opensvn.csie.org/rails_engines/engines/tags/rel_1.0.6) _ **Note for Edge Rails users** _ Sorry guys, this still isn’t for you. Tis the price of living on the bleeding edge! If we can sign off the controllers in modules issue below, I’ll have more time to merge this stuff into the edge branch. ## Highlights !!! CONTROLLERS AND MODULES !!! The biggest issue with Engines at the moment is ensuring that you can controllers within modules are being properly loaded. Because Rails’ dependency mechanism changes, this is a bit of a moving target. Anyway - this release should hopefully fix it for most people. If you are STILL having issues, please checkout the engines\_test application (see below), run the tests and report back to me. If I can close the ticket on this bug (#53), I will get much better sleep. Please, if you can, test this. VERSIONS! You can now quickly find the version information for your installed engines (note not all engines will provide this information at present. I’ll update the login/user engines soon). Try: rake engine\_info or rake engine\_info ENGINE=login # although this won’t give much information, yet LOGGING! You can now isolate the Engine logging so that your development/production.log doesn’t get filled with spurious engine messages. Try: Engines.create\_logger Engines.log.debug “Hi!” ENGINE\_MIGRATE! Should now work. Stupid paths. TESTS! Since the Engines mechanism itself can be tricky to test, I’ve created a special test application which people should be able to check out and use to test Engine behaviour on their own system. You can find this at: [http://opensvn.csie.org/rails\_engines/applications/engines\_test](http://opensvn.csie.org/rails_engines/applications/engines_test) … with more details in the README in it’s /doc folder. MANY OTHER LITTLE FIXES! With the greatest appreciation for all your bug reports and assistance. You guys rock. . ## CHANGELOG ``` * Added ability to determine version information for engines: rake ``` engine\_info \* Added a custom logger for the Engines module, to stop pollution of the Rails logs. \* Added some more tests (in particular, see rails\_engines/applications/engines\_test). \* Another attempt at solving Ticket 53 - controllers and helpers should now be loadable from modules, and if a full path (including RAILS\_ROOT/ENGINES\_ROOT) is given, it should be safely stripped from the require filename such that corresponding files can be located in any active engines. In other words, controller/helper overloading should now completely work, even if the controllers/helpers are in modules. \* Added (finally) patch from Ticket 22 - ActionMailer helpers should now load \* Removed support for Engines.start :engine, :engine\_name =\> ‘whatever’. It was pointless. \* Fixed engine name referencing; engine\_stylesheet/engine\_javascript can now happily use shorthand engine names (i.e. :test == :test\_engine) (Ticket 45) \* Fixed minor documentation error (‘Engine.start’ ==\> ‘Engines.start’) (Ticket 57) \* Fixed double inclusion of RAILS\_ROOT in engine\_migrate rake task (Ticket 61) \* Added ability to force config values even if given as a hash (Ticket 62) – - J \* ~ ---
**Author:** ![nitr0z](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/ba9def/32.png) [@nitr0z](https://www.ruby-forum.com/u/nitr0z)\ **Post date:** [January 31, 2006, 11:48pm UTC](https://www.ruby-forum.com/t/ann-engines-plugin-1-0-6/99486/2 "2006-01-31T23:48:28Z")
I see, Edge doesn’t work. Sad, but happens. Anyway, I just downgraded to only the login\_engine (and to rails stable), as my role-structure is not very complex anyway (only three roles, and incremental). I really do like the login\_engine. I just wanted to say thank you very much ! Keep up the great work! Also I have a little wonder. What is the role field used for in the login\_engine ? (I can’t find the role field anywhere but in the database schema’s). Is it to stay ? Wybo ---
**Author:** ![nitr0z](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/ba9def/32.png) [@nitr0z](https://www.ruby-forum.com/u/nitr0z)\ **Post date:** [January 31, 2006, 11:54pm UTC](https://www.ruby-forum.com/t/ann-engines-plugin-1-0-6/99486/3 "2006-01-31T23:54:32Z")
On 1/31/06, Wybo W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Also I have a little wonder. What is the role field used for in the > login\_engine ? (I can’t find the role field anywhere but in the database > schema’s). Is it to stay ? It will get factored out in the next login\_engine release - it was a part of the SHLG schema, I just never had the chance to remove it 🙂 – - J \* ~