Re: [mezzanine-users] Re: registering new settings for templates

Yeah, I'm referring to that, but simply looking at that part makes little meaning *how *to use it, unless you see an example like this , which imho, should be the most im

Re: [mezzanine-users] Re: registering new settings for templates

The documentation mezzanin.jupo.org/docs/configuration.html only mentions how to register a new setting, expose it to admin, and access/read via models etc. However, there's no mention how to expose the registered setting via templates, which to do, has to be done this way: from mezzanine.conf

Re: [mezzanine-users] Re: registering new settings for templates

I suspect Nkansah is referring to this setting: http://mezzanine.jupo.org/docs/configuration.html#template-accessible-settings But yes, perhaps TEMPLATE_ACCESSIBLE_SETTINGS should be referenced in the docs at the point that talks about register_setting() On 16 October 2015 at 13:03, Ryne Evere

Re: [mezzanine-users] Re: registering new settings for templates

If something is missing please enlighten us. What did you learn? On Thu, Oct 15, 2015 at 9:28 PM, Nkansah Rexford wrote: > got it working. Yet another missing piece from the docs. > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To u

[mezzanine-users] Re: registering new settings for templates

got it working. Yet another missing piece from the docs. -- 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 mor

[mezzanine-users] registering new settings for templates

After registering a setting... from mezzanine.conf import register_setting from django.utils.translation import ugettext_lazy as _ register_setting( name="FOOTER_TEXT", label=_("Footer About"), description=_("If present, about information about " "would be displayed."), ed

Re: [mezzanine-users] Akismet spam filtering with Python 3

Sounds like a bug, patch welcome. On Fri, Oct 16, 2015 at 10:06 AM, Christian Hill wrote: > I have found that Akismet spam filtering isn't working for me with Python > 3.3-- after a bit of investigating, the problem seems to be in > mezzanine.utils.views.is_spam_akismet. The following Exception

[mezzanine-users] Akismet spam filtering with Python 3

I have found that Akismet spam filtering isn't working for me with Python 3.3-- after a bit of investigating, the problem seems to be in mezzanine.utils.views.is_spam_akismet. The following Exception is always being raised: try: response = urlopen(Request(api_url, urlencode(data), headers)).re

Re: [mezzanine-users] Cannot edit content on Rich Text Page

Were you running a Mezzanine 3 site before? I have experienced a problem where the old tinymce files are cached by the browser. A cache reload (Ctrl + F5) does the trick. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from t

Re: [mezzanine-users] Cannot edit content on Rich Text Page

If you're using firefox you may need to go to 127.0.0.1 rather than localhost. On Thu, Oct 15, 2015 at 10:15 AM, Ilya Yakunin wrote: > > > Hi all, > > I've just started a new mezzanine project u

[mezzanine-users] Cannot edit content on Rich Text Page

Hi all, I've just started a new mezzanine project using: * Mezzanine 4.0.1 * Django 1.8.5 * Python 2.7.10 * SQLite 3.8.10.2 * Linux 3.16.0-4-amd64 with default config. Simply ran mezzanine-proj