Re: [mezzanine-users] Django 1.9.2 and Mezzanine 4.1.0 issue

[Stephen McDonald]

On Fri, Mar 4, 2016 at 9:45 AM, Ryne Everett <ryneever...@gmail.com> wrote:

> Before doing anything, discuss it on the mezzanine-users mailing list
>>> first.
>>
>>
> Perhaps I'm wrong, but my interpretation is that this is to save
> contributors effort on patches that will not be accepted, not to reduce the
> number of pull requests.
>

That's right.


>
> On Thu, Mar 3, 2016 at 10:18 AM, <vla...@zunzun.se> wrote:
>
>> Hi colleagues,
>>
>>   Some days ago I opened this issue
>> https://github.com/stephenmcd/mezzanine/issues/1542, and you can find
>> here the patch I have coded for it
>> https://github.com/vladir/mezzanine/commit/363faf3a6f84b5caad339cdada0904d6e5f0ea61,
>> I was thinking into opening a Pull Request for it, but it is clear on the
>> Contributing section that:
>>
>
The patch looks fine, please create a PR, thanks!


>
>>Before doing anything, discuss it on the mezzanine-users
>> <http://groups.google.com/group/mezzanine-users/topics> mailing list
>> first.
>>
>> So better if I firstly consult it here with you (although I have not
>> followed properly the contributing tips this time, sorry, I will do the
>> next time).
>>
>> Any help will be appreciated.
>>
>> Thanks in advance.
>>
>> --
>> 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] User accounts documentation needs a small update

[Stephen McDonald]

PR greatly appreciated. :-)

On Sat, Apr 23, 2016 at 1:53 AM, Melarish Ish <melar...@gmail.com> wrote:

> In http://mezzanine.jupo.org/docs/user-accounts.html it says "Profiles
> are implemented via Django’s AUTH_PROFILE_MODULE setting." However,
> that's deprecated since Django 1.7 (
> https://docs.djangoproject.com/en/dev/releases/1.5/#auth-profile-module).
> Current implementation of custom profiles is:
> https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-the-existing-user-model
> And where it says Django docs for profiles
> <https://docs.djangoproject.com/en/1.4/topics/auth/#storing-additional-information-about-users>
> (
> https://docs.djangoproject.com/en/1.4/topics/auth/#storing-additional-information-about-users)
> - that link is a 404.
>
> It might also affect the following part "Mezzanine will expose all
> relevant user and profile fields available in the signup and update profile
> forms", as it doesn't seem to expose anything from the extended user model.
> Not sure if that's already been noted anywhere.
>
> --
> 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] Suggestion on how to make import and export of products using csv from admin panel?

[Stephen McDonald]

There's a potentially outdated CSV import script here:

https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/management/commands/product_db.py

That should get you 90% of the way

On Sat, Apr 30, 2016 at 4:06 AM, Sathish Anton <sathish.an...@gmail.com>
wrote:

> Hi,
> Please provide Suggestion on how to make import and export of products
> using csv from admin panel?
>
> Thanks and Regards,
> Sathish Anton. A
>
> --
> 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] Introducing Cartridge Downloads

[Stephen McDonald]

Looks awesome Ryne!

BTW custom products is the missing feature that's held back Cartridge
reaching a 1.0 status, so thanks from everyone for working on that. I've
been out of action over the last month and the next few weeks as well, but
once I get back to the backlog I'll be sure to tackle the PR.

On Wed, May 11, 2016 at 7:53 AM, Ryne Everett <ryneever...@gmail.com> wrote:

> I wrote a reusable app adding digital product support to Cartridge:
> https://github.com/ryneeverett/cartridge-downloads.
>
> I initially implemented a `DownloadProduct` as a subclass of `Product`
> using a custom products branch of Cartridge (
> https://github.com/stephenmcd/cartridge/pull/293), but it didn't prove
> necessary or even advantageous for this use case. I could see where this
> feature would be needed in more complex use cases though.
>
> Feedback and suggestions welcome, especially from the many people I know
> (from the mailing list archives) have implemented downloadable products in
> their own cartridge projects over the years.
>
> --
> 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] Templates

[Stephen McDonald]

See https://github.com/stephenmcd/mezzanine/issues/1512

On Mon, Apr 18, 2016 at 8:08 PM, Cameron Burnett <cameron...@gmail.com>
wrote:

> Probably an easy question. I'm just a little confused about how the
> templates are meant to work. I'm using Mezzanine 4.1.0, Django 1.8.11, and
> Python 3.3.6.
>
> If I run...
>
> python manage.py collecttemplates -t base.html
>
>
> I get the following traceback...
>
> Traceback (most recent call last):
>   File "manage.py", line 14, in 
> execute_from_command_line(sys.argv)
>   File
> "/home/cameron/.pyenv/versions/django18/lib/python3.3/site-packages/django/core/management/__init__.py",
> line 354, in execute_from_command_line
> utility.execute()
>   File
> "/home/cameron/.pyenv/versions/django18/lib/python3.3/site-packages/django/core/management/__init__.py",
> line 346, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File
> "/home/cameron/.pyenv/versions/django18/lib/python3.3/site-packages/django/core/management/base.py",
> line 394, in run_from_argv
> self.execute(*args, **cmd_options)
>   File
> "/home/cameron/.pyenv/versions/django18/lib/python3.3/site-packages/django/core/management/base.py",
> line 445, in execute
> output = self.handle(*args, **options)
>   File
> "/home/cameron/.pyenv/versions/django18/lib/python3.3/site-packages/mezzanine/core/management/commands/collecttemplates.py",
> line 42, in handle
> to_dir = settings.TEMPLATE_DIRS[0]
> IndexError: tuple index out of range
>
>
> So I added the following to settings.py which solved my problem but I got
> a message saying that it was no longer the way to do it...
>
> TEMPLATE_DIRS = (
> PROJECT_ROOT + '/templates',
> )
>
> WARNINGS:
> ?: (1_8.W001) The standalone TEMPLATE_* settings were deprecated in Django
> 1.8 and the TEMPLATES dictionary takes precedence. You must put the values
> of the following settings into your default TEMPLATES dict: TEMPLATE_DIRS.
>
> Copied 1 template
>
>
>
> The TEMPLATES section is just standard. I haven't changed it. It's already
> got a path for "templates" but it doesn't seem to use it.
>
> TEMPLATES = [
> {
> "BACKEND": "django.template.backends.django.DjangoTemplates",
> "DIRS": [
> os.path.join(PROJECT_ROOT, "templates")
> ],
> "APP_DIRS": True,
> "OPTIONS": {
> "context_processors": [
> "django.contrib.auth.context_processors.auth",
> "django.contrib.messages.context_processors.messages",
> "django.template.context_processors.debug",
> "django.template.context_processors.i18n",
> "django.template.context_processors.static",
> "django.template.context_processors.media",
> "django.template.context_processors.request",
> "django.template.context_processors.tz",
> "mezzanine.conf.context_processors.settings",
> "mezzanine.pages.context_processors.page",
> ],
>     "builtins": [
> "mezzanine.template.loader_tags",
> ],
> },
> },
> ]
>
>
>
> So, how am I meant to do it???
>
> Thanks.
>
> --
> 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] drum

[Stephen McDonald]

Thanks for the report, it's fixed:

https://github.com/stephenmcd/drum/issues/32

PS: Please don't double-post.

On Mon, Apr 18, 2016 at 6:09 AM, Icham Achtir <iach...@gmail.com> wrote:

>
> Hi,
>
> i have some issue with drum & django 1.9
>
> i think is linked with the following warning:
>
> /home/keiser1080/.virtualenvs/pypy-env/site-packages/mezzanine/core/models.py:390:
> RemovedInDjango19Warning: Model class mezzanine.pages.models.Page doesn't
> declare an explicit app_label and either isn't in an application in
> INSTALLED_APPS or else was imported before its application was loaded. This
> will no longer be supported in Django 1.9.
>   return super(OrderableBase, cls).__new__(cls, name, bases, attrs)
>
> /home/keiser1080/.virtualenvs/pypy-env/site-packages/mezzanine/core/models.py:390:
> RemovedInDjango19Warning: Model class mezzanine.pages.models.RichTextPage
> doesn't declare an explicit app_label and either isn't in an application in
> INSTALLED_APPS or else was imported before its application was loaded. This
> will no longer be supported in Django 1.9.
>   return super(OrderableBase, cls).__new__(cls, name, bases, attrs)
>
> /home/keiser1080/.virtualenvs/pypy-env/site-packages/mezzanine/core/models.py:390:
> RemovedInDjango19Warning: Model class mezzanine.pages.models.Link doesn't
> declare an explicit app_label and either isn't in an application in
> INSTALLED_APPS or else was imported before its application was loaded. This
> will no longer be supported in Django 1.9.
>   return super(OrderableBase, cls).__new__(cls, name, bases, attrs)
>
>
> Could you help ?
>
> --
> 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] Cartridge: Skip payment step when cart total is 0

[Stephen McDonald]

I added an issue here: https://github.com/stephenmcd/cartridge/issues/303

On Tue, Jul 26, 2016 at 6:31 AM, Stephen McDonald <st...@jupo.org> wrote:

> Sounds like something we should implement in cartridge.
>
> On 26 Jul 2016 6:28 AM, "Rémi" <r.fatche...@gmail.com> wrote:
>
>> Hello,
>>
>> I have a site with downloadable products. Some of them are free and are
>> part of the regular chekout flow (I do some processing once the order is
>> complete, to record downloads and such). I'm looking for an easy way to
>> skip the payment step if the cart is equal to zero (only contains free
>> products). Does anyone ever encounter such scenario?
>>
>> Thanks.
>>
>> --
>> 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] Drum auto tags issue.

[Stephen McDonald]

On Thu, Jul 14, 2016 at 5:31 PM, Lyric Wei <5h3l...@gmail.com> wrote:

> > If you have a bug fix, please go ahead and submit it in a pull request
> via Github.
>
> I am trying to fix it, not yet. I am not familiar with django. But I
> though it's a bug in mezzanine.core.models.
>

I think the fix you mentioned is correct. If I recall it's related to a
change between Django 1.8 and 1.9, and we made the same fix in Mezzanine
already, but Drum was not updated presumably. I can submit the fix if you
really don't want to, but I encourage you to.


>
> > What do you mean?
>
> I am requesting a new feature, the tags should support non-character based
> languages, like Japanese, Arabic, Chinese, etc.
>
> the current keywords extract approach doesn't support those languages.
>
> Maybe we can allow user to add tag when they add new links, manually
> adding tags, but simple.
>
> or
>
> Drum support different keywords extract approaches, to extract keywords
> from non-character based languages.
>
> Btw, words in those non-character based languages are not split by *space*
> and *symbols*.That's why I say "different keywords extract approaches". for
> example,
>
> In English, we say "This morning, the weather is good", can be split as
> "This", "morning", "the", "weather", "is", "good" by space and symbols.
>
> In Japanese, we say 今朝は天気が良いです, can be split as "今朝", "は", "天気", "が",
>  "良い",  "です", according to the grammar, not the space and symbols.
>
> In Chinese, we say 今天早上天气不错, can be split as "今天", "早上", "天气", "不错",
>  according to the grammar either, not the space and symbols.
>

That's excellent info, thanks for going into detail there.

Do you think it's possible to programmatically extract tags in those
languages, using different logic? If so we can make the extract function
configurable by the developer.


>
>
>
>
>
>
> On Thursday, July 14, 2016 at 3:11:21 PM UTC+8, Stephen McDonald wrote:
>
>>
>>
>> On Thu, Jul 14, 2016 at 4:54 PM, Lyric Wei <5h3...@gmail.com> wrote:
>>
>>> Thank you for quick response. Now django show me the follow error
>>> message in /usr/local/lib/python2.7/dist-packages/drum/links/models.py
>>>
>>> >  self.keywords.add(AssignedKeyword(keyword=keyword))
>>>
>>> >  instance isn't saved. Use bulk=False or save the object first.
>>>
>>> I check out the code and found how to resolve it. I have to pass
>>> bulk=False to save method to bypass.
>>>
>>
>> If you have a bug fix, please go ahead and submit it in a pull request
>> via Github.
>>
>>
>>>
>>> Oh yes, the more important question. Is it possible to add an existed
>>> tag manually when user adding a link?
>>>
>>> Because I am using drum for international site, a lot of  languages,
>>> like Japanese, Korean, Arabic, Chinese, are not supported by the keyword
>>> extract method drum is using, which i found it in `save` method.
>>>
>>
>> What do you mean?
>>
>>
>>>
>>> I though there are two approaches to solve the problem, to support
>>> different language:
>>>
>>> 1. allow visitors who submit the link to add tags either.
>>> 2. allow drum to support different word extract method, which i suppose
>>> the user can specified in settings.py.
>>>
>>> I thought the first is easy, but 2nd is more powerful.
>>>
>>> On Thursday, July 14, 2016 at 9:53:22 AM UTC+8, Stephen McDonald wrote:
>>>>
>>>> In Mezzanine they're called "keywords", so you should see that.
>>>>
>>>> I've just updated the readme to mention that.
>>>>
>>>> On Wed, Jul 13, 2016 at 10:31 PM, Lyric Wei <5h3...@gmail.com> wrote:
>>>>
>>>>> Hi there,
>>>>>
>>>>> I am using drum(https://github.com/stephenmcd/drum) as a news social
>>>>> website. drum is a Reddit / Hacker News clone for Mezzanine.
>>>>>
>>>>> Its document mentioned that
>>>>>
>>>>> > This means that for auto-tagging to work, the tags must already
>>>>> exist in the database. You can either add them manually via the admin...
>>>>>
>>>>> But I can't find the way to add existed tags in the admin panel. Could
>>>>> you help me?
>>>>>
>>>>> Thank you.
>

Re: [mezzanine-users] Re: Django 1.10

[Stephen McDonald]

On Mon, Jul 25, 2016 at 11:34 AM, Stephen McDonald <stephen...@gmail.com>
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-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] Re: Django 1.10

