From 2a2fcca64972bc2fb6a3530395366fb2ade42303 Mon Sep 17 00:00:00 2001 From: Philip Arndt Date: Tue, 10 Jan 2012 17:19:28 +1300 Subject: Isolate this engine to Refinery::Blog (which, according to my interpretation of the docs, is how it should be) and remove url hack now that resolve/refinerycms#1193 has been fixed. --- lib/refinery/blog/engine.rb | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) (limited to 'lib') diff --git a/lib/refinery/blog/engine.rb b/lib/refinery/blog/engine.rb index aa8ffe4..cd764e3 100644 --- a/lib/refinery/blog/engine.rb +++ b/lib/refinery/blog/engine.rb @@ -3,7 +3,7 @@ module Refinery class Engine < Rails::Engine include Refinery::Engine - isolate_namespace Refinery + isolate_namespace Refinery::Blog engine_name :refinery_blog initializer "register refinerycms_blog plugin", :after => :set_routes_reloader do |app| @@ -13,13 +13,7 @@ module Refinery plugin.url = app.routes.url_helpers.refinery_admin_blog_posts_path plugin.menu_match = /refinery\/blog\/?(posts|comments|categories)?/ plugin.activity = { - :class_name => :'refinery/blog/post', - - # Workaround bug #1193 in refinerycms. - # Without this line, the route fragment generated by the Refinery's - # activity dashboard would be refinery_blog_admin_blog_posts_path, - # which does not exist. - :url => "refinery_admin_blog_post_path" + :class_name => :'refinery/blog/post' } end end -- cgit v1.2.3