[mezzanine-users] Send email on new page creation or blogpost using Mezzanine

[Michael Ketiku]

Hi everyone, I am a beginning Django developer and I am working with 
Mezzanine on my first application. As part of that I would like to find out 
how to send an email message to all users of a mezzanine site when a new 
page or blog post is created. I looked all through the mezzanine docs but 
can not find anything regarding this. Please point me in the right 
direction, I have looked at django-alerts and django-notifier but can not 
understand how to send emails to users like that. 

Thanks-
Michael 

-- 
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] Re: Django 1.10

[Rémi]

Can't wait for a new release, there are few issues that I noticed are fixed 
on the master Branch but aren't present in the 4.1.0 release... Can't wait 
:).

Thanks for the hard work.

On Monday, July 25, 2016 at 12:42:14 AM UTC-4, Stephen McDonald wrote:
>
> And here's the change for anyone interested:
>
> https://github.com/stephenmcd/mezzanine/pull/1636/files
>
> That appears to be all 1.10 issues resolved! Assuming nothing else comes 
> up, I'll try and push a new release over the coming weeks when Django 1.10 
> is released.
>
>
>
> On Mon, Jul 25, 2016 at 12:33 PM, Stephen McDonald  > wrote:
>
>>
>>
>> On Mon, Jul 25, 2016 at 11:34 AM, Stephen McDonald > > wrote:
>>
>>> Alex and I have worked out most of the remaining issues: 
>>> https://github.com/stephenmcd/mezzanine/pull/1635
>>>
>>> There's one major issue outstanding which is slightly laborious but 
>>> should be relatively straightforward, noted in the Django 1.10 release 
>>> notes (
>>> https://docs.djangoproject.com/en/dev/releases/1.10/#features-removed-in-1-10)
>>>  
>>> "Support for optparse is dropped for custom management commands."
>>>
>>> Most of the management commands in Mezzanine are broken against 1.10 due 
>>> to this, and need to be updated to use ArgumentParser - I couldn't find any 
>>> pointers on what needs to happen here, but presumably that can be worked 
>>> out but studying some of the existing commands in Django itself. If anyone 
>>> has time to work on this it'd be a huge help.
>>>
>>
>> Alex is looking at this :-)
>>  
>>
>>>
>>>
>>>
>>> On Wednesday, 22 June 2016 15:39:02 UTC+10, Stephen McDonald wrote:

 Hi all,

 Django just announced a 1.10 beta: 
 https://docs.djangoproject.com/en/1.10/releases/1.10/

 I've been testing Mezzanine against it and have been pleasantly 
 surprised at how much works, as historically this hasn't been the case. 
 I've created a task list to track all issues that have been found and 
 fixed: https://github.com/stephenmcd/mezzanine/issues/1619

 Please try it out yourself, and report anything you come across in the 
 above issue. If you do find anything, please make an effort to work out a 
 resolution too. 

 While I've unfortunately dropped the ball again on getting a release 
 out since Mezzanine 4.1 earlier this year, hopefully we can get any 
 compatibility issues with Django 1.10 ironed out quickly, and put a new 
 Mezzanine release out that coincides with that.


 -- 
 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-use...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Stephen McDonald
>> http://jupo.org
>>
>
>
>
> -- 
> 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] Re: New install of Mezzanine with NGINX & GUnicorn issues

[Jim Spoerl]

Eduardo,

I looked at the fabfile.py and it sure looks to me like the db is synced, 
at least in the restore & rollback, if not in the deploy fab commands.  Am 
I wrong about that?

On Wednesday, August 3, 2016 at 11:44:04 AM UTC-4, Eduardo Rivas wrote:
>
> Cool! Glad to see it works. 
>
> What you're describing is the standard behavior. It's assumed that your 
> development database and media files should be kept separate from the 
> production ones. We probably should mention that in the documentation. 
>
> You can manually dump the development database and restore it in the 
> server, and rsync the media files too. If you plan to do that regularly you 
> can write your own fabric task to do so. 
>

-- 
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: TypeError at /sitemap.xml isinstance() arg 2 must be a class, type, or tuple of classes and types

[Egor Poderyagin]

Still have that trouble or you find way how to render sitemap?

вторник, 10 мая 2016 г., 21:50:24 UTC+3 пользователь Ruud Schroen написал:
>
>
> Hi,
>
> Whenever I try to access /sitemap.xml, I get the following error:
>
>
> *TypeError at /sitemap.xml*
>
> isinstance() arg 2 must be a class, type, or tuple of classes and types
>
> *Request Method:*
>
>
> GET
>
>
> *Request URL:*
>
>
> http://localhost:8000/sitemap.xml
>
>
> *Django Version:*
>
>
> 1.9.6
>
>
> *Exception Type:*
>
>
> TypeError
>
>
> *Exception Value:*
>
>
> isinstance() arg 2 must be a class, type, or tuple of classes and types
>
>
> *Exception Location:*
>
>
> /Users//django_env/lib/python2.7/site-packages/django/db/models/
> fields/related.py in get_default, line 905
>
>
> *Python Executable:*
>
>
> /Users//django_env/bin/python2.7
>
>
> *Python Version:*
>
>
> 2.7.10
>
>
> I don't know what I'm doing wrong.
>
>

-- 
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] Why template path is different and rendered content is different in mezzanine?

[nikhil parmar]

I have two free themes in mezzanine - `solid & moderna` taken from - 
[HERE](https://github.com/thecodinghouse/mezzanine-themes).

I simply want to run the `HOST_THEMES` feature of `mezzanine`. So I went 
ahead and loaded both the themes in my `INSTALLED_APPS` like this - 

INSTALLED_APPS = (
"moderna",
"solid",
"django.contrib.admin",
"django.contrib.auth",
"django.contrib.contenttypes",
"django.contrib.redirects",
"django.contrib.sessions",
"django.contrib.sites",
"django.contrib.sitemaps",
"django.contrib.staticfiles",
"mezzanine.boot",
"mezzanine.conf",
"mezzanine.core",
"mezzanine.generic",
"mezzanine.pages",
"mezzanine.blog",
"mezzanine.forms",
"mezzanine.galleries",
"mezzanine.twitter",
'mezzanine_api',
'rest_framework',
'rest_framework_swagger',
'oauth2_provider',
# "mezzanine.accounts",
# "mezzanine.mobile",
)


AFter that I configured my code and ran on `0.0.0.0:8000`. Then I made two 
hosts in my `HOST_THEMES` settings like this

HOST_THEMES = [("localhost:8000", "solid"),
   ("192.168.1.130:8000", "moderna")]

Everyone wondering why the `:8000` in my hosts because of this line in code 
- `Line 25`

if host.lower() == domain.lower():
if I don't set my host with the ports the equality fails.

So after this I am debugging step by step for which templates are picking 
up.
[![Host and themes match here clearly][1]][1]


And the template directory is also correctly selected:
[![solid theme being picked up from my directory][2]][2]


[![As you can see in the `rendered_content` you will find moderna being 
rendered always because its on top and `template_name` being the template 
from `solid` directory][3]][3]


  [1]: http://i.stack.imgur.com/S8Uz9.png
  [2]: http://i.stack.imgur.com/lAzgX.png
  [3]: http://i.stack.imgur.com/LcbHx.png


What exactly I am doing wrong?

-- 
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.