As you can see I have included a __init__.py file in my theme root
directory. Have also tried including an empty models.py, but I am still not
able to have my theme function without changing the TEMPLATE_DIRS in
settings.py.
Anyway, thanks for your effort. I will update this post if I manage
On 2013-12-21, at 3:32 PM, Stephen McDonald st...@jupo.org wrote:
The app should be a proper Python package which in the least means it should
contain an empty __init__.py file. At some stage Django required each app
have at least an empty models.py module also, I'm not sure if that's still
I've written a context processor, as stated in the docs, so, I have
#context_processors.py
from mezzanine.pages.page_processors import processor_for
@processor_for('myform')
def another_form_processor(request, page):
return {form: {}}
and added context_processors.another_form_processor
to
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
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,
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
Haha, no worries. Glad that you figured it out!
On Mon, Dec 23, 2013 at 4:58 PM, Diego Ponci dgo.ponci...@gmail.com wrote:
I've read the docs before, but the processor wasn't being executed, hence
why I tried registering it as a context processor.
Now I followed your advice, read it again,