[Stephen McDonald]

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.



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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Django 1.10

[Stephen McDonald]

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 <st...@jupo.org> wrote:

>
>
> On Mon, Jul 25, 2016 at 11:34 AM, Stephen McDonald <stephen...@gmail.com>
> 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-users+unsubscr...@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] Cartridge: Skip payment step when cart total is 0

[Stephen McDonald]

Sounds like something we should implement in cartridge.

On 26 Jul 2016 6:28 AM, "Rémi"  wrote:

> Hello,
>
> I have a site with downloadable products. Some of them are free and are
> part of the regular chekout flow (I do some processing once the order is
> complete, to record downloads and such). I'm looking for an easy way to
> skip the payment step if the cart is equal to zero (only contains free
> products). Does anyone ever encounter such scenario?
>
> Thanks.
>
> --
> 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.

[mezzanine-users] Mezzanine 4.2.0 released

[Stephen McDonald]

Hi all,

I've just released Mezzanine 4.2.0 - it contains support for Django 1.10,
as well as including a long list of bug-fixes which were yet to be
released, since 4.1.0 came out 6 months ago.

One other major new feature 4.2 brings is a new "Content Typed"
abstraction. This is the result of refactoring out the parts of Mezzanine's
Page model that provide the system for subclassing it, and having the admin
interface allow you to choose from the different subclasses when creating
new instances. This means you can build your own subclassable models that
work just like Mezzanine's Page models do. We'll use this in the future to
provide custom Product types in Cartridge. You can see the work that was
done here: https://github.com/stephenmcd/mezzanine/pull/1612

A huge thanks goes out to Ryne Everett, Alex Hill and Ed Rivas, who have
been the primary providers of maintenance and support going into this
release - it wouldn't be possible without their efforts, so thank you!



-- 
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] Drum auto tags issue.

[Stephen McDonald]

On Thu, Jul 14, 2016 at 4:54 PM, Lyric Wei <5h3l...@gmail.com> wrote:

> Thank you for quick response. Now django show me the follow error message
> in /usr/local/lib/python2.7/dist-packages/drum/links/models.py
>
> >  self.keywords.add(AssignedKeyword(keyword=keyword))
>
> >  instance isn't saved. Use bulk=False or save the object first.
>
> I check out the code and found how to resolve it. I have to pass
> bulk=False to save method to bypass.
>

If you have a bug fix, please go ahead and submit it in a pull request via
Github.


>
> Oh yes, the more important question. Is it possible to add an existed tag
> manually when user adding a link?
>
> Because I am using drum for international site, a lot of  languages, like
> Japanese, Korean, Arabic, Chinese, are not supported by the keyword extract
> method drum is using, which i found it in `save` method.
>

What do you mean?


>
> I though there are two approaches to solve the problem, to support
> different language:
>
> 1. allow visitors who submit the link to add tags either.
> 2. allow drum to support different word extract method, which i suppose
> the user can specified in settings.py.
>
> I thought the first is easy, but 2nd is more powerful.
>
> On Thursday, July 14, 2016 at 9:53:22 AM UTC+8, Stephen McDonald wrote:
>>
>> In Mezzanine they're called "keywords", so you should see that.
>>
>> I've just updated the readme to mention that.
>>
>> On Wed, Jul 13, 2016 at 10:31 PM, Lyric Wei <5h3...@gmail.com> wrote:
>>
>>> Hi there,
>>>
>>> I am using drum(https://github.com/stephenmcd/drum) as a news social
>>> website. drum is a Reddit / Hacker News clone for Mezzanine.
>>>
>>> Its document mentioned that
>>>
>>> > This means that for auto-tagging to work, the tags must already exist
>>> in the database. You can either add them manually via the admin...
>>>
>>> But I can't find the way to add existed tags in the admin panel. Could
>>> you help me?
>>>
>>> Thank you.
>>>
>>> --
>>> 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
>>
> --
> 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] tel: being stripped from anchor href when saving a RichTextField. How do I allow it?

[Stephen McDonald]

I did a bit of digging and it's a known issue with the "bleach" library we
use to sanitize HTML:

https://github.com/mozilla/bleach/issues/102

I've added the patch mentioned in the issue and it appears to work:

https://github.com/stephenmcd/mezzanine/commit/a50da71da521b3fb03f8b089736eca9656e71bbb

Prior to upgrading, you might be able to do the same in your project's code
somewhere, possibly its settings.py module.

On Thu, Jul 21, 2016 at 12:18 PM, RandomDude <ab16...@gmail.com> wrote:

> Version: Mezzanine (4.0.1)
>
>
> Mailto before save:
>
> mailto:some...@example.com?Subject=Hello%20again;>Send
> Mail
>
> After save: (works!)
>
> mailto:some...@example.com?Subject=Hello%20again;>Send
> Mail
>
> Click to call tel before save:
>
> +1 (303) 499-7111
>
> After save: (href stripped out)
>
> +1 (303) 499-7111
>
> Here are my rich text settings:
>
> RICHTEXT_ALLOWED_TAGS =
> ('p','h1','h2','h3','h4','h5','h6','ol','ul','li','strong','table','caption','thead','tbody','tr','th','td','br','a',
> 'em')
> RICHTEXT_ALLOWED_ATTRIBUTES = ('href')
>
> The following are not in used in my settings.py file.
>
> RICHTEXT_ALLOWED_STYLES
> RICHTEXT_FILTER
> RICHTEXT_FILTERS
> RICHTEXT_FILTER_LEVEL
> RICHTEXT_WIDGET_CLASS
>
> How do I prevent tel: from being stripped out please?
>
> --
> 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] Feature Request - Scheduled publishing for exsiting content #411

[Stephen McDonald]

Suggest reading this thread where we discussed how workflow would work:

https://groups.google.com/forum/#!msg/mezzanine-users/4vr3IWT-8UM/ORcbKB_CNeAJ

Your option 2) sounds like a subset of what's described there.

On Sat, Jul 16, 2016 at 4:42 PM, Shaurya Chaudhuri <shaur...@gmail.com>
wrote:

> *Feature Request - Scheduled publishing for exsiting content #411*
>
> I have two approaches for this problem
>
> 1) Implement an update queue, where the user would update the post/page
> and schedule multiple updates that would be published in the future.
> Ex:-
> A) I update the post to be updated @ 12 AM. Then i update the post to be
> updated at 3 AM.
> Then the post would be updated at 12 AM and then subsequently update at 3
> AM.
> For this we would need to implement another model for updates.
> With the old data we can do 2 things
> I) Delete the update data after they have been updated.
> II) Keep the data in the DB , for future references to the update.
>
>
> 2) Implement a singular future update option. The user would update the
> post and schedule it, and if he updates again before the content going live
> it would be overwritten.
> Ex:-
> I update for data to be published at 12 AM then i again update to be
> published at 3 AM. then the post will be updated at 3 AM, as i ovewrote the
> update whichw as to happen at 12AM.
> For this there would be a need to have an update model as well.
>
> These are the high level conceptualisation of the feature. Would proceed
> once you guys review it and tell me what should be better to implement.
>
> Regards
> Shaurya
>
> --
> 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] Drum auto tags issue.

[Stephen McDonald]

On Fri, Jul 15, 2016 at 2:33 PM, Lyric Wei <5h3l...@gmail.com> wrote:

> I think the fix you mentioned is correct. If I recall it's related to a
>> change between Django 1.8 and 1.9, and we made the same fix in Mezzanine
>> already, but Drum was not updated presumably. I can submit the fix if you
>> really don't want to, but I encourage you to.
>>
>>
> Oh, I am glad to do that.. I don't find source code of Mezzanine in Drum
> project, but I got this:
> https://github.com/stephenmcd/drum/blob/master/setup.py#L54 . Since you
> have made the fix in latest Mezzanine, I can simply change this line, from
> "mezzanine >= 4.0.1" to "mezzanine >= 4.1.0", am i right?
>

That needs to happen, but it's separate from the fix - what I meant was
that Drum literally needs the same change that was applied to Mezzanine.

I've bumped the version here:
https://github.com/stephenmcd/drum/commit/177a202e012ac4c65a5aa2aa289b11008a1c62b7
And made the fix here:
https://github.com/stephenmcd/drum/commit/7b327615a93ee4fa04d595b53d20f9d9f34db925


>
> That's excellent info, thanks for going into detail there.
>>
>> Do you think it's possible to programmatically extract tags in those
>> languages, using different logic? If so we can make the extract function
>> configurable by the developer.
>>
>
> Yes. Search engines like Google need this kind of technology to create
> indexes for each words to support different languages. And there are
> several existed open source projects to extract tags in those languages.
>
> A famous project named JieBa(https://github.com/fxsjy/jieba): a chinese
> text segmentation project in Python, which use dictionary and statistical
> result to extract words, also works for Japanese if we provide suitable
> dictionary.
>

I've made the tag extraction configurable now, see here:
https://github.com/stephenmcd/drum/commit/147984d813c54996e0b97f32959fdd3992bf509d


>
>
> On Friday, July 15, 2016 at 7:38:45 AM UTC+8, Stephen McDonald wrote:
>
>>
>>
>> On Thu, Jul 14, 2016 at 5:31 PM, Lyric Wei <5h3...@gmail.com> wrote:
>>
>>> > If you have a bug fix, please go ahead and submit it in a pull request
>>> via Github.
>>>
>>> I am trying to fix it, not yet. I am not familiar with django. But I
>>> though it's a bug in mezzanine.core.models.
>>>
>>
>> I think the fix you mentioned is correct. If I recall it's related to a
>> change between Django 1.8 and 1.9, and we made the same fix in Mezzanine
>> already, but Drum was not updated presumably. I can submit the fix if you
>> really don't want to, but I encourage you to.
>>
>>
>>>
>>> > What do you mean?
>>>
>>> I am requesting a new feature, the tags should support non-character
>>> based languages, like Japanese, Arabic, Chinese, etc.
>>>
>>> the current keywords extract approach doesn't support those languages.
>>>
>>> Maybe we can allow user to add tag when they add new links, manually
>>> adding tags, but simple.
>>>
>>> or
>>>
>>> Drum support different keywords extract approaches, to extract keywords
>>> from non-character based languages.
>>>
>>> Btw, words in those non-character based languages are not split by
>>> *space* and *symbols*.That's why I say "different keywords extract
>>> approaches". for example,
>>>
>>> In English, we say "This morning, the weather is good", can be split as
>>> "This", "morning", "the", "weather", "is", "good" by space and symbols.
>>>
>>> In Japanese, we say 今朝は天気が良いです, can be split as "今朝", "は", "天気", "が",
>>>  "良い",  "です", according to the grammar, not the space and symbols.
>>>
>>> In Chinese, we say 今天早上天气不错, can be split as "今天", "早上", "天气", "不错",
>>>  according to the grammar either, not the space and symbols.
>>>
>>
>> That's excellent info, thanks for going into detail there.
>>
>> Do you think it's possible to programmatically extract tags in those
>> languages, using different logic? If so we can make the extract function
>> configurable by the developer.
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thursday, July 14, 2016 at 3:11:21 PM UTC+8, Stephen McDonald wrote:
>>>
>>>>
>>>>
>>>> On Thu, Jul 14, 2016 at 4:54 PM, Lyric Wei <5h3...@gmail.com>

Re: [mezzanine-users] Sending an email to admins on new user profile creation

[Stephen McDonald]

On Wed, Feb 1, 2017 at 8:46 AM, Christian Hill <xn.h...@gmail.com> wrote:

> Presumably UserProfile is saved twice and I'm only picking up the first
> time, after it's been attached to a user but before the extra data is
> attached to it.


If that's true, then the signal handler would run each time, which means
you could then modify it to check for the expected data (affiliation) and
only send the email then.


-- 
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] [Cartridge] - Admin links to custom product type no longer work

[Stephen McDonald]

y
> product and none of my extended fields, I'm aware that there have been some
> pretty major changes that happened in commit #8d3ac6b
> <https://github.com/stephenmcd/cartridge/commit/8d3ac6bef9ca4f557edcd4d714a02f69644570dc#diff-79b579f857f436c0b1f13b7397ed6c00>
>  however
> I am currently at a loss trying to figure out what I need to do to get this
> working again.
>
> Any suggestions are greatly appreciated.
>
> --
> 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] displayable_link.js is not generated - development server

[Stephen McDonald]

Just pushed a fix for this:

https://github.com/stephenmcd/mezzanine/commit/23c15f8b78f440a6a81e686fcd4ef772d44854bd

On Fri, Jan 27, 2017 at 12:08 PM, Danny <molo...@gmail.com> wrote:

