Skip to content

Instantly share code, notes, and snippets.

--- a/lib/scaffolding_extensions/controller/ramaze.rb 2010-08-26 06:18:19.000000000 +0200
+++ b/lib/scaffolding_extensions/controller/ramaze.rb 2010-08-26 15:44:50.379829006 +0200
@@ -94,12 +94,30 @@
def scaffold_setup_helper
engine :Erubis
layout(:layout){|name, wish| !request.xhr? }
-
- o = app.options
- o.roots = [scaffold_template_dir]
- o.views = ['/']
--- a/lib/scaffolding_extensions/controller/ramaze.rb 2010-08-26 06:18:19.000000000 +0200
+++ b/lib/scaffolding_extensions/controller/ramaze.rb 2010-08-26 12:31:23.438577289 +0200
@@ -96,10 +96,18 @@
layout(:layout){|name, wish| !request.xhr? }
o = app.options
- o.roots = [scaffold_template_dir]
- o.views = ['/']
- o.layouts = ['/']
-
With the last fixes, scaffold_extensions work for this example, but override layout of the other Ramaze::Controller in the same Ramaze::App
- /foo should use /layout/foo.xhtml as layout, and be renderer an a gray background
- /f/forum should use /layout/foo.xhtml as well
The problem seems to be linked to the fact the Ramaze adapter now updates the *existing containing Ramaze::App* with its own path (here, default one and :forum) and affect as such any other controller in theses Apps.