Re: [mezzanine-users] Ajax add to cart

[Andrés Douglas]

Good point, thanks Ken

> On Jan 14, 2015, at 9:56 AM, Ken Bolton  wrote:
> 
> Stephen's explanation from three years ago remains true. One of the best 
> things about Mezzanine, in my opinion, is how carefully limited the 
> application is. Because it is just Django, you can use the common Django ajax 
> patterns to roll your own without worrying that someone's bizarre opinions 
> won't hinder development.
> 
> - ken
> 
> On Tue, Jan 13, 2015 at 1:22 PM, Andres Douglas  > wrote:
> Was just wondering about this myself. Have there been any changes to 
> facilitate this or is this still the best way to do so?
> 
> On Tuesday, January 10, 2012 at 5:36:59 AM UTC-8, Stephen McDonald wrote:
> There's nothing like this in Cartridge. The general approach taken so far is 
> to implement everything using regular forms/http, and you can overlay ajax on 
> top of that in your project if you want to. You could probably do this with 
> middleware using Django 1.3's template response: 
> https://docs.djangoproject.com/en/dev/topics/http/middleware/#process-template-response
>  
> 
> 
> - Overlay jQuery posting on top of the add to cart form
> - Use middleware with process_template_response and check for an ajax post 
> from the add to cart form, and return JSON with the parts you want from the 
> context (form errors, cart info, etc)
> 
> On Tue, Jan 10, 2012 at 4:41 PM, Daryl Antony > 
> wrote:
> Hey there,
> 
> Getting busy on some work on a cartridge install.  I'm wondering if
> there's any ground work for adding products to the cart via ajax?
> 
> I can see some mention of ajax views in cartridge.views -- but they
> seem to be for the checkout.
> 
> Thoughts appreciated!
> 
> 
> 
> -- 
> Stephen McDonald
> http://jupo.org 
> 
> -- 
> 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, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/mezzanine-users/FDKuf4m2_eA/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> mezzanine-users+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] New Mezzanine 3.2 version dropping python 2.6 & supporting django 1.7.x+ only?

[Ken Bolton]

Mezzanine has a storied history of maintaining compatibility with all
currently supported versions of Python & Django. Right now, that includes
Django 1.4 and 1.6, while issues with 1.7 are ironed out. Dropping support
for 1.5 makes sense for the next release, but a move to drop support for
1.4 goes very much against the Django (and Mezzanine) Way. I believe we
dropped support for Python 2.5 prematurely.

Haste to run the latest versions of software often leads to more problems
than it solves. We are better off with clear upgrade paths and processes.

- ken

On Wed, Jan 14, 2015 at 2:44 PM, Stephen McDonald  wrote:

> And as for dropping older Django versions - the reason we support these is
> that I imagine Mezzanine is commonly used with other third party apps that
> might not necessarily be compatible with the latest Django version, so it's
> not always as simple as "use the latest Mezzanine for the latest Django"
> and everything will just work.
>
> Sure the code base would be slightly cleaner, but honestly, supporting
> multiple Django versions isn't really hard, it's working out how to upgrade
> Mezzanine to work with newer versions of Django that are incompatible with
> concepts in Mezzanine that's the hard problem - once that gets solve X
> number of times for every new version of Django, a few if statements and
> ImportError catches here and there are all that's required to support older
> Django versions.
>
> It's certainly very tempting from a maintenance perspective, but the
> problems it may cause people outweighs the ease in which multiple versions
> can be supported.
>
>
> On Thu, Jan 15, 2015 at 2:26 AM, Josh Cartmell 
> wrote:
>
>> Support for 1.7 is coming, it just isn't quite finished yet.
>>
>> On Wed, Jan 14, 2015 at 1:35 AM, Asif Saifuddin  wrote:
>>
>>> Hello,
>>>
>>> I have been thinking about a newer version of mezzanine cms supporting
>>> django 1.7+ only and dropping support for python 2.6. This will help to
>>> absorb the new django features and with a lot more cleaner & modern code
>>> base for mezzanine cms.
>>>
>>> Looking forward to hear about your thoughts on this issue
>>>
>>> /asif
>>>
>>> --
>>> 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, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Stephen McDonald
> http://jupo.org
>
> --
> 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, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] New Mezzanine 3.2 version dropping python 2.6 & supporting django 1.7.x+ only?

