refinerycms-blog doesn't work if your Rails 3 application is called "blog" about refinerycms-blog

[joemsak]

hmmm... thanks for the note, we will definitely take this into consideration

[parndt]

Not sure how we could fix this,
What version of Refinery CMS are you using?

[benjackson]

It's no biggie really, but 'Blog' always has the potential for naming conflicts as a top-level module, especially if you're new to Refinery and you want to try creating a blog with it ;-)

I think the way around it would be to follow what you have done for the most part, nesting the Blog module inside the Refinery module, but making sure that happens everywhere; e.g. the categories controller uses Blog as a top-level module (Blog::CategoriesController), but could it work as Refinery::Blog::CategoriesController instead? Same goes for anywhere else Blog is used at the top level. I think that would solve it.

I'm using Refinery 1.0.0.

[parndt]

On Rails 3.1+ this will be Refinery::Blog::Whatever so will avoid many of the issues (once this engine is updated to comply).
Likely that will be in a 2.0 release.

[parndt]

This will be fixed in 2.0.0 by virtue of its namespacing