> Hi Lucas,
>
> I've also just noticed that the "Link List" feature is no longer working
> as of Mezzanine 4.2.2 (on either the admin side or the front end) and is
> still broken at HEAD.
> It appears to be some ordering error with regards to when tinymce_setup.js
> is executed vs when the scripts in admin/base_site.html or
> editable_loader.html are parsed to set up the window.__link_list_url
> variable.
>
> I've opened this issue: https://github.com/stephenmcd/
> mezzanine/issues/1728
>
> However, Javascript is not my forte, so debugging this is a little beyond
> me. Hopefully someone else can assist.
>
> [BTW, if you're worried about displayable_links.js not being generated
> properly, just visit admin/displayable_links.js directly - and if it
> returns you a lovely structure of links, then that isn't your issue.]
>
> Best of luck,
>
> Seeya. Danny.
>
>
> On 25/01/2017 7:32 AM, Lucas Corso wrote:
>
> Hello, I have more or less the same problem that Danny presents at:
>
> --> https://groups.google.com/forum/#!searchin/mezzanine-
> users/displayable_links.js|sort:relevance/mezzanine-
> users/6ZgJtRF9VWk/6cR6p0cnAwAJ
>
>
> In my case I'm running mezzanine on a development server, at first I
> thought it was some missing package, but then I realized that the problem
> was that displayable_link.js was not being generated when I clicked the
> link button on the panel Tools to publish.
>
>
>
>
>
> <https://lh3.googleusercontent.com/-xJPQhfn95Fs/WIe-Y2DWnsI/AA0/4oXksV97trY6Iyyp_fawC5-6FKiwwBEnwCLcB/s1600/1.png>
>
> What has worked so far is what clarifies Danny to delete templates / admin
> / base_site.html and if it works
>
>
>
> <https://lh3.googleusercontent.com/-A0jOffWzUxU/WIe_kp2xY0I/AA8/cXB-dUmn16McVDb7IeN7FE395gpJ1c76wCLcB/s1600/2.png>
>
> But some styles are lost in the administration site
>
>
>
> <https://lh3.googleusercontent.com/-1l3NeW4-YgU/WIe_7Ya-rtI/ABA/3itvXt0JijEbUwg0iR_Rn19CtwzxaYQrQCLcB/s1600/3.png>
>
> Compared to the normal style
>
>
> <https://lh3.googleusercontent.com/-xt1RI2MmRJ0/WIfAUwSH0UI/ABE/GM1c6auKY5UOLgfVXy-vL82YzABvhN4EACLcB/s1600/4.png>
>
> What could I do to fix it? Thanks for reading...
>
>
>
>
> --
> 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] Can't upload images

[Stephen McDonald]

On Mon, Feb 6, 2017 at 10:07 AM, marvel tales <marvelta...@gmail.com> wrote:

> Thank you very much for your answer.
> I am very new to Mezzanine CMS.
> Could you please guide me to a source which shows how to properly update
> Mezzanine and dependencies.
> As now what I am thinking is, creating a new virtualenv and installing
> everything from the beginning  fresh.
> I don't know if it is a good way of doing things.
>

That should work


> Many thanks
>
>
> On Sunday, February 5, 2017 at 11:44:56 PM UTC+1, Stephen McDonald wrote:
>>
>> Looks like you're using an older version that depends on the Flash
>> plugin. So you can either install that, or upgrade Mezzanine +
>> dependencies.
>>
>> On 2/6/17, marvel tales <marve...@gmail.com> wrote:
>> > Hello,
>> >
>> > I am having an issue with image upload on Mezzanine CMS. I have this
>> screen
>> >
>> > on Mozilla.
>> >
>> >
>> > And this screen on Chrome
>> >
>> > I will appreciate a lot if someone can help me.
>> >
>> > Thanks in advance
>> >
>> >
>> >
>> > --
>> > 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
>>
> --
> 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] Can't upload images

[Stephen McDonald]

Looks like you're using an older version that depends on the Flash
plugin. So you can either install that, or upgrade Mezzanine +
dependencies.

On 2/6/17, marvel tales <marvelta...@gmail.com> wrote:
> Hello,
>
> I am having an issue with image upload on Mezzanine CMS. I have this screen
>
> on Mozilla.
>
>
> And this screen on Chrome
>
> I will appreciate a lot if someone can help me.
>
> Thanks in advance
>
>
>
> --
> 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] Sending an email to admins on new user profile creation

[Stephen McDonald]

Just spent some time looking into this - there's actually a setting
ACCOUNTS_PROFILE_FORM_CLASS (
http://mezzanine.jupo.org/docs/configuration.html#accounts-profile-form-class)
which allows you to specify a custom form class for user profile
signup/update. You could override the save method of it and send an email
via that, something like (untested):

# settings.py

ACCOUNTS_PROFILE_FORM_CLASS = "myapp.forms.MyCustomProfileForm"

# myapp.forms.py

from mezzanine.account.forms import ProfileForm

class MyCustomProfileForm(ProfileForm):
def save(self, *args, **kwargs):
user = super(MyCustomProfileForm, self).save(*args, **kwargs)
if self._signup:
# send email
return user

On Thu, Feb 2, 2017 at 10:02 PM, Christian Hill <xn.h...@gmail.com> wrote:

> Unfortunately, I don't think this will work very reliably: the time of
> update and time of creation will be a little bit different, so I can't
> check for strict equality, but the two UserProfile save events occur close
> together, so I can't choose a reliable timedelta to ascertain whether the
> instance is begin saved the first time or the second time. For example, the
> output from
>
> def email_admins_on_new_signup(sender, instance, **kwargs):
> print('created:', instance.profile_created)
> print('updated:', instance.profile_updated)
>
> is:
>
> created: 2017-02-02 10:53:51.575074+00:00
> updated: 2017-02-02 10:53:51.575115+00:00
> created: 2017-02-02 10:53:51.575074+00:00
> updated: 2017-02-02 10:53:51.578555+00:00
>
> A workaround is:
> if not kwargs['created'] and instance.profile_updated -
> instance.profile_created < timedelta(seconds=5):
> # Only send an email if a new UserProfile was created.
> send_signup_alert_email_to_admins(instance)
>
> – i.e. only send the email if the instance save is after initial creation,
> but within 5 seconds of it, but that feels awfully hacky and I'd love a
> better solution.
>
>
> On 2 February 2017 at 03:08, Melvyn Sopacua <m.r.sopa...@gmail.com> wrote:
>
>> On Wednesday 01 February 2017 07:02:30 Christian Hill wrote:
>>
>> > And I don't want
>>
>> > the email sent if the user is simply editing their profile.
>>
>> > Would I be better off customizing the accounts app?
>>
>>
>>
>> Add two fields to your profile:
>>
>>    - profile_created: DateTimeField(auto_now_add=True)
>>- profile_updated: DateTimeField(auto_now=True)
>>
>> If they're equal, you send mail.
>>
>>
>>
>> >
>>
>> > On 1 February 2017 at 00:27, Stephen McDonald <st...@jupo.org> wrote:
>>
>> > > On Wed, Feb 1, 2017 at 8:46 AM, Christian Hill <xn.h...@gmail.com>
>> wrote:
>>
>> > >> Presumably UserProfile is saved twice and I'm only picking up the
>>
>> > >> first time, after it's been attached to a user but before the
>>
>> > >> extra data is attached to it.
>>
>> > >
>>
>> > > If that's true, then the signal handler would run each time, which
>>
>> > > means you could then modify it to check for the expected data
>>
>> > > (affiliation) and only send the email then.
>>
>> > >
>>
>> > >
>>
>> > > --
>>
>> > > 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.
>>
>>
>>
>> --
>>
>> Melvyn Sopacua
>>
>> --
>> 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.
>>
>
>
>
> --
> My book, Learning Scientific Programming with Python is published by CUP
> <http://www.cambridge.org/gb/academic/subjects/physics/computational-science-and-modelling/learning-scientific-programming-python?format=PB>
> scipython.com: | @scipython3 <https://twitter.com/scipython3>
>
>
> --
> 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] staff member unable to login to admin

[Stephen McDonald]

On Mon, Jan 30, 2017 at 3:42 AM, CJWalther <cjwalt...@gmail.com> wrote:

> Hi
>
> On Sunday, January 29, 2017 at 3:40:46 AM UTC+1, Akhlaq Rao wrote:
>>
>> Sorry I miss interpreted, did you select the site while creating this
>> user?
>>
>>
> I just tried with adding yet another user: While creating it in the first
> step there is no site to select. This comes in a second step while
> configuring the user account. There there is only one site entry (
> 127.0.0.1:8000) and selecting, meaning highlighting it, not only doesn't
> change anything but also is kind of counter-intuitive...
>

You're right it's not very intuitive. Like Ryne said we recently added a
warning message when you edit the user without selecting site permissions.
Perhaps we could also make the site selection step automatic when only one
site exists.

As for your issue though, I can't reproduce it. I create a user without
selecting the site, and they get the same error as you do. Then after
selecting the (one and only) site for that user, they can then access the
(empty looking, sans individual edit/group permissions being given) admin
area.

To go into a bit more detail on the common mistake Ryne mentioned - be sure
to *actually select* the site. It's a multi-select list that contains one
or more sites in it, their presence in the form field merely indicates that
they're a site that's available to grant permission to - you still need to
select each (and in your case only) one.

If you've certainly definitely absolutely 100% done that, and triple
checked that your selection persisted when you saved the user by going to
the edit view again and checking it, then I can only suggest that the host
for the site isn't matching the host being used to access the site when
trying to log into the admin area. If you're developing locally, you're
probably using a port number other than 80, so the host in the site record
should contain that too, eg 127.0.0.1:8000 and not just 127.0.0.1. Also
note that "localhost" and "127.0.0.1" are not the same thing for this
purpose - the site checking code doesn't perform DNS lookups, it just
literally compares the host header (of the browser requesting the site) to
the value you entered into the admin for the site record. (Note that all
this should be done for you automatically during development if you
followed the documented setup instructions.)

If you're not doing the standard local development setup, and are using a
separate web server to proxy requests to the Django app, be sure it's also
configured correctly to pass on the HTTP_HOST header. If you have say nginx
serving on mysite.com and proxying requests to the Django app listening on
127.0.0.1:8000, the host header the Django app will see will be
127.0.0.1:8000 if nginx doesn't pass on the correct host header (mysite.com
).

Hope this helps.







>
>
> --
> 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] Re: Can't get gallery to work with existing django project

[Stephen McDonald]

You didn't post the error.

On Tue, Feb 14, 2017 at 4:35 AM, Bernardo Tavares <bhd...@gmail.com> wrote:

>
>
> Em segunda-feira, 13 de fevereiro de 2017 15:32:46 UTC-2, Bernardo Tavares
> escreveu:
>>
>> Hi,
>>
>> I'm trying to plug in mezzanine's blog and gallery system into and
>> existing website. After pluging in 'mezzanine.urls', the blog worked like a
>> charm, but i can't get the gallery to work. I can't seem to find the
>> configuration for the '/gallery/' url either.
>>
>
>
> I'm getting the following error when trying to access the url:
>
> Request Method: GET
> Request URL: http://127.0.0.1:8000/gallery/
> Raised by: mezzanine.pages.views.page
>
>
>
>
>> Here is my main 'urls.py' file:
>>
>> from django.conf.urls import include, url
>> from django.contrib import admin
>> from main import urls as mainUrls
>> import mezzanine.urls as mezzanineUrls
>>
>> urlpatterns = (
>> url(r'^', include(mainUrls)),
>> url(r'^', include(mezzanineUrls)),
>> url(r'^admin/', include(admin.site.urls)),
>> )
>>
>>
>> Here is my installed apps:
>>
>> INSTALLED_APPS = (
>> "django.contrib.admin",
>> "django.contrib.auth",
>> "django.contrib.contenttypes",
>> "django.contrib.redirects",
>> "django.contrib.sessions",
>> "django.contrib.sites",
>> "django.contrib.sitemaps",
>> "django.contrib.staticfiles",
>> "django.contrib.messages",
>> 'main',
>> 'custom_mezzanine',
>> "mezzanine.boot",
>> "mezzanine.conf",
>> "mezzanine.core",
>> "mezzanine.generic",
>> "mezzanine.pages",
>> "mezzanine.blog",
>> "mezzanine.forms",
>> "mezzanine.galleries",
>> #"mezzanine.twitter",
>> # "mezzanine.accounts",
>> # "mezzanine.mobile",
>> 'parsley',
>> 'django_comments',
>> )
>>
>> And i added some settings from mezzanine's start-project:
>>
>> #Weird-mezzanine-conf
>> # Store these package names here as they may change in the future since
>> # at the moment we are using custom forks of them.
>> PACKAGE_NAME_FILEBROWSER = "filebrowser_safe"
>> PACKAGE_NAME_GRAPPELLI = "grappelli_safe"
>> OPTIONAL_APPS = (
>> "debug_toolbar",
>> "django_extensions",
>> "compressor",
>> PACKAGE_NAME_FILEBROWSER,
>> PACKAGE_NAME_GRAPPELLI,
>> )
>> SITE_ID = 1
>> COMMENTS_DISQUS_API_SECRET_KEY = 'xxx'
>> COMMENTS_DISQUS_SHORTNAME = 'xxx'
>>
>>
>> try:
>> from mezzanine.utils.conf import set_dynamic_settings
>> except ImportError:
>> pass
>> else:
>> set_dynamic_settings(globals())
>>
>> I'm several hours stuck with this problem and would be glad if someone
>> could help me. Thanks
>>
> --
> 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] Re: Mezzanine 4.2.0 released

