2013/12/22 Giovanni Pederiva giovanni.peder...@gmail.com
hi, i'm an italian physics student.
i was asked to remake a website that was quite old and difficult to manage
for a summer school i had attended. one of my first ideas was to use a cms
do manage the content. as the website was already
found what is calling the django_redirect, still not sure what started
causing it.
*SELECT* django_redirect.id, django_redirect.site_id,
django_redirect.old_path,
django_redirect.new_pathhttp://127.0.0.1:8000/duck-dynasty/#
*FROM* django_redirect *WHERE* (django_redirect.site_id = 1 *AND*
I keep looking at this and trying to find what happened, I have tried to
update the 1st post on here, but cannot find a way to edit the post. Is
there a way to do this?
I figured out what was causing it, I had installed debug_toolbar and that
is when the problems started happening. I
You're hitting these issues because you're using Mezzanine 1.4.16, which is
3 months old, predates the release of Django 1.6, and explicitly defines
its highest supported Django version as 1.5.x.
The current development branch of Mezzanine aims to be fully compatible
with Django 1.6 and doesn't
Hello Stephen,
Thanks for the note. I suspected as much. I'm just picking up mezzanine,
so I didn't know if I was doing something backwards or not. I'll keep an
eye out for the next release.
FWIW, what I've seen so far is pretty slick. Thanks so much for building
this!
David
On Sunday,
