ENHANCEMENT Ticket (pending)

Plugin layout overrides app layout : difficult to integrate properly the plugin in an existant application

As there's a default.ctp file in the plugin layout's directory, it's not actually possible to integrate properly (= with same design) the api_generator as a module in an existant application, without modifying his layout. I think it would be better to include the .js, .css and menus directly in the views (not inline), in order to delete default.ctp. Integration with existing dev environnement would be better ! For an example, we actually have a dev environment, with functionnals tests, user documentation wiki, unit tests reports, and API doc, in the same app (so with the same menu in every pages, same design, etc ...). We just want all our plugins to use the same design and navigation schema ! Thanks a lot for your answer :-) Sébastien Charrier
on 02.27.09 reported by: scharrier owned by: mark_story
on 02.27.09 by scharrier
- **title** was changed to _Plugin layout overrides app layout : difficult to integrate properly the plugin in an existant application_
on 02.28.09 by mark_story
You can just delete the layout as well, it will default to using the next default.ctp it order. You just loose the search element and navigation in doing so. Since both of these elements are 'layout' level elements, I made a layout so I could include them. I don't really know how it would work in a layout-less mode. Perhaps you can explain?