[Stephen McDonald]

I've also just pushed new Cartridge and Drum releases which each leverage
the latest Mezzanine and support Django 1.10

On Sun, Aug 14, 2016 at 9:54 AM, Stephen McDonald <st...@jupo.org> wrote:

> Hi all,
>
> I've just released Mezzanine 4.2.0 - it contains support for Django 1.10,
> as well as including a long list of bug-fixes which were yet to be
> released, since 4.1.0 came out 6 months ago.
>
> One other major new feature 4.2 brings is a new "Content Typed"
> abstraction. This is the result of refactoring out the parts of Mezzanine's
> Page model that provide the system for subclassing it, and having the admin
> interface allow you to choose from the different subclasses when creating
> new instances. This means you can build your own subclassable models that
> work just like Mezzanine's Page models do. We'll use this in the future to
> provide custom Product types in Cartridge. You can see the work that was
> done here: https://github.com/stephenmcd/mezzanine/pull/1612
>
> A huge thanks goes out to Ryne Everett, Alex Hill and Ed Rivas, who have
> been the primary providers of maintenance and support going into this
> release - it wouldn't be possible without their efforts, so thank you!
>
>
>
> --
> 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] Mezzanine 4.2.0 makes all tags as plain text in blog post.

[Stephen McDonald]

On Wed, Aug 31, 2016 at 5:22 PM, Alan Chen <alan.cheng...@gmail.com> wrote:

> This feature in Mezzanine 3.1.10 works fine. But 3.1.10 has no rich text
> editor toolbar


There's your problem. You'll likely find you've somehow misconfigured the
way static files are served - start there.


-- 
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] Multiple XSS issues reported

[Stephen McDonald]

Hi all,

We've had a couple of XSS issues privately reported. They've been verified,
with fixes set to be released next week. You can also mitigate these issues
without having to upgrade, using some small patches to your project.

To learn more, please ensure you're subscribed to the security mailing
list: https://groups.google.com/forum/#!forum/mezzanine-security

Please be aware that the security list is only intended for those with
public Mezzanine sites deployed, so on subscribing you'll need to provide
details of site.

-- 
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] Ryne Everett joins the core team

[Stephen McDonald]

Hi all,

We've asked Ryne Everett to join the core team and he's agreed to. Over the
last year or so, Ryne has consistently contributed a ton of work to
Mezzanine, as well as providing a huge amount of support to newcomers and
experts alike on the mailing list.

It would be a long list of items to note all the parts of Mezzanine he's
touched, but most notable would be the recent "Content Typed" refactor in
Mezzanine that allows you to build your own subclassable models, and also
custom product types for Cartridge (still a WIP) which depends on that work.

Thanks Ryne for all your work and welcome to the team.

-- 
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] Re: Multiple XSS issues reported

[Stephen McDonald]

I've just discovered that when you're not signed in with a Google account,
the subscription form for the mailing list doesn't provide the field for
you to enter your website URL as requested.

If you don't use a Google account, feel free to contact me directly with
the details and I'll subscribe you.

On Wed, Sep 7, 2016 at 10:01 AM, Stephen McDonald <st...@jupo.org> wrote:

> Hi all,
>
> We've had a couple of XSS issues privately reported. They've been
> verified, with fixes set to be released next week. You can also mitigate
> these issues without having to upgrade, using some small patches to your
> project.
>
> To learn more, please ensure you're subscribed to the security mailing
> list: https://groups.google.com/forum/#!forum/mezzanine-security
>
> Please be aware that the security list is only intended for those with
> public Mezzanine sites deployed, so on subscribing you'll need to provide
> details of site.
>
> --
> 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] Blogposts visible on site but not in admin panel.

[Stephen McDonald]

http://mezzanine.jupo.org/docs/configuration.html#ownable-models-all-editable

On Mon, Sep 12, 2016 at 2:28 PM, Michael Ketiku <mket...@gmail.com> wrote:

> So I have a problem with blog_posts not showing in the admin panel for
> users  of my application unless granted super user status.
> Right now only the creator of the blog post and users with  super user
> permissions are able to view blog_posts in the admin section. However, if
> the user signs out or returns to the site they are able to view the blog
> posts directly on the site just fine.
> Am I doing something wrong? Is there a configuration I need to enable?
>
> I am running a development server with:
> Django==1.8.6
> Mezzanine==4.2.0
> Python==2.7.11+
> SQLite==3.11.0
> Here are the permissions I have granted to one user for example.
>
>
> <https://lh3.googleusercontent.com/-am3EglUMbq8/V9Yu8elHrYI/eg0/cRckm9KSdIwa9WB2MVYyxRw5JaZT-59ugCLcB/s1600/Screenshot%2Bfrom%2B2016-09-12%2B00-20-49.png>
>
>
> <https://lh3.googleusercontent.com/-i2uU2PGHnYU/V9YvAEeqmcI/eg4/8iuEZ3HIVkM4CYAwk91Eh_DjwauXzI1tQCLcB/s1600/Screenshot%2Bfrom%2B2016-09-12%2B00-20-49.png>
>
>
> <https://lh3.googleusercontent.com/-1eyoJEcb_hQ/V9Yu5IhoyOI/egw/_Ylct0fmxGgk2dmaIEVXmFT7YBaxbBBSACLcB/s1600/Example_Group_Permissions.png>
>
>
>
> --
> 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] Related to Contact Form View Entries

[Stephen McDonald]

in 
> render_to_response
>   21. content = loader.render_to_string(template_name, context, 
> using=using)
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py" in 
> render_to_string
>   67. template = get_template(template_name, using=using)
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py" in 
> get_template
>   21. return engine.get_template(template_name)
>
> File 
> "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py" 
> in get_template
>   39. return Template(self.engine.get_template(template_name), 
> self)
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/engine.py" in 
> get_template
>   160. template, origin = self.find_template(template_name)
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/engine.py" in 
> find_template
>   134. name, template_dirs=dirs, skip=skip,
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/loaders/base.py" 
> in get_template
>   44. contents, origin, origin.template_name, self.engine,
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/base.py" in 
> __init__
>   191. self.nodelist = self.compile_nodelist()
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/base.py" in 
> compile_nodelist
>   233. return parser.parse()
>
> File "/usr/local/lib/python2.7/dist-packages/django/template/base.py" in parse
>   518. raise self.error(token, e)
>
> Exception Type: TemplateSyntaxError at /admin/forms/form/12/entries/
> Exception Value: Could not parse the remainder: ',' from 'on,'
>
>
>
> --
> 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] Mezzanine 4.2.2 released

[Stephen McDonald]

Hi all,

I just released Mezzanine 4.2.2 - just a quick bugfix release that resolves
an issue that can occur when re-ordering pages in the admin tree.

If you're using 4.2.1 you should upgrade, and you should be able to do so
seamlessly.


-- 
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] Elastic Beanstalk deployment - Mezz 4.1 - Pages don't work properly unless logged in as Super User

[Stephen McDonald]

Thanks Stuart

On Wed, Oct 5, 2016 at 11:15 AM, Stuart Leitch <torui...@gmail.com> wrote:

> Of course it works now.
>
> What I did was post to this group, give up for the night, and go to sleep.
> Nothing changed code or AWS configuration-wise since I made this post.
> Ghost in the machine fixing my problems?
>
> If I find out what the root of all this was, I'll update again.
>
> By the way, thanks for the fantastic work making Mezz, Stephen. It's
> pretty awesome.
>
> On Wednesday, October 5, 2016 at 7:30:03 AM UTC+8, Stephen McDonald wrote:
>>
>> I just clicked the links you gave and they appear to work. Please let the
>> list know what you did to fix it if you get the chance.
>>
>> On Wed, Oct 5, 2016 at 2:05 AM, Stuart Leitch <toru...@gmail.com> wrote:
>>
>>> Just today I deployed a Mezz 4.1 / Cartridge site to AWS Elastic
>>> Beanstalk, and there is some seriously strange behavior going on.
>>>
>>> When I navigate to, for example, http://mullershush-dev.ap-nort
>>> heast-1.elasticbeanstalk.com/ as I am not logged in or I am logged in
>>> as a regular user (created via admin panel), the menu bar doesn't show up
>>> at the top, and if I try to enter in the URL
>>> http://mullershush-dev.ap-northeast-1.elasticbeanstalk.com/
>>> articles/post/ or another one, I get a 404 error "No BlogPost matches
>>> the given query." I guess it suddenly can't find the slug, the existence of
>>> which I verified in the admin panel of course.
>>>
>>> Then I log in as the Super User and everything behaves as it should. It
>>> finds the slug, and loads the exact same page that can't be found as an
>>> anonymous or regular user.
>>>
>>> Naturally, on my local development machine, this behavior doesn't occur.
>>>
>>> I'm pretty new to AWS, and I don't even have the faintest idea of what
>>> could be causing this problem. The only suspicion I have is that it may be
>>> related to my IAM user configuration, but I've given All Access permissions
>>> to EB, RDS, etc... so I really just am stumped.
>>>
>>> Is there anything I could be missing?
>>>
>>> --
>>> 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
>>
> --
> 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] Elastic Beanstalk deployment - Mezz 4.1 - Pages don't work properly unless logged in as Super User

[Stephen McDonald]

I just clicked the links you gave and they appear to work. Please let the
list know what you did to fix it if you get the chance.

On Wed, Oct 5, 2016 at 2:05 AM, Stuart Leitch <torui...@gmail.com> wrote:

> Just today I deployed a Mezz 4.1 / Cartridge site to AWS Elastic
> Beanstalk, and there is some seriously strange behavior going on.
>
> When I navigate to, for example, http://mullershush-dev.ap-
> northeast-1.elasticbeanstalk.com/ as I am not logged in or I am logged in
> as a regular user (created via admin panel), the menu bar doesn't show up
> at the top, and if I try to enter in the URL http://mullershush-dev.ap-
> northeast-1.elasticbeanstalk.com/articles/post/ or another one, I get a
> 404 error "No BlogPost matches the given query." I guess it suddenly can't
> find the slug, the existence of which I verified in the admin panel of
> course.
>
> Then I log in as the Super User and everything behaves as it should. It
> finds the slug, and loads the exact same page that can't be found as an
> anonymous or regular user.
>
> Naturally, on my local development machine, this behavior doesn't occur.
>
> I'm pretty new to AWS, and I don't even have the faintest idea of what
> could be causing this problem. The only suspicion I have is that it may be
> related to my IAM user configuration, but I've given All Access permissions
> to EB, RDS, etc... so I really just am stumped.
>
> Is there anything I could be missing?
>
> --
> 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] Live Demo Code

[Stephen McDonald]

FYI the source is available here:
https://github.com/stephenmcd/mezzanine.jupo.org

As Ed said it's mostly just default Mezzanine/Cartridge - there are a few
custom bits in the project for the homepage, sites gallery and the demo
user and content.

On Sat, Oct 8, 2016 at 12:42 PM, Akhlaq Rao <akhlaq@gmail.com> wrote:

> exactly what I was looking for.
>
> Thanks!
>
> On Fri, Oct 7, 2016 at 5:36 PM, Eduardo Rivas <jerivasmel...@gmail.com>
> wrote:
>
>> I think it's just a Mezzanine + Cartridge project with the demo content
>> installed. You can get the same with:
>>
>> pip install mezzanine cartridge
>> mezzanine-project -a cartridge project_name
>> cd project_name
>> python manage.py createdb --noinput
>> python manage.py runserver
>>
>>
>> --
>> 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.

[mezzanine-users] Re: Multiple XSS issues reported

[Stephen McDonald]

Hi all,

I've just pushed out Mezzanine 4.2.1 which resolves the XSS issues
mentioned previously. Note that a filebrowser_safe upgrade is also required
for the latter of the two issues described below - that should occur
automatically though as the latest Mezzanine version specifies the new
version as a requirements in its setup.py script.

The release also contains a good handful of minor bugfixes as noted in the
changelog: http://mezzanine.jupo.org/docs/colophon.html#version-4-2-1-
sep-19-2016

