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

ImportError: 'module' object has no attribute 'DataJsonPlugin' #36

Open
pck3152 opened this issue Mar 8, 2017 · 4 comments
Open

ImportError: 'module' object has no attribute 'DataJsonPlugin' #36

pck3152 opened this issue Mar 8, 2017 · 4 comments

Comments

@pck3152
Copy link

pck3152 commented Mar 8, 2017

Update: I was using an older clone of datajson, upon update and rebuild the "DataJson" error was fixed, but the "DataJsonHarvester" error in the following comment is still an issue. The noted fix when using WSGI does not resolve the issue.

I am getting the following error when datajson plugin is enabled. I can provide more information if needed.
err.datajson.txt

CKAN version 2.6.0
OS: CentOS 7
Python 2.7
Setuptools 30.0.0

I believe another individual is getting a similar error for 'DataJsonHarvester'. He is running ubuntu.

@ranjayshrestha
Copy link

I am also getting similar error after adding the datajson harvester.
[error] [client 127.0.0.1] ImportError: 'module' object has no attribute 'DataJsonHarvester'
Attached is the detail error log.

CKAN version: 2.5.2
OS: Ubuntu 12.04
Python: 2.7.12

DataJasonHarvesterErrorLog_3_8_2017.txt

Any help is appreciated.
Thanks

@theresaanna
Copy link

Can this be reproduced? Is it still an issue?

@inghamn
Copy link

inghamn commented Aug 16, 2018

I have this same problem when attempting to upgrade to CKAN 2.8.0

After installing CKAN, harvest, and datajson, this error occurs when trying to run the database updates.
My error log is pretty much the same.
out.txt

Our full installation process is done using Ansible:
https://github.com/City-of-Bloomington/ckan-deploy

@inghamn
Copy link

inghamn commented Aug 16, 2018

Merging in newer changes from upstream resolved this for me.

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

No branches or pull requests

5 participants