Haha, no worries. Glad that you figured it out!
On Mon, Dec 23, 2013 at 4:58 PM, Diego Ponci 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, and noticed I had sk
>
> Thanks for looking into this for me. I thought I was doing something
> wrong. New to Django and mezzanine.
--
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 emai
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 now
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, and noticed I had skipped the
section where you put the processor in a page_processors.py file, and it
worked.
So, yeah, typical
>
> May U zip and share your project files with us? Because the problem may
> depends on so many things. I think U are missing something.
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails
The culprit is DjDT 1.0. I haven't had time to look into it, but `pip
install django-debug-toolbar==0.9.1` will fix your problem.
On Mon, Dec 23, 2013 at 6:19 PM, Moltra wrote:
> Yes, I just tried with a fresh install of mezzanine and had the same
>> problem.
>>
>
> ```
> Django==1.5.5
> Mezzan
>
> Yes, I just tried with a fresh install of mezzanine and had the same
> problem.
>
```
Django==1.5.5
Mezzanine==1.4.16
Pillow==2.2.2
bleach==1.2.2
django-debug-toolbar==1.0
filebrowser-safe==0.2.31
grappelli-safe==0.2.23
html5lib==0.95
oauthlib==0.6.0
pytz==2013.8
requests==1.2.3
requests-oau
Have you tried this with a vanilla unmodified Mezzanine installation?
On Mon, Dec 23, 2013 at 3:35 PM, Moltra wrote:
> 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
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, v
Hey Diego, processor_form is used for page_processors (
http://mezzanine.jupo.org/docs/content-architecture.html#page-processors)
not context processors. Context processors are a part of Django that allow
you to globally add things to your template context. Page processors are
something that Mezz
Hey Moltra, I've never run into this issue before with Mezzanine. Could it
have something to do with the INTERCEPT_REDIRECTS setting of the debug
toolbar?
http://django-debug-toolbar.readthedocs.org/en/1.0/configuration.html?highlight=intercept_redirects
(scroll down and you will find it)
On Mon
Hey Alekto, I'm not sure what is going on in your project, but you
shouldn't have to change the TEMPLATE_DIRS setting. I usually put themes
just before mezzanine.boot (they definitely need to be before
mezzanine.core.) Are you using a default mezzanine-project created
settings file? If so have
Hey David, glad your liking it, Mezzanine is definitely an excellent piece
of software! Keep your eye on the list for the release, you can also
follow @mezzaninecms or @stephen_mcd on Twitter as I'm sure the release
will be announced there as well.
On Sun, Dec 22, 2013 at 7:16 PM, David Zwarg w
If if helps, the stacktrace goes back to
local/lib/python2.7/site-packages/django/template/context.py in __init__,
in this section:
1.
Context.__init__(self, dict_, current_app=current_app,
2.
use_l10n=use_l10n, use_tz=use_tz)
3.
i
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'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"
t
On 2013-12-21, at 3:32 PM, Stephen McDonald 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
> true.
N
Also ensure your theme app (a Python package) is importable, eg:
python manage.py shell
>>> import theme
On Mon, Dec 23, 2013 at 7:12 PM, wrote:
> 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
>
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 to
Hi,
I am trying to create a navbar in dropdown.html that is centered around a
middle picture using bootstrap.
Eks.
http://jsfiddle.net/5WxHY/
I would like to limit the numbers of links on the left hand side of the
. I.e. no more than 3.
Is is possible to accomplish by using only one navbar, and
20 matches
Mail list logo