Thanks to Tim Coen of curesec.com for privately reporting the issues, and
giving us time to communicate and mitigate them. If you have a production
Mezzanine site, once again I'd like to remind you to subscribe to the
private security mailing list (https://groups.google.com/
forum/#!forum/mezzanine-security) where you can be notified of issues like
these and how to mitigate them, ahead of them being publicly disclosed.

Here are the issues described in detail, as well as instructions for
patching if you're unable to upgrade:

The first issue is related to Mezzanine's threaded commenting - if you
don't use it, you're not affected, otherwise it should be treated as
critical, since it can be publicly exploited. For this to occur, an
administrator would need to access the list of comments inside the admin
interface, where XSS could be triggered. The problem is with this method of
the comment model solely for use in the admin, which is used to show a nice
avatar next to the commenter's username in the comment list view:
https://github.com/stephenmcd/mezzanine/blob/bede76b6f
96227350cb0bf0058f555daeb4cc2ad/mezzanine/generic/models.py#L67-L73 -
unfortunately the username isn't escaped, and the method's value is marked
as safe for no template escaping, since we use HTML tags in it. A malicious
commenter could therefor include HTML/JavaScript code inside their
username, and have it execute when viewing the list of comments in the
admin interface. The fix for this will be to simply escape the vars in that
method: https://github.com/stephenmcd/mezzanine/commit/
349edff5a22089bfed0baff0f7060d784b1046d2

To patch without upgrading, just remove the list field, using these lines
of code in your project's urls.py module:

from mezzanine.generic.admin import ThreadedCommentAdmin
ThreadedCommentAdmin.list_display = ThreadedCommentAdmin.list_display[1:]

The second issue can only be exploited by a malicious admin user, so it's
of much lower concern. The media library (filebrowser) in Mezzanine allows
for arbitrary file uploads of HTML or SVG files, which can both contain
JavaScript when accessed via a web browser. These are not subject to the
same "richtext" filtering that's applied to the WYSIWIG editor. To fix
this, we now apply the same filtering that's applied to the WYSIWYG editor,
to uploaded HTML or SVG files in the media library - that way if you have
trusted technical admin users, you can disable richtext filtering, and keep
the current behaviour: https://github.com/stephenmcd/filebrowser-safe/
commit/c3bb7ea8d7af67e4fd1279b3cf486f6148a29cb0

To patch without upgrading, simply define the setting in your project's
settings.py module that controls which file extensions can be uploaded:

FILEBROWSER_EXTENSIONS = {
'Image': ['.jpg', '.jpeg', '.gif', '.png', '.tif', '.tiff'],
'Code': ['.py', '.js', '.css']
}

We only need to define the "groups" we want to modify, namely Image/Code -
the values above are the defaults with HTML and SVG removed.

On Wed, Sep 7, 2016 at 10:01 AM, Stephen McDonald <st...@jupo.org> wrote:

> Hi all,
>
> We've had a couple of XSS issues privately reported. They've been
> verified, with fixes set to be released next week. You can also mitigate
> these issues without having to upgrade, using some small patches to your
> project.
>
> To learn more, please ensure you're subscribed to the security mailing
> list: https://groups.google.com/forum/#!forum/mezzanine-security
>
> Please be aware that the security list is only intended for those with
> public Mezzanine sites deployed, so on subscribing you'll need to provide
> details of site.
>
> --
> 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] Redirect administration: filter by site

[Stephen McDonald]

It's something that's been overlooked - Django provides its own admin class
for the redirects, and doesn't filter/hide by site, since that's a
Mezzanine specific behaviour.

I've pushed a change for review that fixes it here:
https://github.com/stephenmcd/mezzanine/pull/1685

Thanks for raising this.

On Tue, Oct 4, 2016 at 9:04 AM, James Pic <james...@gmail.com> wrote:

> Hi all !
>
> I'm just trying out Mezzanine, it's really cool ! It's my first time with
> mezzanine and I have a "bug or feature" type of question.
>
> In the Pages administration, staff may only work on pages of the current
> site.
>
> However, in the Redirects administration, staff may see redirects of other
> sites it doesn't have the permission for, also it may change or add
> redirects for sites it doesn't have permission for. It seems like a staff
> user could create a redirect with a wrong site it doesn't have permission
> for by mistake.
>
> I didn't find any documentation nor discussion about this, but then again
> I have like 10 minutes of experience in mezzanine so I'm really a newb :)
>
> Thanks for your time !
>
> Best
>
> James
>
> --
> 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] Re: Cartridge checkout page blank

[Stephen McDonald]

Works fine for me without changing anything.

What browser are you using?

On Mon, Nov 7, 2016 at 11:39 AM, Thomas Yager-Madden <yagermad...@gmail.com>
wrote:

> Following up on my own post, this seems to be an issue with
> `cartridge.css` rather than a missing tag as I imagined. When I comment
> that particular stylesheet out of `base.html` the checkout forms load fine.
> I'm not sure I want to exclude that whole stylesheet; I'd rather find
> whatever might be in there that's hiding everything. At least now I have a
> better idea where to look. I'll report back again if I find anything—in the
> meantime if anybody more familiar with this project has a more educated
> guess what might be going on, I'd still love to hear about it. Thanks!
>
> --
> 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] Re: Cartridge checkout page blank

[Stephen McDonald]

They're intended to hide any non-primary navigation so as to not distract
the user from completing their checkout, but the intention is for the
developer to modify this completely - they're only vanilla-looking defaults
to get you started with.

-- 
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] Norwegian translation of Mezzanine

[Stephen McDonald]

You can just submit translations as PRs on Github

Thanks

On Fri, Oct 21, 2016 at 7:56 PM, <si...@e5r.no> wrote:

> Hello, I'd like to help improve the Norwegian translation of Mezzanine as
> I'm using Mezzanine for several Norwegian projects. I sent Sebastián
> Ramírez Magrí a request to join the translation team at Transifex about a
> month ago, and a personal message two weeks after that, but I still haven't
> heard anything. Is there anything else I can do to be able to help out with
> the translation? -- Simen
>
> --
> 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] A few quick questions...

[Stephen McDonald]

I think Google Analytics already covers what you're trying to do.

That said, you could put together some Django middleware to do what you
need, nothing Mezzanine specific about it.

On Tue, Dec 13, 2016 at 4:51 AM, Paul <paul...@gmail.com> wrote:

> I'm new to a lot of this and was curious on some pointers on things to
> research. If someone links me to FAQ or help I'm open to that (I've done a
> bit of reading, too).
>
> 1. I want to build a plugin that tracks the first URL someone hits on my
> site, store it in a cookie, and then when someone submits a form, I want to
> include that in the form so I know what page someone first came to on my
> site (I may also want to include referrer in here, too). I've used WTForms
> with Flask before. My question: how do I integrate this with Mezzanine? How
> do I hook into the first page load of a user? In Django terms, I believe I
> want to create "middleware" – but can someone clarify this?
>
> 2. Is there something that logs each page request in a database? eg. I had
> something like this on Drupal: https://www.drupal.org/project/visitors -
> is there something for Mezzanine? Or, do you guys recommend just looking at
> server logs? I'm open to alternative solutions, too.
>
> 3. How much is Mezzanine specific and how much is Django specific? I'm new
> to both, and I'm wondering if I should be searching for solutions to
> Mezzanine and also to Django (I think Django would yield more results, but
> I'm not sure if they're relevant?)
>
> Thank you for your time!
>
> --
> 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] Check if a local path exists?

[Stephen McDonald]

Try querying the page model itself.

On Sun, Dec 18, 2016 at 8:04 AM, Paul <paul...@gmail.com> wrote:

> I'm trying to validate if a page with a url exists. I do something like
> this:
>
> (Pdb) resolve('/does-not-exist/')
>
> I get...
>
> ResolverMatch(func=mezzanine.pages.views.page, args=(), kwargs={'slug':
> 'does-not-exist'}, url_name=page, app_names=[], namespaces=[])
>
> This page doesn't exist. When I go here in my browser, I see something
> like this:
>
> Page not found (404)
> Request Method: GET
> Request URL: http://localhost:8000/does-not-exist/
> Raised by: mezzanine.pages.views.page
>
> You're seeing this error because you have DEBUG = True in your Django
> settings file. Change that to False, and Django will display a standard
> 404 page.
>
> I've tried to research ways to do this within Mezzanine. If I understand
> correctly, the catch-all is causing an issue here. Any two cents? Thank you!
>
> --
> 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] Re: python 3 support

[Stephen McDonald]

On Thu, Dec 29, 2016 at 11:13 AM, Mario R. Osorio <nimbiot...@gmail.com>
wrote:

> Akshually...
>
> I just started working on a Mezzanine project and wanted to use one of
> those many years old free templates. It didn't work from scratch, but it
> didn't take more than 5 or10 minutes to fix the "problems".
>
> I can only recall one problem, and I don't think there was another one.
>
> Here's what I did; remove all imports of the "future" library from all
> template files (the {% load %} tag); and voila!
>

That's all well and good, but to avoid confusing anyone, please note this
has nothing to do with Python 3 support.


>
> Oh, and trust me, I'm NOT what you'd call an "expert" ... I just LOVE
> Mezzanine's simplicity, inherited in part from Django's simplicity, also
> inherited in part from Python's simplicity.
>
>
>
> On Wednesday, December 28, 2016 at 2:28:06 PM UTC-5, Stephen McDonald
> wrote:
>>
>> FWIW you're replying to a 3 year old thread discussing Python 3 support
>> before it was even added. Since then it's been added and has been fully
>> working and supported for several years now.
>>
>> Of course if you've come across a bug, then by all means report it - but
>> you've made no mention of any details here, so nothing can be done to help
>> you.
>>
>> On Thu, Dec 29, 2016 at 12:49 AM, Chekad Sarami <csa...@gmail.com> wrote:
>>
>>> I was able create and run a mezzanine project with python 3 on my ubuntu
>>> 14. But, then for theme customizations and other things NO hope! I guess I
>>> am moving back to Python 2. I guess the should be creamy mentioned in
>>> Mezzanine website. This really through the first-time users OFF!
>>>
>>> On Wednesday, August 28, 2013 at 3:50:16 PM UTC-4, garagefan wrote:
>>>>
>>>> Pardon me if this has been mentioned elsewhere, as I'm sure it has
>>>> been... but
>>>>
>>>> With the growing library of python 3 supported plugins; I was wondering
>>>> when we could expect mezzanine to support python 3 as well?
>>>>
>>>>
>>>> --
>>> 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
>>
> --
> 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] I18N and static files issue (MEDIA_URL)

[Stephen McDonald]

On Sat, Dec 24, 2016 at 3:02 AM, <dunrix...@gmail.com> wrote:

> Hi,
>
> I'm looking for an advice how Mezzanine handles urls for images, when
> *USE_I18N* is *True* ?
>
> In debug mode, all uploaded images have correct urls, like
> */static/media/uploads/rioba.png*, but in production (when *DEBUG is set
> to False*) and application is run with ./manage.py runserver --insecure,
> I'm getting following 404 errors:
>
> "GET /static/media/uploads/rioba.png HTTP/1.1" 301 0
> "GET /nl/static/media/uploads/rioba.png/ HTTP/1.1" 404 5954
>
> In other words, Mezzanine redirects request to MEDIA_URL link to url with
> language code prefix.
>

Sounds like there's a bug there when serving static files through Django in
production, but it's no surprise that's gone unnoticed since you should
never be doing this - the public facing web server should be catching all
the static URLs before the Django app is ever hit, for example see the
bundled nginx conf here:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/deploy/nginx.conf.template#L37-L42



>
> I do not want this behavior, all images are common to all language
> variants. Is there some way how it can be disabled ?
>
> Thanks.
>
> --
> 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] admin WYSIWIG missing with Uncaught TypeError: $elements.tinymce is not a function

[Stephen McDonald]

It was fixed last week:

https://github.com/stephenmcd/mezzanine/commit/556091e3cc9d3220cc52dbb9232c72758e8834ae

Try that

On Mon, Jan 16, 2017 at 2:12 PM, AdamS <add.simm.8...@gmail.com> wrote:

>
> Thank you – any idea as to fixing the JavaScript error?
>
> --
> 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] error deploying project with modeltranslation

[Stephen McDonald]

Unfortunately we don't have anyone contributing to Mezzanine right now who
is familiar with the modeltranslation integration.

Given that, the best possible outcome moving forwards will be for someone
who has a strong need for it to step up and help out.

Thanks in advance to whoever can contribute here.

On Wed, Mar 15, 2017 at 6:05 AM, tazogil <tazo...@gmail.com> wrote:

> Hello,
>
> I'm deploying a project with mezzanine 4.2.3, django 10 and django
> modeltranlation.
> The following error occur during fab create :
> AttributeError: 'SearchableQuerySet' object has no attribute 'rewrite'.
>
> Deploying mezzanine 4.2.3 django 1.9 :
> CommandError: Unknown command:  commands.sync_translation_fields.Command object
>
> Deploying  with mezzanine 4.2.2 and django 1.9 was ok last month but now
> (the reason why I upgrade to 4.2.3) :
> AttributeError: 'module' object has no attribute 'BleachSanitizer'
>
> So I can't deploy anymore ! Thank you for your help.
>
> --
> 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] Mezzanine 4.2.3 released

[Stephen McDonald]

Hi all,

I've just pushed Mezzanine 4.2.3 to PyPI. It contains a long list of very
minor bug-fixes, as well as a fix to the show-stopping issues introduced
this week with the release of a backward incompatible change in some
dependencies.

Thanks to everyone who has contributed reports and fixes.


-- 
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] Recent bleach 2.0 release breaks Mezzanine

[Stephen McDonald]

I've just pushed 4.2.3 which resolves this. Thanks for the reports.

On Wed, Mar 8, 2017 at 8:30 PM, John Barham <jbar...@gmail.com> wrote:

> Hi all,
>
> I just installed current version of Mezzanine 4.2.2 but when I run "python
> manage.py shell" after creating a project I get the following error:
>
> File "/home/jbarham/.virtualenvs/foo/lib/python3.5/site-
> packages/mezzanine/utils/html.py", line 36, in 
> if "tel" not in sanitizer.BleachSanitizer.allowed_protocols:
> AttributeError: module 'bleach.sanitizer' has no attribute
> 'BleachSanitizer'
>
> The installed version of Bleach is 2.0 which was released literally 14
> hours ago (https://github.com/mozilla/bleach/releases). If I manually
> revert to the previous release 1.5, the error goes away, so it's evidently
> due a backwards-incompatible change in the bleach API.
>
> ISTM this is a fairly serious issue since it will break any new installs
> of Mezzanine. A quick workaround may be to change the Mezzanine setup.py
> requirement for bleach from "bleach >= 1.4" to "bleach >= 1.4, < 2.0".
>
> Thoughts?
>
> Cheers, John
>
> --
> 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] Re: Mezzanine 4.2.3 released