[Stephen McDonald]

And as for dropping older Django versions - the reason we support these is
that I imagine Mezzanine is commonly used with other third party apps that
might not necessarily be compatible with the latest Django version, so it's
not always as simple as "use the latest Mezzanine for the latest Django"
and everything will just work.

Sure the code base would be slightly cleaner, but honestly, supporting
multiple Django versions isn't really hard, it's working out how to upgrade
Mezzanine to work with newer versions of Django that are incompatible with
concepts in Mezzanine that's the hard problem - once that gets solve X
number of times for every new version of Django, a few if statements and
ImportError catches here and there are all that's required to support older
Django versions.

It's certainly very tempting from a maintenance perspective, but the
problems it may cause people outweighs the ease in which multiple versions
can be supported.


On Thu, Jan 15, 2015 at 2:26 AM, Josh Cartmell  wrote:

> Support for 1.7 is coming, it just isn't quite finished yet.
>
> On Wed, Jan 14, 2015 at 1:35 AM, Asif Saifuddin  wrote:
>
>> Hello,
>>
>> I have been thinking about a newer version of mezzanine cms supporting
>> django 1.7+ only and dropping support for python 2.6. This will help to
>> absorb the new django features and with a lot more cleaner & modern code
>> base for mezzanine cms.
>>
>> Looking forward to hear about your thoughts on this issue
>>
>> /asif
>>
>> --
>> 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, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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, visit https://groups.google.com/d/optout.
>



-- 
Stephen McDonald
http://jupo.org

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Ajax add to cart

[Ken Bolton]

Stephen's explanation from three years ago remains true. One of the best
things about Mezzanine, in my opinion, is how carefully limited the
application is. Because it is just Django, you can use the common Django
ajax patterns to roll your own without worrying that someone's bizarre
opinions won't hinder development.

- ken

On Tue, Jan 13, 2015 at 1:22 PM, Andres Douglas 
wrote:

> Was just wondering about this myself. Have there been any changes to
> facilitate this or is this still the best way to do so?
>
> On Tuesday, January 10, 2012 at 5:36:59 AM UTC-8, Stephen McDonald wrote:
>>
>> There's nothing like this in Cartridge. The general approach taken so far
>> is to implement everything using regular forms/http, and you can overlay
>> ajax on top of that in your project if you want to. You could probably do
>> this with middleware using Django 1.3's template response: https://docs.
>> djangoproject.com/en/dev/topics/http/middleware/#
>> process-template-response
>>
>> - Overlay jQuery posting on top of the add to cart form
>> - Use middleware with process_template_response and check for an ajax
>> post from the add to cart form, and return JSON with the parts you want
>> from the context (form errors, cart info, etc)
>>
>> On Tue, Jan 10, 2012 at 4:41 PM, Daryl Antony 
>> wrote:
>>
>>> Hey there,
>>>
>>> Getting busy on some work on a cartridge install.  I'm wondering if
>>> there's any ground work for adding products to the cart via ajax?
>>>
>>> I can see some mention of ajax views in cartridge.views -- but they
>>> seem to be for the checkout.
>>>
>>> Thoughts appreciated!
>>>
>>
>>
>>
>> --
>> Stephen McDonald
>> http://jupo.org
>>
>  --
> 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, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Deploy folder

[Ken Bolton]

On Wed, Jan 14, 2015 at 10:47 AM,  wrote:

> Ah, thanks for the quick reply Kenneth. So basically as long as the FABRIC
> dictionary settings in my settings.py are configured correctly, I can use
> the /deploy and fabric python tool to deploy to my hosting provider...  am
> I understanding that correctly?
>

