heroku pre-compiling assets now fails about refinerycms-page-images HOT 11 CLOSED

I think that this gem does something naughty with the database upon initialize (like accessing a model,etc) that prevents the config.assets.initialize_on_precompile = true case working.

from refinerycms-page-images.

Sorry for terseness, but here's a quick fix: https://devcenter.heroku.com/articles/labs-user-env-compile

from refinerycms-page-images.

Yeah; I understand why you're doing it. :-)

Please see refinery/refinerycms#1751

from refinerycms-page-images.

@robyurkowski that was a quick fix: https://devcenter.heroku.com/articles/labs-user-env-compile
@parndt I think you are answering a comment I quickly deleted because I realized that I misread your original comment. =]

from refinerycms-page-images.

was this ever resolved? I'm still seeing this issue on

gem "refinerycms-page-images", :git => "git://github.com/resolve/refinerycms-page-images.git", :branch => "2-0-stable"

from refinerycms-page-images.

Did you enable user-env-compile?

from refinerycms-page-images.

I just did, and it worked.

However, it's not clear to me what the actual root of the problem is however.

The only config/vars I added for this gem was my s3 configuration (keys/bucket/etc) -- and I don't know why it'd be needed during asset pre-compilation.

If "that's just the way it is" I think this would be important to put in the readme to save everyone a few minutes of their life.

from refinerycms-page-images.

Sure, could you please send a pull request? It's just the way it is with Heroku and this extension, unfortunately.

from refinerycms-page-images.

Fixed by #85

from refinerycms-page-images.

@parndt How is this issue fixed now that Heroku has deprecated user-env-compile?

from refinerycms-page-images.

@LoganDSPrice have you encountered the issue?

from refinerycms-page-images.