Re: [mezzanine-users] Limited support of Bootstrap 3 styles in Mezzanine/Cartridge ?

Disclaimer: I wrote most of this before getting Steve's reply, so they may overlap. -- Again, no doubt that Django can apply classes to form inputs. The problem is that it happens at Python level, it is not something you can change by just overriding a template. The available choices for th

Re: [mezzanine-users] Limited support of Bootstrap 3 styles in Mezzanine/Cartridge ?

You're arguing that we should embed bootstrap features into server-side code, but use of bootstrap is entirely optional and can be ripped out at the template (eg HTML, CSS, JS) level. It makes no sense to have it bleed into Python code. What happens when someone wants to use a different front-end C

Re: [mezzanine-users] Limited support of Bootstrap 3 styles in Mezzanine/Cartridge ?

Django can apply classes to input elements or other field widgets, either at a field declaration or at a runtime in form's initializer. For example, Mezzanine does it itself at several places like in HTML5Mixin

[mezzanine-users] Multi Tenancy / Multi IPs

Howdy All - I have a multi tenancy project up and running. However, I need to assign each domain a unique IP. Setting this up on AWS was pretty easy. AWS allows you to use multiple Elastic IPs on a single EC2 server instance. The tricky part has been getting the mezzanine nginx.conf and gunic

[mezzanine-users] Re: Implementing form for paypal payments

So if someone gets the same problem It only occurs in Python3 because of how super() is used. So if you are using python3 super(MyOrderForm, self).__init__(*args,**kwargs) I know It's a noob mistake, but this may help someone like myself. Cheers. On Sunday, 27 December 2015 22:32:39 UTC, T

Re: [mezzanine-users] Overriding ADMIN_MENU_ORDER

Thanks Ken. I tried that, and got the same behavior. Then after spending a little more time on stack overflow, it occurred to me that I might need to add a rule to my urls.py. So now what I have is: url("^admin/importer", "web.views.importer", name="importer"), Then in my views.py I have: d

Re: [mezzanine-users] Limited support of Bootstrap 3 styles in Mezzanine/Cartridge ?

We do this because Django won't let you apply classes directly to input elements without going rather deep into the widget rendering logic. I think the rationale is that swapping Bootstrap out should be a matter of changing CSS only. I haven't found this to be a problem when customizing the looks

Re: [mezzanine-users] Overriding ADMIN_MENU_ORDER

Hi Joel, Assuming everything has been set up correctly, your projects' settings.py should trump all except local_settings.py. Do you get the same results in a new virtualenv with a clean installation of Mezzanine? -ken On Tue, Dec 29, 2015 at 11:34 AM, Joel Gwynn wrote: > OK, so I put in some

Re: [mezzanine-users] Overriding ADMIN_MENU_ORDER

OK, so I put in some print statements: one in the mezzanine core defaults.py right after the call to register_settings(), and the next one in my settings.py right after the code below. It looks like settings.py is being executed before defaults.py, so my setting is getting overriden. Is that

[mezzanine-users] Limited support of Bootstrap 3 styles in Mezzanine/Cartridge ?

Hello, any idea why the decision do not comply to Bootstrap rules and do it its own way ? I did mean html forms, for example. By the mezzanine.css