Hello, Perhaps try installing a completely new/fresh dev environment in a vmware/virtualbox instance, and attempt to get it working from there, that will at least help you narrow this problem down locally instead of poking around at production. Also try and make sure you install the same OS/release as what you are trying to deploy in production. You should also use virtualenv/virtualenvwrapper to help reduce the chance of library/dependency conflict.
Also heads up - realistically the mailing lists are here to point you in the right direction, but it's up to you to do as much of the work as possible. If you come up against a problem, 99% of the time Google will already have the answer. Some great examples of how to use Google accurately can be found at https://code.djangoproject.com/wiki/UsingTheMailingList . If you're not sure how to use any of the things mentioned, then here are some good starting points for learning; http://gettingstartedwithdjango.com/ - Django learning http://learnpythonthehardway.org/book/next.html - Python learning http://virtualenvwrapper.readthedocs.org/en/latest/ Hope this helps, and remember to update this thread once you figure out the answer so others can find it in the future. Cal On Fri, Dec 27, 2013 at 12:34 PM, Gabriele Stoia <gabrielest...@gmail.com>wrote: > Thank you Tom for your answer. > I'm sorry but I don't have much experience with Django... > > Do you have an idea how to fix this problem ? > > Thanks in advance > Gabri > > Il giorno martedì 24 dicembre 2013 20:58:32 UTC+7, Thomas ha scritto: >> >> >> On 2013-12-23, at 9:42 PM, Gabriele Stoia <gabrie...@gmail.com> wrote: >> >> I think I found the problem...maybe... >> >> I running my app in the same hosting of another app ... (sorry for my >> english..is not my first language... I'm italian…) >> >> >> If you are not using virtualenv and pip to manage each of these >> installations you will likely find it useful to do so. It should eliminate >> worries about conflicts between version sets. >> >> hth >> >> - Tom >> >> >> >> I have >> >> >> >> >> >> >> >> *-- first app-- feincms-- other module-- ...--second app-- -- feincms-- >> -- other module* >> >> Maybe my second-app is using feincms of the first app which is different >> version. >> I think this because I got this error : >> >> No module named filterspecs >> /home/*alessandrocambogia*/feincms/admin/filterspecs.py in <module>, line 7 >> >> where *alessandrocambogia *is the first-app. >> >> I need to have >> /home/alessandrocambogia/*gabryandjenny*/feincms >> >> where *gabryandjenny * is the second-app >> >> but actually I don't know how to change the path... Is my first experience >> in Django. >> Can you help in this ???? Please ??? >> Thank you in advance. >> >> Gabri >> >> >> >> >> Il giorno martedì 24 dicembre 2013 07:45:02 UTC+7, Russell Keith-Magee ha >> scritto: >>> >>> >>> On Mon, Dec 23, 2013 at 10:53 AM, Gabriele Stoia <gabrie...@gmail.com>wrote: >>> >>>> Hi Russel, >>>> >>>> thank you for your e-mail !!! >>>> I thought that something was connected with MPTT or FeinCMS... I'll try >>>> to work out ! >>>> What I really don't understand why so many problem when you in >>>> deployment ??? In local everything was super fine !!! >>>> >>> >>> If you're having "deployment only" problems, this points to a problem >>> with the way your development process is organised. These sorts of problems >>> only emerge because your development environment is fundamentally different >>> to your production environment -- for example, different versions of >>> software, different paths. If you make good use of virtualenv to isolate >>> your project, and use requirements files to ensure version compatibility, >>> you should be able to minimise this sort of problem. >>> >>> Yours, >>> Russ Magee %-) >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com. >> To post to this group, send email to django...@googlegroups.com. >> >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/django-users/e66a8967-5e82-43b2-9ba8-8736cb192025% >> 40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> Tom Lockhart >> tlockh...@gmail.com >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/9bd66d58-20d2-40fd-8445-e1e7910b9507%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHKQagE3SaLTyWH8hVdJ-92JEjs0%2BLBzP6NHZ9az6B4psDeYcw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
