[mezzanine-users] Support for Different or Multiple Email Sending Addresses
How can I get Mezzanine/Cartridge to send emails from different email addresses for various purposes? - When the user submits the contact-form email should go from cont...@abc.com - When the user makes a purchase, order receipt should go from ord...@abc.com In Settings-Shop section there is 'From Email' where I put the ord...@abc.com address. BUT there is no field to specify the password and other email settings In Contact-Us page there is 'From email' where I put the cont...@abc.com address. Here also there is no field to specify the password and other email settings However, in *settings.py* file. I use the following, as business accounts with gmail. But the email always arrives from the email setting later in order in the file EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'cont...@abc.com' EMAIL_HOST_PASSWORD = 'password' EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'ord...@abc.com' EMAIL_HOST_PASSWORD = 'password' Please help. Need to make it look business purpose -- 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] Support for Different or Multiple Email Sending Addresses
Hi vikraw, I don't think there is an easy way to specify multiple email users/backends like you have. Instead, I would recommend making it so that cont...@abc.com can send mail as ord...@abc.com (or vice versa). I know that specifically with Google email this is fairly easy to set up. Then mail can be sent as either address through the same smtp connection. On Fri, May 15, 2015 at 8:39 AM, vikraw vik...@gmail.com wrote: How can I get Mezzanine/Cartridge to send emails from different email addresses for various purposes? - When the user submits the contact-form email should go from cont...@abc.com - When the user makes a purchase, order receipt should go from ord...@abc.com In Settings-Shop section there is 'From Email' where I put the ord...@abc.com address. BUT there is no field to specify the password and other email settings In Contact-Us page there is 'From email' where I put the cont...@abc.com address. Here also there is no field to specify the password and other email settings However, in *settings.py* file. I use the following, as business accounts with gmail. But the email always arrives from the email setting later in order in the file EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'cont...@abc.com' EMAIL_HOST_PASSWORD = 'password' EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'ord...@abc.com' EMAIL_HOST_PASSWORD = 'password' Please help. Need to make it look business purpose -- 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] moving data from development to production and the twitter model
Django docs state the flush command installs any initial data - in Mezzanine that equates to a few demo pages and default user account. https://docs.djangoproject.com/en/1.8/ref/django-admin/#flush There's no development to production migration of data occurring. The only correlation with the twitter app is that there is no initial data to install. On Sat, May 16, 2015 at 9:27 AM, Graham Oliver greenbay.gra...@gmail.com wrote: Hello all I am just working through the process of moving data from development to production (which I will document at some point) I notice that after I do a 'flush' command various bits of data spring back to life. Doing some research I see that this is because of something called a post_migrate signal... I have a few questions 1. Is there a reason why the twitter model is the only model in Mezzanine to be affected by this? 2. Can you point me to the lines of code where this happens (the post_migrate actions for the twitter model) 3. When I run the 'flush' command with verbosity 3, I see this comment '[108.59.11.112] out: Creating example.com Site object'. Would it be a good idea to have something similar for the twitter objects that are created? TIA Graham -- 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.
[mezzanine-users] moving data from development to production and the twitter model
Hello all I am just working through the process of moving data from development to production (which I will document at some point) I notice that after I do a 'flush' command various bits of data spring back to life. Doing some research I see that this is because of something called a post_migrate signal... I have a few questions 1. Is there a reason why the twitter model is the only model in Mezzanine to be affected by this? 2. Can you point me to the lines of code where this happens (the post_migrate actions for the twitter model) 3. When I run the 'flush' command with verbosity 3, I see this comment '[108.59.11.112] out: Creating example.com Site object'. Would it be a good idea to have something similar for the twitter objects that are created? TIA Graham -- 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.
[mezzanine-users] Re: Using Mezzanine with Python 3: package compatibility
Thanks Josh and Graham, I'll stick with PostgreSQL then, but wait until the next Mezzanine release before upgrading Django. I'm just glad to have got my site online for now! Cheers, Christian On Friday, May 15, 2015 at 4:31:18 PM UTC-4, Graham Oliver wrote: Hi Christian In terms of MySQL vs PostgreSQL have a look at https://docs.djangoproject.com/en/1.7/topics/migrations When I read 'PostgreSQL is the most capable of all the databases here in terms of schema support' and 'MySQL lacks support for transactions around schema alteration operations, meaning that if a migration fails to apply you will have to manually unpick the changes in order to try again (it’s impossible to roll back to an earlier point).' I decided that PostgreSQL was the best option. Cheers g On Saturday, 16 May 2015 02:32:36 UTC+12, xnx wrote: Hello Mezzanine Users, I'm new to Mezzanine but not Django: I'm enjoying learning it a lot and it does a great job, but I've run into a couple of problems. I am trying to deploy Mezzanine under Python 3.3.5 and, although I have a working site, I have a couple of questions about compatibility with the packages I need. I'm using Anaconda 2.2.0. * Installing Mezzanine with `conda` automatically downgrades my Django version to 1.6.11: is there an upcoming release that will support Django 1.7+ under Python 3? I'd like to use django-migrations. * Is there any way of using MySQL in this stack? I found I could not install MySQLdb under Python 3 and this seems to be a requirement for Mezzanine using a MySQL backend but isn't provided by Anaconda. I'm using PostgreSQL like a grown-up instead, but my preference would probably be for MySQL. * The Mezzanine docs at http://mezzanine.jupo.org/docs/user-accounts.html suggest using AUTH_PROFILE_MODULE to implement user profiles in a Mezzanine site, but the Django docs at http://django.readthedocs.org/en/latest/releases/1.5.html#auth-profile-module say that this has been deprecated since 1.5. Am I missing something here? Thanks for reading, Christian -- 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] Support for Different or Multiple Email Sending Addresses
Josh, Thanks a lot. I will look into it and update if i can get it to work. So what you are suggesting is like creating an alias. On Friday, May 15, 2015 at 9:20:33 PM UTC+5:30, Josh Cartmell wrote: Hi vikraw, I don't think there is an easy way to specify multiple email users/backends like you have. Instead, I would recommend making it so that con...@abc.com javascript: can send mail as ord...@abc.com javascript: (or vice versa). I know that specifically with Google email this is fairly easy to set up. Then mail can be sent as either address through the same smtp connection. On Fri, May 15, 2015 at 8:39 AM, vikraw vik...@gmail.com javascript: wrote: How can I get Mezzanine/Cartridge to send emails from different email addresses for various purposes? - When the user submits the contact-form email should go from con...@abc.com javascript: - When the user makes a purchase, order receipt should go from ord...@abc.com javascript: In Settings-Shop section there is 'From Email' where I put the ord...@abc.com javascript: address. BUT there is no field to specify the password and other email settings In Contact-Us page there is 'From email' where I put the con...@abc.com javascript: address. Here also there is no field to specify the password and other email settings However, in *settings.py* file. I use the following, as business accounts with gmail. But the email always arrives from the email setting later in order in the file EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'con...@abc.com javascript:' EMAIL_HOST_PASSWORD = 'password' EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'ord...@abc.com javascript:' EMAIL_HOST_PASSWORD = 'password' Please help. Need to make it look business purpose -- 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 javascript:. 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.
[mezzanine-users] Re: Using Mezzanine with Python 3: package compatibility
Hi Christian In terms of MySQL vs PostgreSQL have a look at https://docs.djangoproject.com/en/1.7/topics/migrations When I read 'PostgreSQL is the most capable of all the databases here in terms of schema support' and 'MySQL lacks support for transactions around schema alteration operations, meaning that if a migration fails to apply you will have to manually unpick the changes in order to try again (it’s impossible to roll back to an earlier point).' I decided that PostgreSQL was the best option. Cheers g On Saturday, 16 May 2015 02:32:36 UTC+12, xnx wrote: Hello Mezzanine Users, I'm new to Mezzanine but not Django: I'm enjoying learning it a lot and it does a great job, but I've run into a couple of problems. I am trying to deploy Mezzanine under Python 3.3.5 and, although I have a working site, I have a couple of questions about compatibility with the packages I need. I'm using Anaconda 2.2.0. * Installing Mezzanine with `conda` automatically downgrades my Django version to 1.6.11: is there an upcoming release that will support Django 1.7+ under Python 3? I'd like to use django-migrations. * Is there any way of using MySQL in this stack? I found I could not install MySQLdb under Python 3 and this seems to be a requirement for Mezzanine using a MySQL backend but isn't provided by Anaconda. I'm using PostgreSQL like a grown-up instead, but my preference would probably be for MySQL. * The Mezzanine docs at http://mezzanine.jupo.org/docs/user-accounts.html suggest using AUTH_PROFILE_MODULE to implement user profiles in a Mezzanine site, but the Django docs at http://django.readthedocs.org/en/latest/releases/1.5.html#auth-profile-module say that this has been deprecated since 1.5. Am I missing something here? Thanks for reading, Christian -- 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.
