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

Error when adding a new work #3012

Open
scholarworks opened this issue Jan 11, 2017 · 7 comments
Open

Error when adding a new work #3012

scholarworks opened this issue Jan 11, 2017 · 7 comments
Labels
Milestone

Comments

@scholarworks
Copy link

Descriptive summary

On a fresh install with the following gems

gem 'sufia', github: 'projecthydra/sufia', branch: 'master'
gem 'flipflop', github: 'jcoyne/flipflop', branch: 'hydra'
gem 'hydra-role-management'

I am getting an error saving a new work:

https://gist.github.com/scholarworks/c374d29ed7fe75c9870926c3de786d35

screenshot 2017-01-11 12 20 33

@jcoyne
Copy link
Contributor

jcoyne commented Jan 11, 2017

Have you tried restarting your dev server? Could this be an error when autoloading after making a change in one of the gems?

@scholarworks
Copy link
Author

@jcoyne - Yeah, I'm getting this after a restart on a fresh install. Just restarted again. Haven't changed any gems past the initial install.

@mjgiarlo
Copy link
Member

FWIW, we've seen this in Sufia ever since we based it atop CC, but I've only ever seen it in development mode. Try the production environment, or Hyrax. ;)

@scholarworks
Copy link
Author

@mjgiarlo - yeah, this is in development - haven't set the environment to production yet. Will work on that soon as well, but sticking with development during testing/demos has been a lot easier than production. Thanks.

@scholarworks
Copy link
Author

@mjgiarlo - Confirmed I do not see this when running in the production environment. Which I would guess means it's not a blocker, but should still be addressed if possible as it's a pain when getting started.

@mjgiarlo
Copy link
Member

Thanks, @scholarworks!

@jcoyne
Copy link
Contributor

jcoyne commented Jan 25, 2017

I wonder if switching require 'curation_concerns' to require_dependency 'curation_concerns' would fix this problem. See http://apidock.com/rails/ActiveSupport/Dependencies/Loadable/require_dependency

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants