Comments on: Rails 1.2 impact on Ajuby release 0.4 http://www.savedmyday.com/2007/02/10/rails-12-impact-on-ajuby-release-04/ Fri, 30 Jul 2010 03:23:39 +0000 http://wordpress.org/?v=2.5 By: Rajesh Shetty http://www.savedmyday.com/2007/02/10/rails-12-impact-on-ajuby-release-04/#comment-380 Rajesh Shetty Wed, 07 Mar 2007 19:09:00 +0000 http://www.savedmyday.com/?p=76#comment-380 I did this fix provided by "cedric" and this fix has been posted in quite a few places but it never worked for me. I guess even if it works, my idea is to avoid moving out any code from Theme extension files to Rails routes code, with that we are cluttering routes.rb with your custom plugin routes and that is not a smart solution but its a good hack. <br/> In fact I have found the solution that will work with Rails 1.2.X without moving anything out of Theme support code. I have posted the fix in this link <br/><br/>http://www.ruby-forum.com/topic/100163#215694<br/><br/><br/>I'm also posting the fix here<br/><br/># Go to vendor/plugins/theme_support/lib/patches/routeset_ex.rb<br/># Replace "draw" method with following<br/><br/> def draw<br/> clear!<br/> create_theme_routes<br/> yield Mapper.new(self)<br/> named_routes.install<br/> end<br/><br/># In create_theme_routes method<br/> - replace named_route with add_named_route<br/> - replace connect with add_route<br/><br/>So your create_theme_routes should look like this<br/><br/> def create_theme_routes<br/> add_named_route 'theme_images', "/themes/:theme/images/:filename",<br/>:controller=>'theme', :action=>'images'<br/> add_named_route 'theme_stylesheets',<br/>"/themes/:theme/stylesheets/:filename", :controller=>'theme',<br/>:action=>'stylesheets'<br/> add_named_route 'theme_javascript',<br/>"/themes/:theme/javascript/:filename", :controller=>'theme',<br/>:action=>'javascript'<br/><br/> add_route "/themes/*whatever", :controller=>'theme',<br/>:action=>'error'<br/> end I did this fix provided by “cedric” and this fix has been posted in quite a few places but it never worked for me. I guess even if it works, my idea is to avoid moving out any code from Theme extension files to Rails routes code, with that we are cluttering routes.rb with your custom plugin routes and that is not a smart solution but its a good hack.
In fact I have found the solution that will work with Rails 1.2.X without moving anything out of Theme support code. I have posted the fix in this link

http://www.ruby-forum.com/topic/100163#215694

I’m also posting the fix here

# Go to vendor/plugins/theme_support/lib/patches/routeset_ex.rb
# Replace “draw” method with following

def draw
clear!
create_theme_routes
yield Mapper.new(self)
named_routes.install
end

# In create_theme_routes method
- replace named_route with add_named_route
- replace connect with add_route

So your create_theme_routes should look like this

def create_theme_routes
add_named_route ‘theme_images’, “/themes/:theme/images/:filename”,
:controller=>’theme’, :action=>’images’
add_named_route ‘theme_stylesheets’,
“/themes/:theme/stylesheets/:filename”, :controller=>’theme’,
:action=>’stylesheets’
add_named_route ‘theme_javascript’,
“/themes/:theme/javascript/:filename”, :controller=>’theme’,
:action=>’javascript’

add_route “/themes/*whatever”, :controller=>’theme’,
:action=>’error’
end

]]> By: Anonymous http://www.savedmyday.com/2007/02/10/rails-12-impact-on-ajuby-release-04/#comment-379 Anonymous Mon, 26 Feb 2007 22:21:00 +0000 http://www.savedmyday.com/?p=76#comment-379 You can also use the fix mentioned by 'cedric' here:<br/><br/><a HREF="http://agilewebdevelopment.com/plugins/theme_support" REL="nofollow">http://agilewebdevelopment.com/plugins/theme_support</a><br/><br/>This entails just moving and reformating the named routes in routeset_ex.rb into config/routes.rb. You can also use the fix mentioned by ‘cedric’ here:

http://agilewebdevelopment.com/plugins/theme_support

This entails just moving and reformating the named routes in routeset_ex.rb into config/routes.rb.

]]>