[mezzanine-users] Re: page not found django_redirect

2013-12-23 Thread Moltra
I have opened a ticket at https://github.com/django-debug-toolbar/django-debug-toolbar/issues/509 about this issue. I am not sure if it is a problem caused by mezzanine or debug_toolbar. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To

Re: [mezzanine-users] Re: page not found django_redirect

2013-12-23 Thread Moltra
I tried that and still had the same problem. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options,

Re: [mezzanine-users] Re: page not found django_redirect

2013-12-23 Thread Stephen McDonald
Thanks Ken - with this confirmation I looked into it and added details to the DDT GitHub issue Moltra also opened: https://github.com/django-debug-toolbar/django-debug-toolbar/issues/509#issuecomment-31152850 TLDR: DDT 1.0 requires its middleware be ordered last in the middleware order, as it

[mezzanine-users] Re: page not found django_redirect

2013-12-22 Thread Moltra
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*

[mezzanine-users] Re: page not found django_redirect

2013-12-22 Thread Moltra
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