Awesome, worked like a charm, Thank you! You know, I *thought* I tried this but I think I didn't do something right in importing the paths before so when I read it I thought well let me try it once more. I was also half asleap last night trying to get it to work... I should learn that coding while half asleap is usually bad news. -Chris
On Jan 10, 11:43 am, Daniel Roseman <dan...@roseman.org.uk> wrote: > On Jan 10, 3:28 pm, flynnguy <flynn...@gmail.com> wrote: > > > > > So I'm trying to implement tagging on my website and I found the > > django-tagging project and threw it in my app and it works great... on > > my laptop. Go to put things up on the server (dreamhost using their > > new passenger method) and started to run into some issues. I did easy > > install using --prefix so I could install it in my home directory. My > > structure looks something like this: > > ~/django > > |--applications > > | `-- pythonlib > > | `-- lib > > | `-- python2.4 > > | `-- site-packages > > | `-- django_tagging-0.3-py2.4.egg > > | |-- EGG-INFO > > | `-- tagging > > | |-- templatetags > > | `-- tests > > |--projects > > |--source > > > source is my copy of the Django source code and then projects is where > > I keep my application souce code. Also, in order to get it to install, > > I had to put the site-packages path in my PYTHONPATH in .bash_profile: > > export PYTHONPATH=$PYTHONPATH:$HOME/django/source:$HOME/django/ > > projects:$HOME/django/applications/pythonlib/lib/python2.4/site- > > packages > > > So far so good: > > $ python manage.py shell > > Python 2.4.4 (#2, Oct 22 2008, 20:20:22) > > [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2 > > Type "help", "copyright", "credits" or "license" for more information. > > (InteractiveConsole)>>> import tagging > > >>> tagging.VERSION > > > (0, 3, 'pre') > > > I think great, that was pretty easy... I should be ready to go. Push > > my code up to the server, run syncdb, it makes the tables and index... > > but I get a 500 Internal Server Error. What's most frustrating is I > > can't seem to get a debug error page, despite having Debug = True but > > that just seems to be a quirk of using dreamhost. > > > So fearing maybe my code is borked, I undid my recent checkout... > > sites fine again. If I put in 'tagging', into the INSTALLED_APPS, I > > get the 500 Internal Server Error. > > > I realize this is probably due to the way dreamhost is setup. In my > > passenger_wsgi.py script, I have a bunch of sys.path.inserts to add > > the same folders in my PYTHONPATH, I'm just not understanding where > > the disconnect it. If someone has some insight into why this might be > > happening, I'd love to hear it. Both laptop and server are using > > Django version 1.1.1. Is there something I'm missing with my paths? > > I've spent more time trying to fix this than I have adding the tags. :- > > ( > > I'm not familiar with Dreamhost's setup particularly, but if you are > already inserting paths into sys.path in your WSGI script, the answer > is probably there. Instead of running setup.py to install django- > tagging anywhere, just leave it where it is, and insert its path into > sys.path along with all the others. > -- > DR.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
