Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rails generate refinery:[engine name] doesn't know how to build task to install migrations #2539

Closed
duarme opened this issue Feb 1, 2014 · 2 comments

Comments

@duarme
Copy link
Contributor

duarme commented Feb 1, 2014

Using refinerycms v 2.1.0, I just generated a portfolio engine with:

rails g refinery:engine work name main_image:image client description services --i18n name client description --namespace=portfolio

Then bundle install went fine, but rails generate refinery:works failed due to this error:

rake aborted!
Don't know how to build task 'refinery_works:install:migrations'

It worked after

cp vendor/extensions/works/lib/tmp/refinerycms-works.rb vendor/extensions/works/lib/refinerycms-works.rb

I don't know if this issue arises only when specifying a namespace, but if this is the correct procedure, it should be mentioned both on the generator output and the guides.

@parndt
Copy link
Member

parndt commented Feb 1, 2014

Out of interest, if you look in the new files, do they say:

module Refinery
  module portfolio
# etc

or do they say:

module Refinery
  module Portfolio

Thanks!

@parndt
Copy link
Member

parndt commented Feb 1, 2014

Never mind, I checked it out myself.. at least that part handles the capitalisation fine.. will keep looking.

@parndt parndt closed this as completed in 8f97a08 Feb 1, 2014
ugisozols added a commit that referenced this issue Feb 1, 2014
Fixes #2539 by checking if extension was specifically supplied as an option
keram pushed a commit to keram-refinery/refinerycms that referenced this issue Feb 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants