[ckan-dev] Help with understanding plugin not found

Thu Jan 19 19:41:48 UTC 2017

Hi Timothy,

How do you normally 'install' an extension? You have the code locally and
run `python setup.py install`? Or `python setup.py develop`? Or...?
Also, are you sure you have the CKAN virtualenv enabled when installing
plugins, by doing `. /usr/lib/ckan/default/bin/activate.sh` or similar?

Cheers,
Carl

On Thu, 19 Jan 2017 at 18:05 Timothy Giles <timothy.giles at slu.se> wrote:

Hi all,

So two of my teams development environments have recently suffered from
being unable to use newly created extensions. So, our base build of CKAN
includes 20 odd extensions and works well in both development, test and
production. The two development VMs in question both complain when a new
extension is either created (ie. using the paster create template command)
or I copy paste an existing extension and copy replace in setup.py and
plugin.py.

So, the issue is definitely not a lack of understanding and implementation
of getting the plugin name correct, consistent etc... Even a newly created
extension is giving the same error. Even if disable all extensions bar the
new one - it still complains. And - today - we installed a 3rd part
extension (I forget which one) - so it does not seem to be just my groups
extensions. And to reiterate, the mix of home grown and community plugins
already in and working (around 20) work a treat.

Is there anything else I can check on these VMs. I dont really have the
time to completely reload them - and I am sure someone with a bit more
experience of CKAN development can help point me at a file or directory or
config file somewhere that might help provide some answers.

Thanks in advance

Tim
_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org
https://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

-- 
Cheers,
Carl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20170119/5b66bd20/attachment-0003.html>