If you want to deploy to the default stack of Nginx, Gunicorn, & PostgreSQL
on Ubuntu 12.04, you can leave everything in the `deploy` directory exactly
as it stands. The changes specific to your project will all be to the
FABRIC dictionary in settings.py. You can (though I don't, ever!) modify
the files in `deploy` in whatever way you want. Keep in mind that some
modifications to the files in `deploy` will also require changes to the
fabfile.py.

best,
ken

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Deploy folder

[automotiveace]

Ah, thanks for the quick reply Kenneth. So basically as long as the FABRIC 
dictionary settings in my settings.py are configured correctly, I can use 
the /deploy and fabric python tool to deploy to my hosting provider...  am 
I understanding that correctly?

On Tuesday, January 13, 2015 at 12:11:41 PM UTC-5, Kenneth Bolton wrote:
>
> Fabric is a Python library for streamlining the use of SSH for 
> deployments. Mezzanine's deploy directory relies on the included fabfile.py 
> and your settings.FABRIC dictionary to automate deployment to Ubuntu 12.04. 
> Further illumination can be found at 
> http://mezzanine.jupo.org/docs/deployment.html.
>
> hth,
> ken
>
> On Tue, Jan 13, 2015 at 10:46 AM, > 
> wrote:
>
>> Somewhat of a newb to Mezzanine, so forgive me if this question sounds a 
>> bit obvious:  what exactly is the deploy folder for? How can that be used 
>> for deployment? Are there settings in there that need to be addressed 
>> or.
>>
>> I've looked on Django and Mezzanine deploy docs but I guess I still need 
>> a bit more clarity/understanding.
>>
>> -- 
>> 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-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] New Mezzanine 3.2 version dropping python 2.6 & supporting django 1.7.x+ only?

[Josh Cartmell]

Support for 1.7 is coming, it just isn't quite finished yet.

On Wed, Jan 14, 2015 at 1:35 AM, Asif Saifuddin  wrote:

> Hello,
>
> I have been thinking about a newer version of mezzanine cms supporting
> django 1.7+ only and dropping support for python 2.6. This will help to
> absorb the new django features and with a lot more cleaner & modern code
> base for mezzanine cms.
>
> Looking forward to hear about your thoughts on this issue
>
> /asif
>
> --
> 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, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] django_auth_ldap3, a new LDAP authentication backend

[Josh Cartmell]

Cool stuff, thanks Sam!

On Tue, Jan 13, 2015 at 10:10 PM, Mario Gudelj <
ma...@twoblokeswithapostie.com> wrote:

> Legend! Thanks for sharing this Sam!
>
>
> P: +61 2 9281 3315
> M: +61 415 193775
> E: ma...@twoblokeswithapostie.com
> W: www.twoblokeswithapostie.com
>
>
>
>
> On Wed, Jan 14, 2015 at 1:31 PM, Sam Kingston  wrote:
>
>> Hi Stephen and others,
>>
>> I have developed and release a new LDAP authentication backend called
>> django_auth_ldap3, that plugs into Django's auth system and allows
>> authentication against OpenLDAP or Active Directory. It fully supports Py
>> 2.7/3 and Django 1.6/1.7, and unlike most other backends has pure-Python
>> dependencies.
>>
>> It's not specific to Mezzanine, but it was written for a Mezzanine
>> project I have.
>>
>> You can see the full source and documentation at
>> https://github.com/sjkingo/django_auth_ldap3
>>
>> To install in Mezzanine is as simple as:
>> https://github.com/sjkingo/django_auth_ldap3/wiki/Intergration-with-Mezzanine
>>
>> I have tested it and not found any issues with coexisting with
>> Mezzanine's auth backend.
>>
>> Thought it might be useful! :)
>>
>> --
>> 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, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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, visit https://groups.google.com/d/optout.
>

-- 
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, visit https://groups.google.com/d/optout.