[Stephen McDonald]

I've pushed those to PyPI now too. Thanks for the reminder.

On Fri, Mar 10, 2017 at 10:21 AM, Eduardo Rivas <jerivasmel...@gmail.com>
wrote:

> Hey Steve, thanks for the release! Are you also going to release Grappelli
> and Filebrowser? They contain fixes for the inline issues described in
> https://github.com/stephenmcd/grappelli-safe/pull/79#
> issuecomment-263872748
>
> --
> 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] Access field of Page subclass in template

[Stephen McDonald]

Docs have you covered

http://mezzanine.jupo.org/docs/content-architecture.html#displaying-custom-content-types

On Mar 8, 2017 1:40 PM, "Jochen Breuer"  wrote:

>
> Hello everyone,
>
> I've got a Page subclass with some additional fields. Everything works
> perfectly. But now I need to implement a side-bar navigation which should
> display a field from the Page subclass. The relevant template code looks
> like roughly this:
>
> {% for page in page_branch %}
> {{ page.city }},
> {% endfor %}
>
> city would be the field created in the Page subclass. Is there any way to
> achieve this without reimplementing the template tags needed here?
>
> The Page subclass looks like this:
>
> class MyOwnPage(Page):
> city = models.CharField(max_length=255, verbose_name=_(u"City"))
> content = RichTextField(_("Content"))
> …
> search_fields = ("content",)
>
>
> Thanks!
>
> Jochen
>
> --
> 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] Mezzanine Deployment Instructions lacking and unusable

[Stephen McDonald]

A Mezzanine project is just a regular Django project, so perhaps you'd
better off broadening your search to deploying Django in general.

On Mon, Mar 6, 2017 at 10:31 AM, Henro Ritchie <henro.ritc...@gmail.com>
wrote:

> Hi
>
> I have tried deploying Mezzanine about 10 times today using various
> guides, including the official one from Mezzanine. None worked, with
> various different errors. The most persistent error is the fab all command
> continuously asking for the password without and progress and fabric not
> providing any feedback on why this would happen. The question title refers
> to the official guide only glancing over various aspects without proper
> instruction. Without proper help and instruction Mezzanine will never be
> adopted by main stream users.
>
> Any help would greatly be appreciated.
>
> --
> 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] "Cannot use None as a query value"

[Stephen McDonald]

0.1-py2.7.egg/mezzanine/core/models.py" in delete
>   446. after = concrete_model.objects.filter(**lookup)
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/manager.py"
> in manager_method
>   127. return getattr(self.get_queryset(), name)(*args,
> **kwargs)
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/query.py"
> in filter
>   679. return self._filter_or_exclude(False, *args, **kwargs)
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/query.py"
> in _filter_or_exclude
>   697. clone.query.add_q(Q(*args, **kwargs))
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/sql/query.py"
> in add_q
>   1309. clause, require_inner = self._add_q(where_part,
> self.used_aliases)
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/sql/query.py"
> in _add_q
>   1337. allow_joins=allow_joins, split_subq=split_subq,
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/sql/query.py"
> in build_filter
>   1155. value, lookups, used_joins = self.prepare_lookup_value(value,
> lookups, can_reuse, allow_joins)
> File 
> "/Users/majora/venv/lib/python2.7/site-packages/django/db/models/sql/query.py"
> in prepare_lookup_value
>   995. raise ValueError("Cannot use None as a query value")
>
> Exception Type: ValueError at /admin/vital_theme/tuitionpage/318/
> Exception Value: Cannot use None as a query value
>
> Any advice would be great appreciated!
>
> Cheers,
>
> Rich
>
> --
> 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] Password reset URL scheme in email templates is hard coded as HTTP

[Stephen McDonald]

That's merged now, thanks Ryne.

We'll release that fix along with a new version of Mezzanine that supports
Django 1.11 once that's ready. You can track progress here:

https://github.com/stephenmcd/mezzanine/pull/1750

Anyone who can help in testing that work, and contributing any other
changes required would be greatly appreciated, thanks!

On Sun, Apr 16, 2017 at 12:43 PM, Ryne Everett <ryneever...@gmail.com>
wrote:

> I went ahead and submitted the patch:
> <https://github.com/stephenmcd/mezzanine/pull/1751>.
>
> --
> 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] Cartridge customisation

[Stephen McDonald]

On Wed, Aug 16, 2017 at 1:36 AM, Simon Bradley <captain.bal...@gmail.com>
wrote:

> Hi
>
> I've read a lot of posts about customising cartridge but they tend to be
> issue specific.
>
> I've only just started using mezzanine and cartridge and while i've found
> mezzanine very easy to bend to my will, i'm struggling with how to
> customise cartridge.
>
> I'm trying to build a location booking system.
>
> It's really easy to get the default shop up and running which is
> fantastic. I've done that and added various products with the admin
> interface and that all works great.
>
> Now i want to customise the product view to remove the quantity field and
> to add from and to dates. Just basic booking stuff like you'd get on
> booking.com. The simple way appears to be to just edit the model but then
> what happens if i want to update my installed version of cartridge?
>

Given that the rate of change in Cartridge is *very* low, this shouldn't be
a problem. Depend on your private fork of Cartridge, and updating should be
as simple as merging upstream changes when they do infrequently occur. For
the small price to pay of needing some way to keep on top of those changes,
and the manual task of having to resolve conflicts should they occur, you
gain unlimited ability to customize.



> That's a real concern if there's a security issue. And of course i'd like
> to avoid building in my own security problems!
>
> I've read through the docs on integration and sub classing the order form
> and then removing the fields i dont want (Which is most of them). I dont
> need shipping and what have you either because there's no physical product.
>
> However, it seems on the face of it to be much simpler to just edit the
> models.
>
> So, i was wondering if there's a way to make these fairly simple
> modifications without just copying the cartridge folder into my project and
> hacking it to pieces and then making the necessary migrations! Or is that
> common?
>
> Sorry this sounds so clueless, I'm really just looking for some sound
> advice.
>
> Cheers.
>
>
>
>
> --
> 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] Docs typo

[Stephen McDonald]

Thanks for pointing this out, fixed here: https://github.com/
stephenmcd/mezzanine/commit/fd6168903d53f4e145741a980ded26dbc3e59dfd



On Mon, Jun 26, 2017 at 4:12 PM, Mike Dewhirst <mi...@dewhirst.com.au>
wrote:

> About a third of the way down the page at ...
>
> http://mezzanine.jupo.org/docs/overview.html#installation
>
> Users on Debian or Ubuntu will require some system packages to support the
> imaging library:
>
> $ apt-get install libjpeg8 libjpeg8-dev
> $ apt-get build-dep python-imaging
>
> Ubuntu 16.04 returns an error ...
>
> E: Unable to locate package build-dep
>
> Maybe you mean build-essential?
>
> Mike
>
> --
> 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] updating the word "Mezzanine" to our own name/logo in the upper left of the admin view

[Stephen McDonald]

I replied to the other discussion you started on Github. I would suggest
having only one running conversation.

-- 
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] First time installation - cannot log in

[Stephen McDonald]

