an old satchmo installation

[MikeKJ]

Many years ago using one of the 1st releases of satcmo we created a site and unfortunately the holding directory for the site was called satchmo.  This site has since remained on a server on it's own as it cannot go onto the main server becasue having the directory called satchmo creates total confusion with the other shops.  I have tried just renaming the holding directory but that fails miserably, anyone got any ideas please?

[Stuart Laughlin]

Check the URLs setting in settings.py. I think you'll need to change it from satchmo.urls to newname.urls.

On Apr 27, 2012 8:51 AM, "MikeKJ" <mike....@paston.co.uk> wrote:

Many years ago using one of the 1st releases of satcmo we created a site and unfortunately the holding directory for the site was called satchmo.  This site has since remained on a server on it's own as it cannot go onto the main server becasue having the directory called satchmo creates total confusion with the other shops.  I have tried just renaming the holding directory but that fails miserably, anyone got any ideas please?

--
You received this message because you are subscribed to the Google Groups "Satchmo users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/satchmo-users/-/oqfn70TxajQJ.
To post to this group, send email to satchm...@googlegroups.com.
To unsubscribe from this group, send email to satchmo-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.

[MikeKJ]

Yep thx done that, also as it is a satchmo shop melded with normal django and apps in the settings.py too I am now getting

[Fri Apr 27 16:30:12 2012] [error] [client 194.164.225.146] PythonHandler django.core.handlers.modpython: IOError: [Errno 2] No such file or directory: '/var/www/django/satchmo/satchmo.log'

even after I traced the path down and changed it to /var/www/django/foldername/satchmo.log'  what it should be, I still get the above error 

[hynekcer]

The best for separating different versions is virtualenv in general.
Moving an _existing_ installation into virtualenv is however not easy.
(or not as easy as fixing python paths manually)

In short, removing some unnecessary paths from sys.path is your
friend.

I regularly use all supported versions of Django and Satchmo for
compatibily tests without using virtualenv. It is relative easy if
they all use the same python version.
Only one Satchmo should be on the path with directories like
"satchmo_store" etc. As you know paths can be added dynamically by
many ways like evironment variable PYTHONPATH or option "--
pythonpath=..." for "manage.py" but the unuseful ones can be removed
from "sys.path" by some written lines in "manage.py". (i.e. remove
them before incorrect packages are imported) You should check files
containing strings like "../../satchmo/apps" and "../satchmo/
apps" (manage.py or settings.py) whether such added relative paths are
unambiguous and correct.

A more cleaner solution is remove some potencially conflicting paths
from easy-install.pth or other *.pth and add them dynamically the
apropriate version

(Possible side effects under certain circumstances are one of reasons
why the newest Python 1.4 never adds parent directory of django
project directory to the path, even at the cost of more complicated
directory structure. Django 1.4 has customized manage.py different for
every project. This was inspiration for me to do the same with old
versions and it works.)

If you need move some directory (i think it is not usually necassary)
it is good to recompile them to be reported correct filenames and at
all any code line in tracebacks etc.
cd something # go to the directory under which every *.py should
be recompiled
python -m compileall -f $(pwd)

--Hynek