Check whether the toolbar directory has __init__.py in it. Then try
from cms.middleware import toolbar
On Fri, Dec 10, 2010 at 12:20 AM, wilbur wrote:
> I have checked my python path, and I see:
>
> /usr/local/lib/python2.6/dist-packages/django_cms-2.1.0.beta3-
> py2.6.egg
>
> as one of the di
I have checked my python path, and I see:
/usr/local/lib/python2.6/dist-packages/django_cms-2.1.0.beta3-
py2.6.egg
as one of the directories. If i point to the module I want with:
'cms.middleware.toolbar.ToolbarMiddleware',(##and this path
DOES exist in the directory structure)
in my MI
Hi,
the problem look to be that cms is not in your python path.
It should work without hard copying it in other directory.
Are you able to import this middleware from the python interpeter?
If not check your python path.
On Thu, Dec 9, 2010 at 11:25 PM, wilbur wrote:
> Hello and thank you,
>
>
Hello and thank you,
Removing south worked fine. I initially had problems loading
middleware classes to settings.py for the following:
#'cms.middleware.page.CurrentPageMiddleware',
#'cms.middleware.user.CurrentUserMiddleware',
#'cms.middleware.toolbar.ToolbarMiddleware',
#'cms.mid
The simplest solution:
remove south from the list of installed application, run
./manage.py syncdb
this will create you tables the way thay have to be and everything will
be ok.
This will not fix your south problem, but will allow you to use django cms.
If you later fix the south, just run
./manag
5 matches
Mail list logo
