Community Forums

1. 

   pythonguy
   Member
   Posted 13 years ago

   Hi there,

   I'm new to the MediaCore scene, but not so new to deploying Python sites. I've got MediaCore up and running behind mod_wsgi inside a virtualenv just fine (used the 'python setup.py develop' method, but I can't seem to get it to recognize the plugins I've installed. I downloaded/unzipped the SEO 0.9.0b1 plugin to /PATH/TO/VIRTUALENV/src/GITHUB_CLONE/mediacore/plugin/MediaCore-SEO-0.9.0b1/

   When I change to that directory and run 'python setup.py (install|develop)', the output looks completely normal. When my virtualenv is activated, I can 'import mediacore_seo'. I've enabled logging at the DEBUG level for the 'mediacore' root logger, so I can see when plugins are loaded, and the relevant lines in my logfile show no plugins loaded.

   Any ideas what's going on here?
2. 

   Nathan Wright
   Maintainer
   Posted 13 years ago

   Put the plugin adjacent to MediaCore, not inside it. I think that should do it.
3. 

   pythonguy
   Member
   Posted 13 years ago

   Hmm, didn't work.

   >>> import mediacore_seo
   >>> mediacore_seo.__file__
   '/home/myuser/virtualenvs/my_mediacore/src/MediaCore-SEO-0.9.0b1/mediacore_seo/__init__.pyc'

   So now it lives as a sibling to the mediacore source, and is again importable (after a setup.py install), but still no plugins are found...

   [Tue Apr 12 15:42:42 2011] [error] 15:42:42,961 DEBUG [mediacore.plugin] [MainThread] Initializing plugins
   [Tue Apr 12 15:42:42 2011] [error] 15:42:42,991 DEBUG [mediacore.plugin] [MainThread] App wrapped
   [Tue Apr 12 15:42:42 2011] [error] 15:42:42,993 DEBUG [mediacore.plugin] [MainThread] Public paths: {}
4. 

   Nathan Wright
   Maintainer
   Posted 13 years ago

   This is bizarre... I just made a fresh virtualenv, cloned our github repo, downloaded MediaCore-SEO-0.9.0b1.tar.gz and installed it and worked fine. Here's the steps I took... you could try using setup.py develop instead of install.

   virtualenv --no-site-packages env
   source env/bin/activate
   mkdir env/src
   cd env/src
   git clone git://github.com/mediacore/mediacore.git MediaCore
   wget http://mediacore.com/files/MediaCore-SEO-0.9.0b1.zip
   tar xzvf MediaCore-SEO-0.9.0b1.tar.gz
   cd MediaCore
   python setup.py develop
   cd ../MediaCore-SEO-0.9.0b1
   python setup.py develop
   cd ../MediaCore
   paster serve --reload development.ini
5. 

   pythonguy
   Member
   Posted 13 years ago

   I agree, bizarre.

   The only difference between what I did and what you did, is that I'm using Apache/mod_wsgi to serve it up. I realize it's probably too much of a pain to set that up to test this one bug out, but I just wanted to point out the only difference I'm aware of.

   I'm going to get started installing it all over again. Yay.
6. 

   Nathan Wright
   Maintainer
   Posted 13 years ago

   We're using plugins with Apache/mod_wsgi without any problems, so I think something else must've gone wrong. It might be worthwhile running the paster server just as a simple command line test to see if the plugin loads then, as unlikely as it seems..
7. 

   pythonguy
   Member
   Posted 13 years ago

   Well now I'm befuddled.

   paster serve --reload development.ini

   ...works for me, too (with my original setup).

   Now to figure out what mod_wsgi is missing.
8. 

   pythonguy
   Member
   Posted 13 years ago

   Adding the following to my mediacore.wsgi file fixed it:

   import site
   site.addsitedir('/home/myuser/virtualenvs/my_mediacore/lib/python2.7/site-packages/')

   It's something I've done countless times with my other mod_wsgi apps, I don't know why I assumed MediaCore would be any different. Thanks for sticking with me even after it was clear the problem wasn't on your end ;-)

RSS feed for this topic

Reply

You must log in to post.