stephenmcd/mezzanine — Issue #127: Introduce Upgrade Instructions
Author: atlasloewenherz
Created: 2012-01-18 15:27:44+00:00
State: open

according to the good documentation +1 one can use mezzazine with django 1.3.1 which is partially true
except the fact that in the settings.py and in other views of the project you still rely on the MEDIA_URL instead of the
STATIC_URL introduced by Django-1.3.x.
here are the steps to get the issue:

> virtualenv yourEnv -no-site-ackages
> pip install django
> gh clone path/to/mezzanine
> echo localPathTo/mezzaning > yourEnv/lib/python-yourVersion/site-packages/mezzanine.pth
> ln -s localPathTo/mezzaning/mezzanine/bin/mezzaning_project.py yourEnv/bin/mezzanine_project

either

> django-admin startproject sampleProject
> cd sampleProject

set the settings.py to meets mezzanine requirements
here is mine:

> http://dpaste.com/689752/

> python manage.py syncdb --noinput

> python manage.py collectstatic

> python manager.py runserver

i changed all occurance of MEDI_URL in base.html into STATIC_URL but i still get an empty value for the
STATIC_URL when accessing the Backend and Frontend.

or even using

> mezzanine_project sampleProject

the same setting.py as above i get the same behaviour STATIC_URL is empty hence all the static resources are not served
and the server process returns 404 since the path for each resource is wrong.

if im doing something wrong in here please ignore this request otherwise i would be more than glad to see this peace of
documentation reflected in the main docs.

thanks & regards
Yassine