ib\site-packages\django\utils\decorators.py" in
> bound_func
>   63. return func.__get__(self, type(self))(*args2,
> **kwargs2)
>
>
> File "c:\projects\\lib\site-packages\django\utils\decorators.py" in
> _wrapper
>   67. return bound_func(*args, **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\views\decorators\cache.py"
> in _wrapped_view_func
>   57. response = view_func(request, *args, **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\utils\decorators.py" in
> bound_func
>   63. return func.__get__(self, type(self))(*args2,
> **kwargs2)
>
>
> File "c:\projects\\lib\site-packages\django\contrib\auth\views.py" in
> dispatch
>   90. return super(LoginView, self).dispatch(request, *args,
> **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\views\generic\base.py" in
> dispatch
>   88. return handler(request, *args, **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\views\generic\edit.py" in
> post
>   182. if form.is_valid():
>
>
> File "c:\projects\\lib\site-packages\django\forms\forms.py" in
> is_valid
>   183. return self.is_bound and not self.errors
>
>
> File "c:\projects\\lib\site-packages\django\forms\forms.py" in errors
>   175. self.full_clean()
>
>
> File "c:\projects\\lib\site-packages\django\forms\forms.py" in
> full_clean
>   385. self._clean_form()
>
>
> File "c:\projects\\lib\site-packages\django\forms\forms.py" in
> _clean_form
>   412. cleaned_data = self.clean()
>
>
> File "c:\projects\\lib\site-packages\django\contrib\auth\forms.py" in
> clean
>   187. self.user_cache = authenticate(self.request,
> username=username, password=password)
>
>
> File "c:\projects\\lib\site-packages\django\contrib\auth\__init__.py"
> in authenticate
>   70. user = _authenticate_with_backend(backend,
> backend_path, request, credentials)
>
>
> File "c:\projects\\lib\site-packages\django\contrib\auth\__init__.py"
> in _authenticate_with_backend
>   115. return backend.authenticate(*args, **credentials)
>
>
> File "c:\projects\\lib\site-packages\mezzanine\core\auth_backends.py"
> in authenticate
>   34. user = User.objects.get(username_or_email,
> **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\db\models\manager.py" in
> manager_method
>   85. return getattr(self.get_queryset(), name)(*args,
> **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\db\models\query.py" in get
>   371. clone = self.filter(*args, **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\db\models\query.py" in
> filter
>   784. return self._filter_or_exclude(False, *args, **kwargs)
>
>
> File "c:\projects\\lib\site-packages\django\db\models\query.py" in
> _filter_or_exclude
>   802. clone.query.add_q(Q(*args, **kwargs))
>
>
> File "c:\projects\\lib\site-packages\django\db\models\sql\query.py"
> in add_q
>   1261. clause, _ = self._add_q(q_object, self.used_aliases)
>
>
> File "c:\projects\\lib\site-packages\django\db\models\sql\query.py"
> in _add_q
>   1287. allow_joins=allow_joins, split_subq=split_subq,
>
>
> File "c:\projects\\lib\site-packages\django\db\models\sql\query.py"
> in build_filter
>   1165. lookups, parts, reffed_expression =
> self.solve_lookup_type(arg)
>
>
> File "c:\projects\\lib\site-packages\django\db\models\sql\query.py"
> in solve_lookup_type
>   1045. _, field, _, lookup_parts = 
> self.names_to_path(lookup_splitted,
> self.get_meta())
>
>
> File "c:\projects\\lib\site-packages\django\db\models\sql\query.py"
> in names_to_path
>   1363.  "Choices are: %s" % (name, ",
> ".join(available)))
>
>
> Exception Type: FieldError at /admin/login/
> Exception Value: Cannot resolve keyword 'request' into field. Choices are:
> blogposts, comment_comments, comment_flags, date_joined, email, first_name,
> groups, id, is_active, is_staff, is_superuser, last_login, last_name,
> logentry, password, ratings, sitepermissions, user_permissions, username
>
> --
> 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] Re: modeltranslation

[Stephen McDonald]

This is working now as per
https://github.com/stephenmcd/mezzanine/issues/1679#issuecomment-307730648

Please don't post the same issue in multiple places.

On Mon, Jun 12, 2017 at 7:01 PM, i bigoss <jaroslaw.b...@gmail.com> wrote:

> Tried everything but adding form page does not work:
>
> I have applied above patch.
> However while adding form page in admin i get:
>
> __
> self.fields["label"].widget = admin.widgets.AdminTextInputWidget()
> KeyError: u'label'
> [12/Jun/2017 10:45:05] "GET /en/admin/forms/form/add/ HTTP/1.1" 500 149820
>
> Can anyone help please?
>
> On Friday, June 2, 2017 at 3:40:39 PM UTC+2, Melvyn Sopacua wrote:
>>
>> On Thursday 01 June 2017 05:31:31 i bigoss wrote:
>>
>> > ok got it if anyone else in near future gets same problem some
>>
>> > solution is described here:
>>
>> > https://github.com/stephenmcd/mezzanine/pull/176
>>
>>
>>
>> For prosperity, the correct link
>> <https://github.com/stephenmcd/mezzanine/pull/1764>.
>>
>> --
>>
>> Melvyn Sopacua
>>
> --
> 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] Re: Wordpress import and redirects

[Stephen McDonald]

Not sure about the second issue, but if you can create a PR with your fix
for the first issue, that would be great thanks.

On Sun, May 28, 2017 at 8:05 PM, Karim <lemieli...@gmail.com> wrote:

> Hello, I found some time to work on this and I changed the
> import_wordpress.py (line 75)
>
> if entry.wp_post_type == "post":
> ​​
> post = self.add_post(title=entry.title, content=content,
> ​​
> pub_date=pub_date, tags=terms["tag"],
> ​​
> categories=terms["category"],
> *​​old_url=entry['link'])*
>
>
> ​Instead of* old_url=entry.id <http://entry.id>* I used
> *old_url=entry['link']*
>
> The result: I got ALL the redirects.​
>
> Another issue (or maybe not) is the redirects with accents. I have some
> redirects like:
>
> *old_url = /2010/05/03/la-stagione-della-luce-e-arrivata-finalmente/*
> *new_url = /blog/la-stagione-della-luce-%C3%A8-arrivata-finalmente/*
>
>
> This works because the new url is handled by mezzanine. The new_url slug
> is generated from the title (?).
>
> In this case:
>
> *old_url =
>  
> /2010/03/09/e%e2%80%99-possibile-dare-una-spintarella-a-questo-inverno-e-mandarlo-gentilmente-in-vacanza-nell%e2%80%99emisfero-australe/*
> *new_url
> = 
> /blog/e-possibile-dare-una-spintarella-a-questo-inverno-e-mandarlo-gentilmente-in-vacanza-nellemisfero-australe/*
>
>
> But actually in wordpress the original old_url is:
> */2010/03/09/e’-possibile-dare-una-spintarella-a-questo-inverno-e-mandarlo-gentilmente-in-vacanza-nell’emisfero-australe/*
>
> ​If in my local I use the old_url as in the Redirect object, the url is
> changed to: *http://127.0.0.1:8000/2010/03/09/e
> <http://127.0.0.1:8000/2010/03/09/e>’-possibile-dare-una-spintarella-a-questo-inverno-e-mandarlo-gentilmente-in-vacanza-nell’emisfero-australe/*
> (as in wordpress), but I get a 404.​
>
> ​I have the feeling that this is a bug.​
>
> ​Any thoughts?​
>
>
>
> --
> Karim N. Gorjux
>
> --
> 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] displayable_link.js is not generated - development server

[Stephen McDonald]

Generally speaking, all of the content that would appear in
displayable_links.js
is tied to a particular "site" record in the database, and will only be
displayed if the hostname you're accessing the site with in your browser
matches the hostname for the "site" record in the database.

For that to work, you'll need to ensure nginx and uwsgi are correctly
sending the HTTP_HOST header to the Django app, and that the correct host
name is configured in the "sites" section of the admin.

I've never used uwsgi, but you can see where this is configured in the
default nginx config supplied with Mezzanine:

https://github.com/stephenmcd/mezzanine/blob/7bee9d8ca29321ef018a0ea4d5f26c06bb77037f/mezzanine/project_template/deploy/nginx.conf.template#L30


On Tue, May 30, 2017 at 9:54 PM, Lucas Corso <lucascorso1...@gmail.com>
wrote:

> There is an important detail when I raise the project in production with $
> python manage.py runserver if it works and it generates the
> displayable_links.js but when I lift it with nginx and uwsgi then it fails,
> and it gives 404 in the url.
>
> Which makes me think that it may not be a source code error if not some
> erroneous or missing configuration.
>
> --
> 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] New release date ?

[Stephen McDonald]

On Wed, Oct 4, 2017 at 8:39 AM, <lud...@gmail.com> wrote:

> Hi there,
>
> is there a rough estimate for when the next version will be released with
> Django 1.11 support ?
>

There is no rough estimate


> I would love to use Mezzanine on my project but I'm using Django 1.11 and
> I wouldn't know how to use the git version
>

I typed "git pip heroku" into Google and the first result was Heroku's docs
explaining how to do it:

https://devcenter.heroku.com/articles/python-pip#git-backed-distributions


> (which I know already supports Dj 1.11) on Heroku.. (suggestions welcome!)
>
> Many thanks,
> Ludo
>
> --
> 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] example.com!

[Stephen McDonald]

It uses the domain defined in the record for the current site which you can
view and update at: http://127.0.0.1:8000/en/admin/sites/site/

It gets set to 127.0.0.1:8000 for the development site if you follow
Mezzanine's installation instructions to the tee, but if you deviate from
that which presumably you've done, Django defaults it to example.com

On Fri, Aug 25, 2017 at 8:55 AM, Simon Bradley <captain.bal...@gmail.com>
wrote:

> Hi
>
> The View on Site button has started doing something quite unusual.
>
> Now when i press it, it replaces localhost with example.com!
>
> I'm starting to doubt myself here. Did it always do that? I don't think it
> did.
>
> So when i hover over the button i can see the link at the bottom.
> Something like: http://127.0.0.1:8000/en/admin/r/16/9/
>
> An then when i press the button it takes me to example.com/ and
> everything after that slash is as it should be!
>
> Any ideas? Mind = boggled.
>
> Cheers.
>
> --
> 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] Spaces and all-caps categories

[Stephen McDonald]

https://stackoverflow.com/questions/427102/what-is-a-slug-in-django

On Wed, Nov 15, 2017 at 4:04 PM, Tom Tanner <dontsendemailher...@gmail.com>
wrote:

> Hey all,
>
> I made a blog post, I added a category named "HUD."
>
> When I go to `mysite.com/blog/HUD` <http://mysite.com/blog/HUD>, I get a
> 404 error. But if I go to  `mysite.com/blog/hud`
> <http://mysite.com/blog/hud>, it works fine. Why is this?
>
> I also added a category "some category," but when I go to `
> mysite.com/blog/some%20category/`
> <http://mysite.com/blog/some%20category/>, it gives me a 404 too.
>
> Does Mezzanine have its own way to correct these, or must I do so through
> `reverse()` or another Django method?
>
> --
> 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] How do I add default values to SEARCH_MODEL_CHOICES?

[Stephen McDonald]

My man, please check the docs:

http://mezzanine.jupo.org/docs/configuration.html#registering-settings

On Mon, Nov 13, 2017 at 10:12 AM, Tom Tanner <dontsendemailher...@gmail.com>
wrote:

> In my app's `defaults.py`, I have this code:
>
> register_setting(
> name="SEARCH_MODEL_CHOICES",
> description=_("Sequence of models that will be provided by default as
> "
> "choices in the search form. Each model should be in the format "
> "``app_label.model_name``. Only models that subclass "
> "``mezzanine.core.models.Displayable`` should be used."),
> editable=False,
> default=("theme.ProjectPage", ),
> )
>
>
>
> My goal here is to add `"theme.ProjectPage"` to the models the search
> engine queries. But in effect, this replaces Mezzanine's built-in
> SEARCH_MODEL_CHOICES. How do I change this code so that
> `"theme.ProjectPage"` gets added to SEARCH_MODEL_CHOICES without replacing
> its defaults: `"pages.Page", "blog.BlogPost"`?
>
> --
> 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] Re: Mezzanine 3.1.10: Can't delete the media files in the admin page

[Stephen McDonald]

Could you create a pull request with your fix? That'd be great, thank you.

On Tue, Feb 13, 2018 at 7:14 AM, Simon Bradley <captain.bal...@gmail.com>
wrote:

> OK def fixed it now
>
> This line in the views.py of filebrowser-safe:
>
> if not normalized.startswith(get_directory()) or ".." in normalized:
>
> It appears to be the problem.
>
> I changed it to:
>
> if not normalized.startswith(get_directory().strip("/")) or ".." in
> normalized:
>
> Removed the FILEBROWSER_DIRECTORY entry from the local_settings.py because
> i generally stick with the default path anyway.
>
> Tested everything. Looks like it's working. I know there was a bit of a
> false alarm before but this time i'm fairly sure.
>
> If there's a simpler way to get around this though i'd like to know it.
>
> It's a bit of a faff having to have my own version of filebrowser-safe for
> every mez proj.
>
>
>
>
>
> On Monday, February 12, 2018 at 7:54:20 PM UTC, Simon Bradley wrote:
>>
>> A!
>>
>> Now i can't navigate in the media library.
>>
>> LOL!
>>
>> Still. Bound to be able to figure it out from here!
>>
>> On Monday, February 12, 2018 at 7:47:15 PM UTC, Simon Bradley wrote:
>>>
>>> Also, thanks to Mathias.
>>>
>>> It was your advice that led me to it.
>>>
>>> - Uninstalled filebrowser-safe
>>> - Cloned a fresh one from the repo
>>> - did setup.py develop
>>> - fiddled with the messages from delete
>>> - found said problem
>>>
>>>
>>> On Monday, February 12, 2018 at 7:43:46 PM UTC, Simon Bradley wrote:
>>>>
>>>> Well i found the problem.
>>>>
>>>> Very silly. Silly windows user.
>>>>
>>>> filebrowser-safe get_directory() picks up the directory from
>>>> settings.py or the default 'uploads/' and it's as simple as that it seams.
>>>>
>>>> Because for it to work on windows the path needs to be 'uploads\'
>>>>
>>>> A backslash. That's it.
>>>>
>>>> So i just added this:
>>>>
>>>> FILEBROWSER_DIRECTORY = 'uploads\\'
>>>>
>>>> To my local_settings.py and now we're good.
>>>>
>>>> Hope this helps some people.
>>>>
>>>>
>>>> On Saturday, February 10, 2018 at 7:12:02 PM UTC, Simon Bradley wrote:
>>>>>
>>>>> Yo!
>>>>>
>>>>> Does anyone have any idea about this? Googling it seems to suggest it
>>>>> has lingered for several years. It's a real annoyance because overall i
>>>>> really like mezzanine and have developed a couple of sites with it now. 
>>>>> I'm
>>>>> also using windows 10 and everything else works great.
>>>>>
>>>>> Would be great if i had any kind of workaround for this.
>>>>>
>>>>> Anyone any idea?
>>>>>
>>>>> Anyone at all?
>>>>>
>>>>> I mean i spent a fair amount of time fiddling with it. Looking here:
>>>>> https://docs.python.org/3/library/os.html
>>>>>
>>>>> It says this:
>>>>> Although Windows supports chmod()
>>>>> <https://docs.python.org/3/library/os.html#os.chmod>, you can only
>>>>> set the file’s read-only flag with it (via the stat.S_IWRITE and
>>>>> stat.S_IREADconstants or a corresponding integer value). All other
>>>>> bits are ignored.
>>>>>
>>>>> Now i'm not really all that knowledgeable in this area but is that
>>>>> saying that because Mezzanine uses chmod that you can't actually change 
>>>>> the
>>>>> file permissions on windows through mezzanine?
>>>>>
>>>>> If so could there be another way? Maybe changing the file permissions
>>>>> in windows explorer somehow?
>>>>>
>>>>> Welcome a discussion here folks. I know someone out there knows more
>>>>> about this than i do. In fact i suspect their number may be legion.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, November 29, 2017 at 8:42:17 PM UTC, Alexander Yang
>>>>> wrote:
>>>>>>
>>>>>> Hi. I'm trying Mezzanine on Windows 10 and facing this same issue. I
>>>>>> can't delete images from the media library in the admin interface. Same
>>>>>> error message. Did you manage to solve this?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>>
>>>>>> On Friday, 27 March 2015 02:41:22 UTC+1, Wan Hsin Mao wrote:
>>>>>>>
>>>>>>> I'm using the newest version of Mezzanine as my website CMS. There
>>>>>>> is always "An error occurred" message after  I click the trash can
>>>>>>> icon. Is there any way to find out what's going wrong or anything 
>>>>>>> suggested
>>>>>>> that I can check to solve this error?
>>>>>>>
>>>>>>> p.s. I just want to delete the .ppt file in admin page.
>>>>>>>
>>>>>> --
> 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] Issues with rich-text filtering in version 4.3.0

[Stephen McDonald]

I've just pushed 4.3.1 which resolves this.

Thanks

On Fri, Aug 3, 2018 at 8:25 AM,  wrote:

> Context:
> Mezzanine: 4.3.0
> Python: 2.7.14
>
> Hi there,
>
> I have noticed that rich-text filtering (of HTML tags at least) is not
> working on my Mezzanine 4.3.0 installation,
>
> Regardless of `RICHTEXT_FILTER_LEVEL` or `RICHTEXT_ALLOWED_TAGS` being set
> in `settings.py`, I am able to drop 

Re: [mezzanine-users] Not possible to use extra_context in Page view?

[Stephen McDonald]

Just pushed a fix for that here:

https://github.com/stephenmcd/mezzanine/commit/4e94ab99555f5b2f4852a5a6ae0918695e5d3ba6

On Thu, Aug 9, 2018 at 8:47 PM, Tuk Bredsdorff  wrote:

> Hi,
>
> I am using the 'HOMEPAGE AS AN EDITABLE PAGE IN THE PAGE TREE'-pattern in
> urls.py and it's working fine.
>
> Now I would like to add to the context but it's not working.
>
> This is what I have in urls.py:
>
>   url('^$', mezzanine.pages.views.page, {'slug': '/', 'extra_context':
> {'my_var': 'Something extra'}}, name='home'),
>
> my_var is, however, not set on the index page and neither when expecting
> the request with the debug toolbar.
>
> Am I doing something wrong?
>
> Best,
> Tuk
>
> --
> 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] Re: Mezzanine beyond Django 1.10

[Stephen McDonald]

On Mon, Feb 19, 2018 at 10:29 PM, Wim Feijen <w...@go2people.nl> wrote:

> Hello,
>
> I was wondering what we can do to help in the release of a new stable
> Mezzanine which supports Django 1.11 LTS or Django 2.0?
>

Django 1.11 support has been available for the last 10 months, all you need
to do is depend on the latest explicit commit on GitHub. If you'd like to
see 2.0 support, please run the default Mezzanine project against 2.0, test
every documented feature and see if you contribute the necessary fixes for
compatibility. Once that's done and there are no issues, voila - 2.0 will
be supported.

Unfortunately we work in an environment where stability is of much more
> importance than using a quick leading edge release.
>

You and your team or whoever else perceives a difference between a PyPI
release and what's on GitHub, unfortunately suffers from an inaccurate
perception.

Here's the crux of it - if we were pushing commits very frequently to
GitHub, constantly breaking things, as is the case very early on in the
development of a project, then your perception would be accurate. Picking a
commit and depending on it would be a gamble. But the commits to Mezzanine
for several years now have been infrequent and minor. Non-breaking changes,
no new features. The project (and specifically the master branch on GitHub)
is very stable. You can pick the latest commit on GitHub and add it to your
dependencies file and you're now working with the latest version.

The only significant changes that have occurred over the years have been
updates for compatibility with the latest Django versions. These changes
are generally long-developed in a pull request on GitHub and heavily tested
and refined before being merged into the master branch. Again, the
stability of the master branch is something always striven for.

If we were to push a build to PyPI right now, there would literally be no
difference between that and specifying an exact commit on GitHub in your
dependencies file, which is something you can do right now. The code would
function exactly the same way.

I hope this paints a clear picture of where Mezzanine is and how you can
use the most update to date version of it with confidence. To reiterate -
commits to the master branch are *stable and infrequent*. There is no
technical or conceptual difference between a commit on GitHub and PyPI
release. Each commit to GitHub is a new version. Want the latest version?
Update the commit referenced in your dependencies.

Why don't we just push a release? There's a lot of work involved and the
process needs a lot of improvement. The team has been recently discussing
this off-list. But the idea that the project is dead or isn't a viable
option, considering all the above, is nonsense. The project is mature,
which means development is infrequent and stable, but as active as
necessary.



> We are stuck in a situation where dropping Mezzanine is actually being
> considered as an option. I would rather help the open source project
> Mezzanine forward than drop it. So that's why I feel forced to bump my
> question. Apologies for that.
>
> Best regards,
>
> Wim
>
>
> Op woensdag 10 januari 2018 17:38:07 UTC+1 schreef Wim Feijen:
>
>> Hello,
>>
>> The latest Mezzanine release 4.2.3 support Django up to Django 1.10,
>> which does not receive security updates anymore. See:
>> https://www.djangoproject.com/download/#supported-versions
>>
>> How can we help to release a new version of Mezzanine which support
>> Django 1.11 LTS or Django 2.0?
>>
>> Although I love the high quality of development branches, using a
>> development branch (git version) of Mezzanine is not possible for us,
>> because it is not stable enough.
>>
>> Best regards,
>>
>> Wim
>>
>> --
> 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] The user is active but won't be able to access the admin

[Stephen McDonald]

You need to assign at least one site permission which defines the site(s)
the user has admin access to, see the bottom of this screenshot:

[image: Screen Shot 2018-10-25 at 12.22.52 PM.png]

On Thu, Oct 25, 2018 at 7:21 AM Jason Matta  wrote:

> I have created a group that has permissions to add, edit delete pages and
> users.
>
> when i create a user and assign them to the group and go to save, i get
> the message "The user is active but won't be able to access the admin, due
> to no edit/site permissions being selected" and indeed cannot login to the
> admin site
>
> i HAVE also set the staff status which should allow the user to login.
>
> looking at the mezzanine code, it checks for permissions and if it doesnt
> have any, it will display that message.
>
> Should it not check the group permissions that the user is in also? is the
> group functionality broken or am i missing something.??
>
>
> --
> 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] TypeError, Direct assignment to the reverse side of a related set is prohibited. Use +.set() instead

[Stephen McDonald]

python3.6/site-packages/django/forms/models.py",
> line 439, in _save_m2m
> f.save_form_data(self.instance, cleaned_data[f.name])
>   File
> "/home/mike/projects/plab/venv/lib/python3.6/site-packages/mezzanine/generic/fields.py",
> line 206, in save_form_data
> super(KeywordsField, self).save_form_data(instance, data)
>   File
> "/home/mike/projects/plab/venv/lib/python3.6/site-packages/django/db/models/fields/__init__.py",
> line 838, in save_form_data
> setattr(instance, self.name, data)
>   File
> "/home/mike/projects/plab/venv/lib/python3.6/site-packages/django/db/models/fields/related_descriptors.py",
> line 509, in __set__
> % self._get_set_deprecation_msg_params(),
> TypeError: Direct assignment to the reverse side of a related set is
> prohibited. Use +.set() instead.
> [12/Nov/2018 14:28:08] "POST /admin/pages/richtextpage/add/ HTTP/1.1"
> 500 146350
>
> Attempting to debug this in pycharm, I found that the item being saved was
> a 'keyword' of ''. I had not entered any keywords in the form, so it
> appears the empty string is saved, anyway. I've read through both django
> and mezzanine code in the callstack, and it seems like this is related to
> django's database layer and ManyToMany relationships. But it seems the
> ultimate saving of the empty keyword is a Field.setattr() call, which is
> neither an = or a .set(). And I don't know what the '+' character is from.
>
> Can anyone help me to understand what needs to be fixed, here? Since I
> haven't actually written any code, I'm tempted to think either mezzanine or
> django needs a pull request. Or perhaps there's a compatibility issue
> between versions of django and mezzanine? I haven't seen anything obvious
> in git diffs. But until I understand better, I wouldn't know how to go
> about fixing it. I have found a few slightly similar things in this group
> and on stackexchange, but nothing that matches. The same behavior occurs if
> I run the server and try to add a blog post rather than a richtextpage. And
> I get the same behavior on a different server running debian 8 rather than
> ubuntu 18.
>
> Thanks for any advice!
>
> --
> 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] How to resize image on upload ?

[Stephen McDonald]

On Mon, Nov 26, 2018 at 3:27 AM Nicolas Pinault <3...@drpi.fr> wrote:

> Le 24/11/2018 à 23:47, Danny a écrit :
>
> On 25/11/2018 3:43 am, Nicolas Pinault wrote:
>
>
> Hi,
>
> Le 14/10/2018 à 02:33, Danny a écrit :
>
> On 13/10/2018 11:41 PM, 3...@drpi.fr wrote:
>
> Hi,
>
> When uploading images in blog post or in media library, I get an error
> saying the file size is too big.
> I don't want to modify the file size limit, my images come from a DSLR
> generating big files.
> What I'd like, this is to be able to resize uploaded images automatically.
> I this possible ?
>
>
> How would this work? In order for the server to do the resizing (which I
> guess is what you want, as that's where Pillow is installed), you'd have to
> upload the full file, and then allow the server to resize it - in which
> case, you're uploading the large file anyway, so you'd have to remove the
> file size limit to allow grapelli to upload that size file.
>
> If you want to resize the file locally before uploading - why would this
> be a feature of Mezzanine, which is server-based? Can't you just resize the
> pictures yourself using any photo app on your local computer/device, and
> then do the upload?
>
> There are 3 ways of doing the resize :
> 1) Server side. I have to authorize bigger files to be uploaded. Then, how
> do I resize the image ?
>
>
> It looks like this is the best option.
> So, how do I resize the image when it is uploaded ?
>
> Use Pillow to do the resizing (https://pillow.readthedocs.io/en/5.3.x/ )
> but I'm not sure where in the Mezzanine code to put this - possibly as part
> of a filebrowser or grapelli fork?
>
> Sure, Pillow is the way to go.
> But where do I put the resize code ?
>

Mezzanine generally doesn't resize images on upload, instead opting to
resize images server-side when they're first requested. The code for doing
this resides in the template where the image is displayed, see:
http://mezzanine.jupo.org/docs/utilities.html#thumbnail


>
>
> --
> 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] Change size of RichTextField in the admin

[Stephen McDonald]

If you override the admin template for that admin class (
https://docs.djangoproject.com/en/1.11/ref/contrib/admin/#admin-overriding-templates)
you can apply some custom CSS which should allow you to do what you want.

While I personally think using RichTextField inside inlines like that is an
extremely clunky user experience, we could probably provide the CSS by
default in Mezzanine (without having to override admin templates) to make
this behave better in a general way - so if you can contribute the fix back
to the project by way of a pull request, that would be great.



On Tue, Nov 27, 2018 at 4:37 AM Tyger Marshall 
wrote:

> I'm looking for a way to change the size of the RichTextField in the admin
> interface. I have a model with the field Description that is a
> RichTextField. The field isn't very user-friendly via the admin, see the
> attached image. How would I go about resizing to have more working area?
> Thanks!
>
> --
> 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] Re: Mezzanine+Security+Issue

[Stephen McDonald]

Thanks Susanne.

Unfortunately it looks like this issue was discovered and made public
without any communication with the project itself, thusly this is the first
we've heard of it and there was no fix until now.

It's now resolved in a dependency ironically called "grappelli-safe", which
I just pushed a new version of (0.5.2) to PyPI containing the fix, which
you can see on GitHub here:

https://github.com/stephenmcd/grappelli-safe/commit/cb1d459b2cb96be4ea8be33060da7874525510e0

New installs of the current Mezzanine version will automatically pick this
up.

Thanks again,
Steve

On Fri, Mar 15, 2019 at 11:31 AM Ramsey, Susanne B. 
wrote:

> Hello
>
>
> I have searched various locations, but can find nothing concerning a fix
> for CVE-2018-16632 <https://nvd.nist.gov/vuln/detail/CVE-2018-16632>.  
> Mezzanine
> CMS v4.3.1 allows XSS via the
> /admin/blog/blogcategory/add/?_to_field=id&_popup=1 title parameter at
> admin/blog/blogpost/add/.
>
> Has this been addressed or will it be ??
>
>
>
> Many thanks!
>
> Susanne
>
>
>
>
>
>
>
> **
>
> *Susanne B. Ramsey*
>
> *Physical and Life Sciences Directorate *
>
> *Lawrence Livermore National Laboratory*
>
> *7000 East Ave., L-556   *
>
> *Livermore, CA 94550*
>
>
>
> *Email **rams...@llnl.gov *
>
> Office *(925)423-9530 Cell (925)980-7621*
>
> **
>
> *"Experience is what you get when you didn't get what you wanted."*
>
>
>


-- 
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] Mezzanine 5.0 alpha 1 released!

[Stephen McDonald]

Thanks for all your hard work with this Ed and for taking the reins
overall.

Really cool to see some of the meta improvements you've made too.

On Wed, Sep 9, 2020 at 12:02 PM Eduardo Rivas 
wrote:

>
> Hello everyone!
>
> I'm very happy to announce that the first pre-release of the next major
> version of Mezzanine is now available: 5.0.0 alpha 1. You can download it
> right now with `pip install -U mezzanine==5.0.0a1`. This will also get you
> the alpha versions for filebrowser-safe and grappelli-safe.
>
> *The biggest change is that we have completely dropped support for Python
> 2 and Django versions prior to 2.2.*
>
> Other than that you can check out the pre-release notes over at GitHub:
> https://github.com/stephenmcd/mezzanine/releases/tag/v5.0.0-alpha.1
>
> With this version we're also testing a new release process based on
> Semantic Versioning that should make it much easier to publish pre-release
> and stable versions to PyPI so the community can test Mezzanine without
> having to install from GitHub.
>
> Additionally, since this is an alpha release, we request you do not use it
> in production systems (unless you're ready to report and/or fix bugs). You
> can help get Mezzanine to a stable release by filing bug reports on the
> GitHub issue tracker. The community has already identified a few minor bugs
> which are now being worked on as you can see here:
> https://github.com/stephenmcd/mezzanine/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22
>
> Finally, I want to publicly thank Stephen McDonald who authored and
> maintained Mezzanine for many years, as well as many other members of the
> core team and the larger community who have made Mezzanine what it is
> today. Going forward I (Ed Rivas) will be serving as the maintainer of the
> project. I look forward to helping grow and nurture this amazing CMS.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mezzanine-users/9d034202-e26c-4596-b966-fb1523c12d94n%40googlegroups.com
> <https://groups.google.com/d/msgid/mezzanine-users/9d034202-e26c-4596-b966-fb1523c12d94n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mezzanine-users/CAFDn9NbE%3DuJMVSvuomd7FAktVGTn72U2pjUwoPJBuNk2GaNTUQ%40mail.gmail.com.

Re: [mezzanine-users] Weird alerts in demo blogposts

[Stephen McDonald]

Thanks for pointing this out. It was an old XSS bug that was fixed and
released around a year ago (see:
https://groups.google.com/forum/#!topic/mezzanine-users/BGGeI1Ncjuo) but
had not been applied to the demo site, which I've done now.

Just a reminder - if you believe you have come across a potential security
issue, please use the private email address core-t...@mezzaninecms.com to
report the issue, as noted in the readme. That gives a chance to resolve
the issue and get it released to the private security group (
https://groups.google.com/forum/#!forum/mezzanine-security) and rolled out
to public sites before being made public.



On Wed, May 27, 2020 at 11:17 PM Αντώνης Καρβελάς 
wrote:

> I get weird alerts in the demo blogposts section:
> http://mezzanine.jupo.org/en/admin/blog/blogpost/
> I wonder if someone tried to implant XSS...
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mezzanine-users/be02fff1-e4a3-4ea2-88b3-842b8ec3574a%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mezzanine-users/CAFDn9Nb8AFXKyiJndJzcXqB8M01M4svat-TpgqTkvHng%3DFU8Zw%40mail.gmail.com.