Re: [mezzanine-users] Re: django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

[Ryne Everett]

You might try raising an exception on the first line of local_settings.py just 
to make sure it’s being imported.

-- 
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.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

[Ryne Everett]

I would follow the flow of execution to ensure your local_settings are
being sourced. For example, in the default project template:

1. You're running makemigrations through manage.py which defines
DJANGO_SETTINGS_MODULE as the settings.py file in your main project
directory.

settings_module = "%s.settings" % real_project_name("{{ project_name }}")
os.environ.setdefault("DJANGO_SETTINGS_MODULE", settings_module)

2. The settings.py looks for a local_settings.py file in the
main project directory and imports it.

f = os.path.join(PROJECT_APP_PATH, "local_settings.py")
if os.path.exists(f):
import sys
import imp
module_name = "%s.local_settings" % PROJECT_APP
module = imp.new_module(module_name)
module.__file__ = f
sys.modules[module_name] = module
exec(open(f, "rb").read())

If your project looks different than the default, that would be
noteworthy.

-- 
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 hide a link in the navbar when a user is logged in/out?

[Ryne Everett]

Not the most elegant solution but you should be able to do something
like this:

{% if page.in_menu %}
{% if page.slug == 'login_register' %}
{% if not user.is_staff %}

{{ page.title }}

{% endif %}
{% else %}

{{ page.title }}

{% endif %}
{% endif %}

-- 
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] Adding a Button to TinyMCE Issue

[Ryne Everett]

Pardon if I'm misunderstanding the question, but are you adding it to
the toolbar field in tinymce_setup?

-- 
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 create a form for blog posts that accepts image uploads

[Ryne Everett]

While several security issues have been recognized and patched in
filebrowser_safe more readily than in filebrowser, the "safe" aspect is
a reference to package stability and not security. However, I would be
very surprised if use of Filebrowser with Mezzanine does not have
numerous bugs and broken features. Filebrowser_safe has
Mezzanine-specific code in it that Filebrowser does not.

-- 
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: Lost in javascript

[Ryne Everett]

I just created a fresh project and got the forecolor and background
buttons working:

1. `cp mezzanine/mezzanine/core/static/mezzanine/js/tinymce_setup.js 
example_project/static/`
2. Edit tinymce_setup.js, adding "textcolor" to `plugins` and "forecolor
backcolor" to `toolbar`.
3. Edit settings:

TINYMCE_SETUP_JS = 'tinymce_setup.js'
RICHTEXT_ALLOWED_STYLES = ("border", "display", "float", "list-style-type",
   "margin", "margin-bottom", "margin-left",
   "margin-right", "margin-top", "padding-left",
   "text-align", "text-decoration", 
"vertical-align",
   "color", "background-color")

-- 
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] Models aren't loaded yet

[Ryne Everett]

A traceback would be helpful.

-- 
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] Lost in javascript

[Ryne Everett]

Quoting Malik Rumi (2017-08-13 20:00:19)

> *2. In the docs at*
> 
> 
> http://mezzanine.jupo.org/docs/packages.html?highlight=settings#mezzanine.conf.Settings
> 
> 
> I see a reference to *class* mezzanine.conf.*Settings**.* I have no such 
> file at that location, or any location that I have searched for. 

The Settings class is not a file but an internal abstraction around the
settings you provide (conventionally in settings.py).

> *3. In the TinyMCE docs * 
> 
> 
> https://www.tinymce.com/docs/get-started/basic-setup/
> 
> 
> It talks about snippet examples. I do see these examples, but what I am 
> supposed to do with them remains a mystery. Thinking that I could just copy 
> and paste these snippets into an existing file, I've been looking all over 
> my code for a working example of 
> 
> 
> "tinymce.init"
> 
> 
> but been unable to find one.

Copy the default setup from
`mezzanine/core/static/mezzanine/js/tinymce_setup.js` into your static
assets, change the `TINYMCE_SETUP_JS `
(http://mezzanine.jupo.org/docs/configuration.html#tinymce-setup-js)
value to your custom path, and then make modifications to it.

> 5 mg is too big!?

Django's default maximum is 2.5mb:


-- 
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: Possible to remove fields inherited from Page in custom models?

[Ryne Everett]

I don't think you're going to do much better than Ken's solution.

-- 
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] wysiwyg

[Ryne Everett]

Tinymce comes bundled with the project. Once you log into the admin a
lot of content becomes inline-editable if that's what you're after.

-- 
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] Get the click event from a button

[Ryne Everett]

Sorry, I think I understand what you're asking now.

You want to have a form submitted to a page processor which will use the
form's data to add context to the page and re-render the view. If I
understand you correctly, you're asking how to add a submission button
to the html form that will call the page processor.

I don't know the answer. I'd have to look at the source and don't have
time at the moment. Seems like it ought to be included with the example
in the documentation.

-- 
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] Get the click event from a button

[Ryne Everett]

I don't think page processors are relevant to your use case. If you're
not familiar, I would suggest looking into django's form docs:
.

-- 
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] Simplifying rich text

[Ryne Everett]

> 2) Implement the approach to RichTextField and global editor configuration 
> from django-
> ckeditor, but leave TinyMCE as default. Introducing as little 
> incompatibilities as possible 
> would be the hard part.

Sounds like #2 is the approach for improving the core project, though
creating a third-party mezzanine-ckeditor project would also be useful.

Could you expand (perhaps with a code sample) on how django-ckeditor
makes inline RichTextField configuration easier than Mezzanine?

-- 
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] Simplifying rich text

[Ryne Everett]

The direction this discussion goes hinges on whether ckeditor is a
preferable editor to tinymce or if django-ckeditor just has a more
powerful RichTextField implementation than Mezzanine.

-- 
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] blog_months template may be incorrect when USE_TZ is set to True

[Ryne Everett]

I agree. See .

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

[Ryne Everett]

Could we use the existant `SITE_TITLE` setting instead?

Or could we put the admin title in it's own template block to ease
template maintenance without increasing Mezzanine maintenance. E.g.:
`{% block admin_title
%}Mezzanine{% endblock}`.

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

[Ryne Everett]

I went ahead and submitted the patch:
.

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

[Ryne Everett]

I can reproduce with both the OP's project and a fresh project following
the docs on both current master and right after the patch landed.

A quick look at django-debug-toolbar suggests that the `{% if
content_models.count > 1 %}` condition in the
`admin/shop/product/change_list.html` template isn't being triggered,
even though I can see more than one item in the `content_models` context
variable.

-- 
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] upload thumbnails rendering with relative URLs instead of absolute (AWS S3)

[Ryne Everett]

Your analysis appears correct to me. Care to open a PR?

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

[Ryne Everett]

Ah, my bad. Are you seeing this in DEBUG mode on localhost?

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

[Ryne Everett]

A common mistake is failing to add the site permissions for staff users.
If a user doesn't have permissions for any site, they will not be able
to log in.

This was discussed in a recent thread and a patch was added to the
development version of mezzanine to warn users when they're about to
create a staff user that cannot log in (usually not desirable).

-- 
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 thumbnails when the original image has been updated

[Ryne Everett]

That makes sense to me. I'd suggest sending a pull request.

-- 
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] Implementing an Editable Django Forms with Mezzanine (with emailing function)

[Ryne Everett]

Quoting Carl Almayda II (2017-01-13 00:01:39)
> It seems that mezzanine forms are intended for content 
> management, not on email ...

There's an email section in the form page admin ...

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

[Ryne Everett]

Quoting dunrix...@gmail.com (2016-12-24 01:04:21)
> Never when exposed to public. On the other hand, it is quite common at 
> development test app in non-debug mode, before fiddling with nginx/apache 
> configuration. At least in our region.

This practice doesn't make a lot of sense to me. It may be easier to get
going but you're testing an environment that still isn't very
production-like.

> If this looks like bug and not intended behavior, would anyone attempt to 
> fix it ? I'd like help myself, but it feels beyond my knowledge of 
> Mezzanine internals.

Due to the above reasoning, I'm doubtful anyone will be inspired to fix
this. Setting up production static asset serving will probably be easier
and you need to do it eventually anyway.

-- 
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] Problem with TinyMCE and html

[Ryne Everett]

I'm not able to reproduce this on stock mezzanine. Are you using any
custom [richtext
filters](https://mezzanine.readthedocs.io/en/latest/configuration.html#richtext-filters)
by chance? Whenever I've had issues with extra ``'s in a richtext
field beautiful soup has ultimately been to blame for adding closing ``'s.

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

[Ryne Everett]

Page models *are* database models.

-- 
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: Extra model fields at Mezzanine's derived package ?

[Ryne Everett]

I'm aware of this option, but it is a dictionary with application name 
as a key, right ? How can I tell Django to look for /cartridge.shop/ 
migrations both at original path and my extension package ?
In this case the application name is just /shop/. After setting up 
MIGRATION_MODULES, your first run of `makemigrations` will squash the 
existing migrations into one file and your extension package will be the 
only place django looks for /shop/ migrations from now on. This means 
you'll need to ship any future migrations in cartridge yourself.


I'm not sure what you're thinking on this, but I would document how to 
make the necessary changes to EXTRA_MODEL_FIELDS and MIGRATION_MODULES 
as part of the installation process rather than modifying them in your app.


--
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: Upgrading from 4.1 to 4.2 fails

[Ryne Everett]

I followed the installation docs
(http://mezzanine.jupo.org/docs/overview.html#installation), went to the
default pages, and was able to add subpages no problem.


On 11/10/2016 04:09 AM, Gerhard Spitzlsperger wrote:
> Hi Ryne,
>
> thanks for your quick answer. I tried again with a fresh install, for
> me it does not fix the issue. I have installed as well
> django-modeltranslation and mezzanine-pagedown.
> It works under 4.1 could you please let me know what you  exactly do.
>
> Thank you very much
> Gerhard
>
>
>
> Am Mittwoch, 14. September 2016 12:26:26 UTC+2 schrieb Gerhard
> Spitzlsperger:
>
> Dear All,
>
> I tried to upgrade mezzanine from 4.1 to 4.2 and the system
> crashed. As I did not find somethin different I did a naive pip3
> --upgrade. I tried to sites (one pretty fresh created under 4.1)
>
> both sites are deployed using apache2.4 and mod_wsgi
>
> after downgrading again to 4.1 everything worked.
>
> Thanks a lot for any hint
> Gerhard
>
> Traceback (most recent call last):
> [:error] [pid 9181] [remote ...:40070]   File
> "/home/django/mezzanine/blueberrye/blueberrye/wsgi.py", line 29,
> in 
> [:error] [pid 9181] [remote ...:40070] application =
> get_wsgi_application()
> [:error] [pid 9181] [remote ...:40070]   File
> "/home/django/mezzanine/lib/python3.4/site-packages/django/core/wsgi.py",
> line 13, in get_wsgi_application
> [:error] [pid 9181] [remote ...:40070]
> django.setup(set_prefix=False)
> [:error] [pid 9181] [remote ...:40070]   File
> "/home/django/mezzanine/lib/python3.4/site-packages/django/__init__.py",
> line 27, in setup
> [:error] [pid 9181] [remote ...:40070]
> apps.populate(settings.INSTALLED_APPS)
> [:error] [pid 9181] [remote ...:40070]   File
> 
> "/home/django/mezzanine/lib/python3.4/site-packages/django/apps/registry.py",
> line 78, in populate
> [:error] [pid 9181] [remote ...:40070] raise
> RuntimeError("populate() isn't reentrant")
> [:error] [pid 9181] [remote ...:40070] RuntimeError: populate()
> isn't reentrant
> [[:info] [pid 9181] mod_wsgi (pid=9181): Shutdown requested
> 'blueberrye.cc'.
> [:info] [pid 9181] mod_wsgi (pid=9181): Stopping process
> 'blueberrye.cc'.
> [:info] [pid 9181] mod_wsgi (pid=9181): Destroying interpreters.
> [:info] [pid 9181] mod_wsgi (pid=9181): Destroy interpreter
> 'blueberrye.cc|'.
> [:error] [pid 9181] Exception ignored in:  '/usr/lib/python3.4/threading.py'>
> [:error] [pid 9181] Traceback (most recent call last):
> [:error] [pid 9181]   File "/usr/lib/python3.4/threading.py", line
> 1288, in _shutdown
> [:error] [pid 9181] assert tlock is not None
> [:error] [pid 9181] AssertionError:
> [:info] [pid 9181] mod_wsgi (pid=9181): Cleanup interpreter ''.
> [:info] [pid 9181] mod_wsgi (pid=9181): Terminating Python.
> [:error] [pid 9181] Exception ignored in:  '/usr/lib/python3.4/threading.py'>
> [:error] [pid 9181] Traceback (most recent call last):
> [:error] [pid 9181]   File "/usr/lib/python3.4/threading.py", line
> 1288, in _shutdown
> [:error] [pid 9181] assert tlock is not None
> AssertionError:
>
>
> -- 
> 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] Edit/Insert Link in Rich Text Page feature broken

[Ryne Everett]

I can't reproduce this. It works fine for me on 4.2.2.

On 11/06/2016 06:58 PM, Chirag Dua wrote:
> This was fixed in trunk earlier:
>
> https://github.com/stephenmcd/mezzanine/commit/94d57294bcc1e934fdd723546be7ea15bb9dcd1a
>
> I can see this in 4.2.2 as well but feature seems to be broken again.
>
> I had 4.1 and just upgraded to 4.2.2
>
> Can someone pls help?
>
> And make migrations don't detect anything, so I hope no data model
> changes from 4.1 to 4.2.2
>
> 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.

Re: [mezzanine-users] Re: Upgrading from 4.1 to 4.2 fails

[Ryne Everett]

FYI, I can't reproduce this issue on a freshly generated mezzanine project.

On 11/09/2016 11:59 AM, Gerhard Spitzlsperger wrote:
> Dear All,
>
> in the meantime I fixed this problem by installing a fresh Mezzanine
> 4.2.2 environment and copying over my projects. This works (after
> getting static files and templates right).
>
> ONLY ONE issue remains: If I want to add a new page I can do so using
> the top level /add page /menu; unfortunately  if I try use the menu to
> add a sub page for an existing page the menu is empty.
>
> After looking a bit through the source code I suspect it has something
> to do with permissions but I am not sure.
>
> If you have any suggestion 
>
> Thank you very much
> Gerhard
>
>  
>
> Am Mittwoch, 14. September 2016 12:26:26 UTC+2 schrieb Gerhard
> Spitzlsperger:
>
> Dear All,
>
> I tried to upgrade mezzanine from 4.1 to 4.2 and the system
> crashed. As I did not find somethin different I did a naive pip3
> --upgrade. I tried to sites (one pretty fresh created under 4.1)
>
> both sites are deployed using apache2.4 and mod_wsgi
>
> after downgrading again to 4.1 everything worked.
>
> Thanks a lot for any hint
> Gerhard
>
> Traceback (most recent call last):
> [:error] [pid 9181] [remote ...:40070]   File
> "/home/django/mezzanine/blueberrye/blueberrye/wsgi.py", line 29,
> in 
> [:error] [pid 9181] [remote ...:40070] application =
> get_wsgi_application()
> [:error] [pid 9181] [remote ...:40070]   File
> "/home/django/mezzanine/lib/python3.4/site-packages/django/core/wsgi.py",
> line 13, in get_wsgi_application
> [:error] [pid 9181] [remote ...:40070]
> django.setup(set_prefix=False)
> [:error] [pid 9181] [remote ...:40070]   File
> "/home/django/mezzanine/lib/python3.4/site-packages/django/__init__.py",
> line 27, in setup
> [:error] [pid 9181] [remote ...:40070]
> apps.populate(settings.INSTALLED_APPS)
> [:error] [pid 9181] [remote ...:40070]   File
> 
> "/home/django/mezzanine/lib/python3.4/site-packages/django/apps/registry.py",
> line 78, in populate
> [:error] [pid 9181] [remote ...:40070] raise
> RuntimeError("populate() isn't reentrant")
> [:error] [pid 9181] [remote ...:40070] RuntimeError: populate()
> isn't reentrant
> [[:info] [pid 9181] mod_wsgi (pid=9181): Shutdown requested
> 'blueberrye.cc'.
> [:info] [pid 9181] mod_wsgi (pid=9181): Stopping process
> 'blueberrye.cc'.
> [:info] [pid 9181] mod_wsgi (pid=9181): Destroying interpreters.
> [:info] [pid 9181] mod_wsgi (pid=9181): Destroy interpreter
> 'blueberrye.cc|'.
> [:error] [pid 9181] Exception ignored in:  '/usr/lib/python3.4/threading.py'>
> [:error] [pid 9181] Traceback (most recent call last):
> [:error] [pid 9181]   File "/usr/lib/python3.4/threading.py", line
> 1288, in _shutdown
> [:error] [pid 9181] assert tlock is not None
> [:error] [pid 9181] AssertionError:
> [:info] [pid 9181] mod_wsgi (pid=9181): Cleanup interpreter ''.
> [:info] [pid 9181] mod_wsgi (pid=9181): Terminating Python.
> [:error] [pid 9181] Exception ignored in:  '/usr/lib/python3.4/threading.py'>
> [:error] [pid 9181] Traceback (most recent call last):
> [:error] [pid 9181]   File "/usr/lib/python3.4/threading.py", line
> 1288, in _shutdown
> [:error] [pid 9181] assert tlock is not None
> AssertionError:
>
>
> -- 
> 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] Cartridge: How to override the name of the product and variations in the cart / checkout?

[Ryne Everett]

Thanks, I'll probably use that some time. However, I'd likely use the
class_prepared signal
(https://docs.djangoproject.com/en/stable/ref/signals/#class-prepared)
so I'm not reliant on my app being after `cartridge.shop` in
`INSTALLED_APPS`.

-- 
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] Override behaviour of "image upload" in media library

[Ryne Everett]

The functionality is in filebrowser-safe
(https://github.com/stephenmcd/filebrowser-safe/blob/master/filebrowser_safe).

My first thought is use the filebrowser_pre_upload or
filebrowser_post_upload signal
(https://github.com/stephenmcd/filebrowser-safe/blob/master/filebrowser_safe/views.py).
These signals are not currently documented but I don't think they're
likely to be deleted any time soon.

On 11/04/2016 10:12 AM, Valeriia Sytchenko wrote:
> I want to add additional functionality to image uploader.
>
> Now I'm building a shop with Cartridge/ Mezzanine. 
> When editing Product, admin could add image using media library. When
> admin select file from local PC, it uploads to MEDIA ROOT without any
> changes. 
> I need to add resizing and putting watermark on it, so that after
> pushing "upload" button, all selected images will be resized,
> watermaark will be put and then uploaded to MR folder. 
>
> The problem is that I've searched via both of packages and haven't
> found where those functions related to Media library live.
>
> -- 
> 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] Cartridge: How to override the name of the product and variations in the cart / checkout?

[Ryne Everett]

I agree that the current default behavior isn't great for everybody. I'm
not thrilled by it myself but have lived with it so far.

One approach would be to improve the default behavior in cartridge,
though I don't have a proposal for a more generally acceptable format at
hand.

Another approach would be to add a cartridge setting for a function that
formats this string, but I'm not sure that can be justified.

Perhaps monkey-patching the ProductVariation.__str__ method would be the
best approach. I don't think I've monkey-patched model methods before
but you might come up with a sensible way to do it with experimentation
and/or searching the web.

Please give a report if you come up with anything.

On 11/02/2016 05:20 AM, Pete Dermott wrote:
> Hi Everyone,
>
> I'm looking to create a Cartridge store that offers the ability for
> customers to buy low cost samples of our products, my thought was to
> use the variations system to do so.
>
> However, when I get to the checkout the system puts the items in the
> cart as $ProductName $ProductOptionType: $ProductOptionName so for
> example, with my product option type of "Shippable" this turns into
> "Product Name Shipable: Sample" which isn't really ideal.
>
> What I would like to do instead is remove the modification of the
> product description and show the original description and a separate
> field for the products SKU instead. 
>
> I believe the modification to the name is taking place
> incartridge.models.ProductVariation file's __str__ method
> 
> but I've got no idea how I can modify this without causing issues with
> other parts of the site.
>
> What is my best option here?
> -- 
> 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] Run manage.py commands for mezzanine plugins (drum in this case)

[Ryne Everett]

Shouldn't you be calling the `manage.py` in your own project rather than
the template project? I'm not sure the template project itself is
actually a valid django project until it is used to generate a concrete
project. Regardless, you probably need to invoke `manage.py` from base
project directory (same directory `manage.py` is in).

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

[Ryne Everett]

I can't reproduce with a vanilla mezzanine site.

On 10/25/2016 12:08 AM, Akhlaq Rao wrote:
> As soon as I uncomment the mezzanine.accounts app I see the following
> error. Is this bug reported?
>
> django.urls.exceptions.NoReverseMatch: 'rest_framework' is not a
> registered namespace
>
> Unhandled exception in thread started by  check_errors..wrapper at 0x10951abf8>
> Traceback (most recent call last):
>   File
> "/Users/kashfey/Documents/Kash/Development/Webservice/mezzanine/couture92/lib/python3.5/site-packages/django/urls/base.py",
> line 77, in reverse
> extra, resolver = resolver.namespace_dict[ns]
> KeyError: 'rest_framework'
>
>   File
> "/Users/kashfey/Documents/Kash/Development/Webservice/mezzanine/couture92/lib/python3.5/site-packages/mezzanine/accounts/urls.py",
> line 29, in 
> url("^%s%s$" % (LOGIN_URL.strip("/"), _slash),
>   File
> "/Users/kashfey/Documents/Kash/Development/Webservice/mezzanine/couture92/lib/python3.5/site-packages/django/utils/functional.py",
> line 111, in __wrapper__
> res = func(*self.__args, **self.__kw)
>   File
> "/Users/kashfey/Documents/Kash/Development/Webservice/mezzanine/couture92/lib/python3.5/site-packages/django/urls/base.py",
> line 87, in reverse
> raise NoReverseMatch("%s is not a registered namespace" % key)
>
> django.urls.exceptions.NoReverseMatch: 'rest_framework' is not a
> registered namespace
> -- 
> 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] TypeError at /shop/invoice/#/

[Ryne Everett]

See https://github.com/stephenmcd/cartridge/pull/306. (Not yet released.)

On 10/24/2016 12:42 AM, Akhlaq Rao wrote:
>
>
>   I am seeing this error when clicking on the link on Order Complete page.
>
>
>   TypeError at /shop/invoice/4/
>
> dict expected at most 1 arguments, got 3
> Request Method:   GET
> Request URL:  https://couture92.com/shop/invoice/4/
> Django Version:   1.10.2
> Exception Type:   TypeError
> Exception Value:  
> dict expected at most 1 arguments, got 3
> Exception Location:
> /home/kash/workspace/environments/mez4venv/couture92/local/lib/python2.7/site-packages/django/template/context.py
> in __init__, line 18
> Python Executable:
> /home/kash/workspace/environments/mez4venv/couture92/bin/python
> Python Version:   2.7.12
>   
>
> -- 
> 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] Should I namespace for templates/ and static/ directories

[Ryne Everett]

I'm not too familiar with the "theme" pattern, but it seems like the point
of namespacing is that things can live together without namespace collision
and the point of themes is swappability. Presumably only one theme is
applicable at a time so collisions aren't a concern, and if you namespace
them they're not swappable.

On Tue, Oct 18, 2016 at 4:06 PM,  wrote:

>
> Is it a good practice to namespace* templates/ *and *static/* directories
> with app name for my two mezzanine apps: *theme1* and *theme2* ?
>
> For example, is it good idea to create template files like this:
> *theme1/templates/theme1/*.html*  and static files like this:
> *theme2/static/theme2/js/*.js*  ?
>
> I am only modifying the *base.html* and *index.html* in my theme;
> everything else is from default theme unchanged.  If I namespace
> *templates/* and *static/* directory for my *theme1* and *theme2* apps as
> above, what other changes do I have to make?
>
> --
> 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.core.middleware.SSLRedirectMiddleware Depricated 1600?

[Ryne Everett]

If you want your configuration to more closely resemble the default nginx
template you can uncomment those ssl lines and use the django ssl
middleware instead.

On Thu, Oct 13, 2016 at 11:33 AM, Akhlaq Rao <akhlaq@gmail.com> wrote:

> ok so nginx template for SSL entries no good anymore, were they directly
> connected to SSLRedirectMiddleWare?
>
> Thanks,
> A
>
>
>
> On Thu, Oct 13, 2016 11:23 AM, Ryne Everett ryneever...@gmail.com wrote:
>
>> SSLRedirectMiddleware would not solve that problem, all it does is
>> redirect to https.
>>
>> The way I handle this is having a line like ` return 301 
>> https://$host$request_uri;
>> ` in my server block listening on port 80, and another server block
>> listening on port 443 that actually proxies to django.
>>
>> On Thu, Oct 13, 2016 at 11:18 AM, Akhlaq Rao <akhlaq@gmail.com>
>> wrote:
>>
>> Hi Ryne,
>>
>> I totally get it, but if I do not use SSLRedirectMiddleware then I don't
>> see SSL Enable form in the Admin Settings. Do you know how do I enable SSL
>> without using SSLRedirectMiddleware? if I go to my frontend nginx all
>> the SSL related entries are commented out.
>>
>> server {
>>
>> listen 80;
>> # listen 443 ssl;
>> server_name shop.couture92.com shop.couture92.com.;
>> client_max_body_size 10M;
>> keepalive_timeout15;
>> error_log /home/admin/logs/couture92_error_nginx.log info;
>>
>> # ssl_certificate  conf/couture92.crt;
>> # ssl_certificate_key  conf/couture92.key;
>> # ssl_session_cacheshared:SSL:10m;
>> # ssl_session_timeout  10m;
>>
>>
>> Thanks, your help much appreciated.
>>
>>
>>
>> On Thu, Oct 13, 2016 10:44 AM, Ryne Everett ryneever...@gmail.com wrote:
>>
>> Whoops. I just pushed a fix for that bug.
>>
>> However, you still shouldn't be using that middleware. If you're going to
>> use an SSL middleware, use django's (https://docs.djangoproject.co
>> m/en/1.10/ref/middleware/#module-django.middleware.security). However,
>> my recommendation is to handle the redirect in the frontend server (nginx,
>> apache, etc) instead.
>>
>> On Thu, Oct 13, 2016 at 12:55 AM, Akhlaq Rao <akhlaq@gmail.com>
>> wrote:
>>
>> If it's deprecated then how do we enable SSL now? when I enable it I get
>> the following error:
>>
>> unhandled exception in thread started by > check_errors..wrapper at 0x10ff97950>
>> Traceback (most recent call last):
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/utils/autoreload.py",
>> line 226, in wrapper
>> fn(*args, **kwargs)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/mezzanine/core/man
>> agement/commands/runserver.py", line 163, in inner_run
>> super(Command, self).inner_run(*args, **kwargs)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/management/commands/runserver.py",
>> line 142, in inner_run
>> handler = self.get_handler(*args, **options)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/mezzanine/core/man
>> agement/commands/runserver.py", line 166, in get_handler
>> handler = super(Command, self).get_handler(*args, **options)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/contrib/sta
>> ticfiles/management/commands/runserver.py", line 27, in get_handler
>> handler = super(Command, self).get_handler(*args, **options)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/management/commands/runserver.py",
>> line 64, in get_handler
>> return get_internal_wsgi_application()
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/servers/basehttp.py",
>> line 46, in get_internal_wsgi_application
>> return get_wsgi_application()
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/wsgi.py", line 14,
>> in get_wsgi_application
>> return WSGIHandler()
>>   File "/Users/kashfey/Documents/Kash/Devel

Re: [mezzanine-users] mezzanine.core.middleware.SSLRedirectMiddleware Depricated 1600?

[Ryne Everett]

SSLRedirectMiddleware would not solve that problem, all it does is redirect
to https.

The way I handle this is having a line like ` return 301
https://$host$request_uri;
` in my server block listening on port 80, and another server block
listening on port 443 that actually proxies to django.

On Thu, Oct 13, 2016 at 11:18 AM, Akhlaq Rao <akhlaq@gmail.com> wrote:

> Hi Ryne,
>
> I totally get it, but if I do not use SSLRedirectMiddleware then I don't
> see SSL Enable form in the Admin Settings. Do you know how do I enable SSL
> without using SSLRedirectMiddleware? if I go to my frontend nginx all the
> SSL related entries are commented out.
>
> server {
>
> listen 80;
> # listen 443 ssl;
> server_name shop.couture92.com shop.couture92.com.;
> client_max_body_size 10M;
> keepalive_timeout15;
> error_log /home/admin/logs/couture92_error_nginx.log info;
>
> # ssl_certificate  conf/couture92.crt;
> # ssl_certificate_key  conf/couture92.key;
> # ssl_session_cacheshared:SSL:10m;
> # ssl_session_timeout  10m;
>
>
> Thanks, your help much appreciated.
>
>
>
> On Thu, Oct 13, 2016 10:44 AM, Ryne Everett ryneever...@gmail.com wrote:
>
>> Whoops. I just pushed a fix for that bug.
>>
>> However, you still shouldn't be using that middleware. If you're going to
>> use an SSL middleware, use django's (https://docs.djangoproject.
>> com/en/1.10/ref/middleware/#module-django.middleware.security). However,
>> my recommendation is to handle the redirect in the frontend server (nginx,
>> apache, etc) instead.
>>
>> On Thu, Oct 13, 2016 at 12:55 AM, Akhlaq Rao <akhlaq@gmail.com>
>> wrote:
>>
>> If it's deprecated then how do we enable SSL now? when I enable it I get
>> the following error:
>>
>> unhandled exception in thread started by > check_errors..wrapper at 0x10ff97950>
>> Traceback (most recent call last):
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/utils/autoreload.py",
>> line 226, in wrapper
>> fn(*args, **kwargs)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/mezzanine/core/
>> management/commands/runserver.py", line 163, in inner_run
>> super(Command, self).inner_run(*args, **kwargs)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/
>> management/commands/runserver.py", line 142, in inner_run
>> handler = self.get_handler(*args, **options)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/mezzanine/core/
>> management/commands/runserver.py", line 166, in get_handler
>> handler = super(Command, self).get_handler(*args, **options)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/contrib/
>> staticfiles/management/commands/runserver.py", line 27, in get_handler
>> handler = super(Command, self).get_handler(*args, **options)
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/
>> management/commands/runserver.py", line 64, in get_handler
>> return get_internal_wsgi_application()
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/servers/basehttp.py",
>> line 46, in get_internal_wsgi_application
>> return get_wsgi_application()
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/wsgi.py", line 14,
>> in get_wsgi_application
>> return WSGIHandler()
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/handlers/wsgi.py",
>> line 153, in __init__
>> self.load_middleware()
>>   File "/Users/kashfey/Documents/Kash/Development/Webservice/mezzan
>> ine/couture92/lib/python3.5/site-packages/django/core/handlers/base.py",
>> line 58, in load_middleware
>> mw_instance = mw_class()
>> TypeError: __init__() missing 1 required positional argument:
>> 'get_response'
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Mezzanine Users" group.
>> To unsubscribe f

Re: [mezzanine-users] I'm not able to install Cartridge

[Ryne Everett]

My recommendation is to `pip install html5lib<=0.999`. Although this is
pinned in bleach, in the context of installing from a requirements file
I've yet to see pip resolve it correctly.

On Thu, Oct 13, 2016 at 7:46 AM, Ken Bolton  wrote:

> Hi Ahmad,
>
> Can you show us what you tried? Saying, "it didn't work", is not an
> adequate request for assistance.
>
> It should be as simple as `pip uninstall html5` followed by `pip install
> bleach`.
>
> -ken
>
> On Thu, Oct 13, 2016 at 5:16 AM, ahmad almashni 
> wrote:
>
>> Hi , I tried to reinstall bleach but it didnt work ,
>> I don't know how to downgrade html5 library . can you tell me how please
>> thanks
>>
>> On Wednesday, October 12, 2016 at 3:50:43 PM UTC+3, Akhlaq Rao wrote:
>>>
>>> I had to reinstall bleach to downgrade html5 lib. I am not sure if it
>>> will solve your problem but it won't hurt to give it a try.
>>>
>>> pip install bleach
>>>
>>> A
>>>
>>> Sent from my iPhone
>>>
>>> On Oct 12, 2016, at 1:10 AM, ahmad almashni  wrote:
>>>
>>> Hi , It's already installed and it still doesn't work .
>>>
>>> On Tuesday, October 11, 2016 at 11:51:07 PM UTC+3, Akhlaq Rao wrote:

 try to install bleach.



 On Tue, Oct 11, 2016 8:53 AM, ahmad almashni ahma...@gmail.com wrote:

> Hello Everyone ,
> I've a problem installing cartridge inside a virtualenv
> I've installed Mezzanine and now inside a Mezzanine project I'm trying
> to install cartridge :
>
> pip install -U cartridge
>
>
>
> but an error rises every time :
>
>
> Using cashed html151lib-0.9.tar.gz
> complete output from command python setup.py egg_info:
> html151lib requires setuptools version 18.5 or above;
> please upgrade before installing ( you have 1.1.6)
>-
> command "python setup.py egg_info" faild with error code 1 in c:\users
> \ahmad\appdate\local\temp\pip-build\8zqfw9\html151lib\
>
> I've tried to update setup_tools but it doesn't get updated ...
> I need your help , 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.
>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to mezzanine-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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.core.middleware.SSLRedirectMiddleware Depricated 1600?

[Ryne Everett]

Whoops. I just pushed a fix for that bug.

However, you still shouldn't be using that middleware. If you're going to
use an SSL middleware, use django's (
https://docs.djangoproject.com/en/1.10/ref/middleware/#module-django.middleware.security).
However, my recommendation is to handle the redirect in the frontend server
(nginx, apache, etc) instead.

On Thu, Oct 13, 2016 at 12:55 AM, Akhlaq Rao  wrote:

> If it's deprecated then how do we enable SSL now? when I enable it I get
> the following error:
>
> unhandled exception in thread started by  check_errors..wrapper at 0x10ff97950>
> Traceback (most recent call last):
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/django/utils/autoreload.py",
> line 226, in wrapper
> fn(*args, **kwargs)
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/mezzanine/core/management/commands/runserver.py",
> line 163, in inner_run
> super(Command, self).inner_run(*args, **kwargs)
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/django/core/management/commands/runserver.py",
> line 142, in inner_run
> handler = self.get_handler(*args, **options)
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/mezzanine/core/management/commands/runserver.py",
> line 166, in get_handler
> handler = super(Command, self).get_handler(*args, **options)
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/
> django/contrib/staticfiles/management/commands/runserver.py", line 27, in
> get_handler
> handler = super(Command, self).get_handler(*args, **options)
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/django/core/management/commands/runserver.py",
> line 64, in get_handler
> return get_internal_wsgi_application()
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/
> django/core/servers/basehttp.py", line 46, in
> get_internal_wsgi_application
> return get_wsgi_application()
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/django/core/wsgi.py",
> line 14, in get_wsgi_application
> return WSGIHandler()
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/django/core/handlers/wsgi.py",
> line 153, in __init__
> self.load_middleware()
>   File "/Users/kashfey/Documents/Kash/Development/Webservice/
> mezzanine/couture92/lib/python3.5/site-packages/django/core/handlers/base.py",
> line 58, in load_middleware
> mw_instance = mw_class()
> TypeError: __init__() missing 1 required positional argument:
> 'get_response'
>
> --
> 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] Re: Search Results (Content Pages First)

[Ryne Everett]

I can't speak for everyone, but I only reply when I know more than the OP
about how to solve their problem than they do. If nobody replies it's
likely because nobody following the mailing list has done this.

If you don't know where to get started, look into how mezzanine's listing
order works currently. You may need to override the blog listing view and
modify the query in order to customize the ordering.

On Thu, Sep 22, 2016 at 11:39 AM, Chirag Dua  wrote:

> Can someone please reply/help?
>
>
> On Wednesday, September 21, 2016 at 4:06:45 PM UTC-4, Chirag Dua wrote:
>>
>> Is there a way to display content pages first and then all the blog posts
>> when someone searches with a keyword? I am assuming everything is combined
>> right now as per natural relevancy. I still want to retain that but within
>> blog posts and content pages separately.
>>
>> Is that feasible?
>>
>> Many 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.

Re: [mezzanine-users] More customized publishing workflow (Draft, Published...)

[Ryne Everett]

My question would be, is this setting actually sufficient for enabling more
complex workflows? An important component of workflows I've seen in other
frameworks is policies and enforcement. For instance, certain users are
privileged to approve changing the status of content from one stage to
another.

Right now, the content status represents a policy -- whether or not the
content is public.

It seems like the goal of your proposal is to also use content status as an
arbitrary label. If this is correct I would argue that this data is
different in kind and should therefore be in a different field. However,
perhaps this label field could serve as a "wrapper" around the status --
hiding the field in the admin and setting it based on it's own internal
logic.

On Tue, Sep 20, 2016 at 11:45 PM, Eduardo Rivas 
wrote:

> There's another person working on something like this here:
> https://github.com/stephenmcd/mezzanine/issues/411#issuecomment-235018090.
> You may want to check on that and unify efforts.
>
> One issue with your approach is that it will require a migration when a
> user adds a new choice. This will affect all models that subclass
> Displayable (pretty much everything). The developer will have to maintain
> the whole migration history separately or use one of the hacks for field
> injection. Not desirable IMO.
>
> Maybe we can define the choices in the form level instead of the model?
> That way the model field can be a non-choiced field while the dynamically
> generated choices are used in the form. That will still require a single
> migration but it can live in Mezzanine and be completely backwards
> compatible.
>
>
> --
> 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] gunicorn.conf gives ImportError: No module named wsgi

[Ryne Everett]

>
> If I pull out the contents out of nektra_coinfabrik/nektra_coinfabrik
> into /nektra_coinfabrik it somehow works but the admin is broken (cannot
> login, no styles).
>

That's because the path is wrong. Gunicorn is trying to import
`./nektra_coinfabrik/wsgi.py` from the current directory, but the correct
relative path is `./nektra_coinfabrik/nektra_coinfabrik/wsgi.py`. However,
simply changing the line to
`nektra_coinfabrik.nektra_coinfabrik.wsgi:application` probably wont work
because the outer nektra_coinfabrik directory is probably not a python
package and regardless your application probably depends on the package
directory being added to the python path. So I would try adding the to your
gunicorn flags
`--pythonpath="/home/david/nektra_coinfabrik/nektra_coinfabrik,"`.

As for the admin being broken, you're probably not doing anything to serve
static assets. The django development server does this by default but
you'll have to come up with your own solution in production. The ideal way
is to serve them with your production server (e.g., nginx, apache, etc.)
but the python package dj-static is probably sufficient to start with.

On Fri, Sep 16, 2016 at 3:21 PM,  wrote:

> Hi,
>
> I'm trying to run mezzanine on gunicorn, but cannot configure the
> gunicorn.conf file correctly, I tried to change the path to .sock and to
> wsgi:application without success.
>
> I get the error "ImportError: No module named wsgi". Gunicorn does't find
> the wsgi file.
>
> Development server works fine with nginx for static files.
>
> My file structure was created with the mezzanine-project command. It's a
> multi-tenancy project.
>
> If I pull out the contents out of nektra_coinfabrik/nektra_coinfabrik
> into /nektra_coinfabrik it somehow works but the admin is broken (cannot
> login, no styles).
>
> Is there a way to configure the gunicorn.conf so I don't have to change my
> file structure?
>
> Find attached files.
>
> Thanks!
>
> David
>
> --
> 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] Ryne Everett joins the core team

[Ryne Everett]

And the absurdity piles higher!
https://github.com/django/django/pulls?utf8=%E2%9C%93=author%3AAlexHill

On Wed, Sep 7, 2016 at 8:39 PM, Mario R. Osorio 
wrote:

> Long due ... Finally, someone who understands Django!
>
>
> ;)
>
> --
> 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] Ryne Everett joins the core team

[Ryne Everett]

Thanks Stephen.

It's funny that my name is tacked to the top of those ContentTyped PR's
when the majority of the work was done by Alex Hill (original
implementation, review, testing), yourself (review) and Josh Cartmell
(original implementation/review). They were shaped more by the feedback
than by the typist, but sometimes a typist is the only piece missing to
make a good idea succeed.

On Wed, Sep 7, 2016 at 4:18 PM, Stephen McDonald <st...@jupo.org> wrote:

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

-- 
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: Odd test database behaviour

[Ryne Everett]

You might look into what gets imported at init-time. I've run into this
before when modules that are imported when the app is initialized try to
access the database in global scope. Good luck.

On Tue, Sep 6, 2016 at 6:40 PM, Arti K  wrote:

> Hi,
>
> I am running into the same issue -
>
> django.db.utils.ProgrammingError: relation "pages_page" does not exist
>
>
> Could you let me know how you ended up sorting this ?
>
>
> I am so stuck on this and have been here for a week...
>
>
> Thanks for your help.
>
>
> Regards,
>
> Aarthi
>
> On Tuesday, January 6, 2015 at 11:11:48 PM UTC+1, Avery Laird wrote:
>>
>> Hello,
>>
>> I ran into an issue while trying to create a test database:
>>
>> django.db.utils.ProgrammingError: relation "pages_page" does not exist
>>
>> I have an theme app (called theme) that uses the mezzanine page model, so
>> I assume it must have something to do with that; sure enough, the top of
>> the traceback includes a failed SQL operation involving the table
>> theme_homepage,homepage being a model in my theme app that inherits from
>> mezzanine.pages.models.Page. To see if my hunch is correct, I change the
>> order of my installed apps to have mezzanine.pages before theme. Sure
>> enough, when running python manage.py test the error is now:
>>
>> django.db.utils.ProgrammingError: relation "pages_page" already exists
>>
>> I know there must be some overlap between apps causing the issue, one
>> which I fixed before by fiddling with south. The problem is, I can't fiddle
>> with a test database, and at any rate I would rather do things the right
>> way then have a fragile database. The models.py from theme is included
>> below:
>>
>> from django.db import models
>> from django.utils.translation import ugettext_lazy as _
>>
>>
>> from mezzanine.core.fields import FileField, RichTextField
>> from mezzanine.core.models import RichText, Orderable, Slugged
>> from mezzanine.pages.models import Page
>> from mezzanine.utils.models import upload_to
>>
>>
>> class HomePage(Page, RichText):
>> """
>> The homepage
>> """
>> header = models.CharField(max_length=140)
>> subheader = models.CharField(max_length=140)
>> splash = FileField(verbose_name=_("Splash Image"),
>> upload_to=upload_to("theme.HomePage.splash", "splash"),
>> format="Image", max_length=255, null=True, blank=True)
>>
>>
>> class Meta:
>> verbose_name = _("Home Page")
>> verbose_name_plural = _("Home Pages")
>>
>> class Slide(Orderable):
>> '''
>> Homepage slider images
>> '''
>> homepage = models.ForeignKey(HomePage, related_name="slides")
>> image = FileField(verbose_name=_("Image"),
>> upload_to=upload_to("theme.Slide.image", "slider"),
>> format="Image", max_length=255, null=True, blank=True)
>>
>>
>> class ExtendedBlog(Page, RichText):
>> """
>> RichText page, but with an optional splash image
>> """
>> splash = FileField(verbose_name=_("Splash Image"),
>> upload_to=upload_to("theme.ExtendedBlog.splash", "splash"),
>> format="Image", max_length=255, null=True, blank=True)
>>
>>
>> class Meta:
>> verbose_name = _("Extended Blog")
>> verbose_name_plural = _("Extended Blogs")
>>
>>
>> Thanks for any ideas/help!
>>
>> Cheers,
>>
>> Avery
>>
>>
>> --
> 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] Good sample Mezzanine site (with code) for learning forms processing

[Ryne Everett]

I don't think mezzanine plays any role here -- it's all vanilla django. You
can implement 1 & 2 with ModelForms
 and 3
with a generic ListView
.
I wouldn't look any further than the django docs for these tasks.

On Sat, Sep 3, 2016 at 11:44 AM, Rick9004  wrote:

>
> In looking for "how to" for form building with Mezzanine and Django I
> can't find a complete site that would allow me to de-construct how form
> processing is performed.  I mostly understand the various components but
> lack the overview of how they are put together. Specifically, I have a
> model Account that is in my PostgreSQL database.  I want to create a form
> that would allow users to 1) create a new account, 2) edit a current
> account and 3) list all accounts.  Do not want to use Mezzanine's admin for
> this.
> Can someone point me to any example code sites?  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.

Re: [mezzanine-users] Mezzanine 4.2.0 makes all tags as plain text in blog post.

[Ryne Everett]

Glad that solved your problem.

Perhaps being able to handle raw html intermingled with prose was a feature
we lost when we upgraded to tinymce4. It likely it can be re-enabled with
the correct tinymce configuration. (See
http://mezzanine.jupo.org/docs/configuration.html#tinymce-setup-js).

On Fri, Sep 2, 2016 at 12:20 AM, Alan Chen <alan.cheng...@gmail.com> wrote:

> Thanks for your clarification, it works using source code.
> I put the tags directly into tinymce like this in v3.1.10, and it works.
> Obviously it is not the story in v4.2.10.
>
> Thanks again, Ryne.
>
>
> 在 2016年9月2日星期五 UTC+8上午11:44:26，Ryne Everett写道：
>>
>> That is normal behavior. You can't put raw html directly into tinymce
>> like that. You need to click on the second to right button in the toolbar
>> ("<>") and put it in there or tinymce will treat it as plain text and wrap
>> it in additional html tags.
>>
>> On Thu, Sep 1, 2016 at 11:26 PM, Alan Chen <alan.c...@gmail.com> wrote:
>>
>>> Ryne, please check the enclosed screenshot, thanks.
>>>
>>> 在 2016年9月2日星期五 UTC+8上午10:40:42，Ryne Everett写道：
>>>>
>>>> Could you post a screenshot of what this bug looks like?
>>>>
>>>> On Thu, Sep 1, 2016 at 10:21 PM, Alan Chen <alan.c...@gmail.com> wrote:
>>>>
>>>>> Ryne, thanks for your reply.
>>>>>
>>>>> The tinymce shows up and all static files served normally. No errors
>>>>> shown in console.
>>>>> Both in my local debug environment (Python 2.7.9, Win7 64bit OS) and
>>>>> production (Python 2.7.6, Ubuntu 14, deployed by Apache + mod_wsgi) has 
>>>>> the
>>>>> same issue.
>>>>>
>>>>> Weird.
>>>>>
>>>>>
>>>>> 在 2016年9月1日星期四 UTC+8下午11:33:57，Ryne Everett写道：
>>>>>>
>>>>>> To make sure we're on the same page, the next steps were:
>>>>>> - python manage.py runserver
>>>>>> - navigate to admin and tinymce doesn't show up
>>>>>>
>>>>>> The out-of-the-box static files configuration has always worked fine
>>>>>> for me. I wonder if it could be a problem with the way your OS handles 
>>>>>> file
>>>>>> paths. What OS are you using? Also, are there any errors in either the
>>>>>> browser console or backend logs?
>>>>>>
>>>>>> On Thu, Sep 1, 2016 at 6:06 AM, Alan Chen <alan.c...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> the same after init a new project used Mezzanine 4.2.0
>>>>>>> - mezzanine-project testproject
>>>>>>> - python manage.py createdb --noinput
>>>>>>>
>>>>>>> Please help, thanks.
>>>>>>>
>>>>>>>
>>>>>>> 在 2016年9月1日星期四 UTC+8上午8:48:12，Stephen McDonald写道：
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Aug 31, 2016 at 5:22 PM, Alan Chen <alan.c...@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-use...@googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Mezzanine Users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to mezzanine-use...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[Ryne Everett]

That is normal behavior. You can't put raw html directly into tinymce like
that. You need to click on the second to right button in the toolbar ("<>")
and put it in there or tinymce will treat it as plain text and wrap it in
additional html tags.

On Thu, Sep 1, 2016 at 11:26 PM, Alan Chen <alan.cheng...@gmail.com> wrote:

> Ryne, please check the enclosed screenshot, thanks.
>
> 在 2016年9月2日星期五 UTC+8上午10:40:42，Ryne Everett写道：
>>
>> Could you post a screenshot of what this bug looks like?
>>
>> On Thu, Sep 1, 2016 at 10:21 PM, Alan Chen <alan.c...@gmail.com> wrote:
>>
>>> Ryne, thanks for your reply.
>>>
>>> The tinymce shows up and all static files served normally. No errors
>>> shown in console.
>>> Both in my local debug environment (Python 2.7.9, Win7 64bit OS) and
>>> production (Python 2.7.6, Ubuntu 14, deployed by Apache + mod_wsgi) has the
>>> same issue.
>>>
>>> Weird.
>>>
>>>
>>> 在 2016年9月1日星期四 UTC+8下午11:33:57，Ryne Everett写道：
>>>>
>>>> To make sure we're on the same page, the next steps were:
>>>> - python manage.py runserver
>>>> - navigate to admin and tinymce doesn't show up
>>>>
>>>> The out-of-the-box static files configuration has always worked fine
>>>> for me. I wonder if it could be a problem with the way your OS handles file
>>>> paths. What OS are you using? Also, are there any errors in either the
>>>> browser console or backend logs?
>>>>
>>>> On Thu, Sep 1, 2016 at 6:06 AM, Alan Chen <alan.c...@gmail.com> wrote:
>>>>
>>>>> the same after init a new project used Mezzanine 4.2.0
>>>>> - mezzanine-project testproject
>>>>> - python manage.py createdb --noinput
>>>>>
>>>>> Please help, thanks.
>>>>>
>>>>>
>>>>> 在 2016年9月1日星期四 UTC+8上午8:48:12，Stephen McDonald写道：
>>>>>>
>>>>>>
>>>>>> On Wed, Aug 31, 2016 at 5:22 PM, Alan Chen <alan.c...@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-use...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[Ryne Everett]

Could you post a screenshot of what this bug looks like?

On Thu, Sep 1, 2016 at 10:21 PM, Alan Chen <alan.cheng...@gmail.com> wrote:

> Ryne, thanks for your reply.
>
> The tinymce shows up and all static files served normally. No errors shown
> in console.
> Both in my local debug environment (Python 2.7.9, Win7 64bit OS) and
> production (Python 2.7.6, Ubuntu 14, deployed by Apache + mod_wsgi) has the
> same issue.
>
> Weird.
>
>
> 在 2016年9月1日星期四 UTC+8下午11:33:57，Ryne Everett写道：
>>
>> To make sure we're on the same page, the next steps were:
>> - python manage.py runserver
>> - navigate to admin and tinymce doesn't show up
>>
>> The out-of-the-box static files configuration has always worked fine for
>> me. I wonder if it could be a problem with the way your OS handles file
>> paths. What OS are you using? Also, are there any errors in either the
>> browser console or backend logs?
>>
>> On Thu, Sep 1, 2016 at 6:06 AM, Alan Chen <alan.c...@gmail.com> wrote:
>>
>>> the same after init a new project used Mezzanine 4.2.0
>>> - mezzanine-project testproject
>>> - python manage.py createdb --noinput
>>>
>>> Please help, thanks.
>>>
>>>
>>> 在 2016年9月1日星期四 UTC+8上午8:48:12，Stephen McDonald写道：
>>>>
>>>>
>>>> On Wed, Aug 31, 2016 at 5:22 PM, Alan Chen <alan.c...@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-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[Ryne Everett]

To make sure we're on the same page, the next steps were:
- python manage.py runserver
- navigate to admin and tinymce doesn't show up

The out-of-the-box static files configuration has always worked fine for
me. I wonder if it could be a problem with the way your OS handles file
paths. What OS are you using? Also, are there any errors in either the
browser console or backend logs?

On Thu, Sep 1, 2016 at 6:06 AM, Alan Chen  wrote:

> the same after init a new project used Mezzanine 4.2.0
> - mezzanine-project testproject
> - python manage.py createdb --noinput
>
> Please help, thanks.
>
>
> 在 2016年9月1日星期四 UTC+8上午8:48:12，Stephen McDonald写道：
>>
>>
>> On Wed, Aug 31, 2016 at 5:22 PM, Alan Chen  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.
>

-- 
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] Save Button In Blog Post and Everything That Involves Tinymce Not Working

[Ryne Everett]

This isn't nearly enough information for anyone to be able to help you.
What are "various fixes"? Is this in a development or production
environment? Are there any errors in the browser console or backend logs?

On Thu, Sep 1, 2016 at 4:55 AM, Leke Okumoyinbo 
wrote:

>  Python == 2.7
> Django == 1.10
> Mezzanine == 4.2.0
>
> Please, what can I do to correct this problem? I applied various fixes to
> Mezzanine, then i couldn't save blog posts and anything that involves the
> Tinymce widget any longer. 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.
>

-- 
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 translate field injection

[Ryne Everett]

I'm pretty ignorant about translation but it seems like the migration
triggered by the extra field would be relevant.

On Sun, Aug 28, 2016 at 8:58 AM, Cajoline  wrote:

> Hi,
>
> I try to translate a field injection for the model Page, but i have an
> exception "FieldDoesNotExist",
> I read the documentation and i have created an application that i have
> inserted in settings before "mezzanine.pages",
>
>
> My Gist:
> https://gist.github.com/Cajoline/1b074ac83c9ab61f57102bee4d8dc2f7
>
> 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.
>

-- 
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] Send email on new page creation or blogpost using Mezzanine

[Ryne Everett]

You could start by writing a function that just prints something to the
console. Then connect it with the post_save signal (and the Page sender).

I find the signals documentation and terminology difficult to interpret
myself but you should be able to figure it out by mimicking the examples.

On Fri, Aug 5, 2016 at 10:30 AM, Michael Ketiku <mket...@gmail.com> wrote:

> Thanks, I really don't even know where to start and to be honest I am
> confused but thanks anyways.
>
> On Thursday, August 4, 2016 at 9:52:38 PM UTC-4, Ryne Everett wrote:
>>
>> There are probably a lot of different approaches to this but the first
>> one that comes to mind is django signals
>> <https://docs.djangoproject.com/en/stable/topics/signals/>. You could
>> listen to the post-save signal
>> <https://docs.djangoproject.com/en/stable/ref/signals/#post-save> on the
>> Page model and have your handler check if the page is published (and you
>> probably want to make sure it's the first time it's been published) and if
>> so dispatch your emails.
>>
>> It would be great if you implemented this as a reusable app
>> <https://docs.djangoproject.com/en/stable/intro/reusable-apps/> and
>> shared it with the mezzanine community because it seems like a common
>> blogging-platform feature which we lack. This would also enable us to be
>> more helpful should you run into difficulties because we could see your
>> code.
>>
>> On Thu, Aug 4, 2016 at 6:15 PM, Michael Ketiku <mke...@gmail.com> wrote:
>>
>>> Hi everyone, I am a beginning Django developer and I am working with
>>> Mezzanine on my first application. As part of that I would like to find out
>>> how to send an email message to all users of a mezzanine site when a new
>>> page or blog post is created. I looked all through the mezzanine docs but
>>> can not find anything regarding this. Please point me in the right
>>> direction, I have looked at django-alerts and django-notifier but can not
>>> understand how to send emails to users like that.
>>>
>>> Thanks-
>>> Michael
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] wrong base.html

[Ryne Everett]

>
> This is a common pattern in Django, but I couldn't find any documentation
> that supports it. Hopefully someone else can reference a reputable source
> that explains it.


The django tutorial
 has a section
on "Template namespacing". There's a similar section on "Static file
namespacing" in part 6.

On Mon, Aug 1, 2016 at 7:56 PM, Eduardo Rivas 
wrote:

> Django templates don't work with absolute paths (or if they do, it's not a
> good idea for portability). The templates you want to refer to in {%
> extends %} are relative to the templates/ directory in each installed app.
>
> Since all templates/ directories from all apps are combined into one
> "pool", you should always reuse the application name inside the templates/
> folder. For example, for your nektra template, the base.html file should be
> at nektra/templates/nektra/base.html. And then you can extend it with {%
> extends "nektra/base.html" %}.
>
> The same goes for your coinfabrik application. The base template should be
> in coinfabrik/templates/coinfabrik/base.html, and you can then reference it
> in templates as "coinfabrik/base.html".
>
> This is a common pattern in Django, but I couldn't find any documentation
> that supports it. Hopefully someone else can reference a reputable source
> that explains it.
>
>
>
> --
> 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] Blog category hangs

[Ryne Everett]

Another possibility would be that you have postmortem breakpoints enabled
somehow and the line in the traceback is triggering an exception. This
doesn't seem likely to happen by accident though.

How are you invoking the development server? The screenshot doesn't include
the fancy mezzanine ascii art and it doesn't look like the one provided by
django-extensions either.

On Mon, Aug 1, 2016 at 2:34 AM, Bojan Kogoj <bojan.ko...@gmail.com> wrote:

> I did a force reinstall, but it still doesn't work. I haven't set any
> breakpoints, neither do I know how to in django. Any more ideas?
>
> On Friday, July 29, 2016 at 3:34:30 PM UTC+2, Ryne Everett wrote:
>>
>> You have a breakpoint at line 30 in mezzanine/blog/views.py which is
>> blocking indefinitely as is to be expected. Upgrading to any mezzanine
>> release should fix this, e.g., `pip install -U mezzanine`.
>>
>> On Fri, Jul 29, 2016 at 3:43 AM, Bojan Kogoj <bojan...@gmail.com> wrote:
>>
>>> Sometimes without any reason, it hangs and won't load.
>>>
>>> [image: screen shot 2016-07-28 at 16 39 24]
>>> <https://cloud.githubusercontent.com/assets/634075/17216688/f3e467a6-54e1-11e6-93b2-3e7bfa70488f.png>
>>>
>>> That is the only thing I get from it, no errors or anything else,
>>> browser has a spinning circle as if it is loading
>>> If I try to wget I get this:
>>>
>>>
>>> vagrant@vagrant-ubuntu-trusty-64:~$ wget localhost:8000/blog/category/
>>> food/ --2016-07-28 14:43:36-- http://localhost:8000/blog/category/food/
>>> Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost
>>> (localhost)|127.0.0.1|:8000... connected. HTTP request sent, awaiting
>>> response...
>>>
>>> I already asked on StackOverflow
>>> <http://stackoverflow.com/questions/38565786/mezzanine-blog-category-freezing>
>>> with no luck
>>>
>>> Anyone has an idea why this is happening? Comes and goes with no
>>> apparent reason.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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: Sending emails from a contact form

[Ryne Everett]

Assuming you're actually dealing with a mezzanine site (and not a different
product with the same name) there is no way to access the console or
install things from the admin -- you need access to the server. To some
this is an inconvenience and to others (myself included) an essential
security property.

I don't think there's anything we're going to be able to do to help you
unless you have ssh access to the server.

On Mon, Aug 1, 2016 at 1:23 AM,  wrote:

> So in the top left it says Mezzanine and the company who gave us this site
> is called LIFT.
>
> On Sunday, 31 July 2016 18:47:43 UTC-7, o.tr...@share.epsb.ca wrote:
>
>> I am a non programmer and I have a small site in development. And one of
>> the things I need is for the contact form to send emails automatically when
>> someone fill the form out and hits submit. I tried many ways like PHP and
>> others but no luck. I do not know how to program. Can someone please
>> provide a guide or tips in simple language, so I can finally get it
>> working. Any help is appreciated.
>>
>> p.s. I figured out a way for the form to send the email, but it needs to
>> open my outlook to send it. I need something that does not need a mailing
>> program to work.
>>
> --
> 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] Re: Sending emails from a contact form

[Ryne Everett]

What site are you using?

On Mon, Aug 1, 2016 at 12:52 AM,  wrote:

> I did not start it from the console, when I launch mezzanine I just go to
> a generic side building page.
>
> On Sunday, 31 July 2016 18:47:43 UTC-7, o.tr...@share.epsb.ca wrote:
>
>> I am a non programmer and I have a small site in development. And one of
>> the things I need is for the contact form to send emails automatically when
>> someone fill the form out and hits submit. I tried many ways like PHP and
>> others but no luck. I do not know how to program. Can someone please
>> provide a guide or tips in simple language, so I can finally get it
>> working. Any help is appreciated.
>>
>> p.s. I figured out a way for the form to send the email, but it needs to
>> open my outlook to send it. I need something that does not need a mailing
>> program to work.
>>
> --
> 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] Re: Sending emails from a contact form

[Ryne Everett]

Installation instructions are right on the page I linked. (
https://github.com/anymail/django-anymail#anymail-1-2-3). Not sure what you
mean about finding the console. Didn't you start mezzanine from the console
in the first place?

On Sun, Jul 31, 2016 at 11:38 PM,  wrote:

> Can you please explain where can I find the console to type everything I
> need to? Like installation commands?
>
>
> On Sunday, 31 July 2016 18:47:43 UTC-7, o.tr...@share.epsb.ca wrote:
>>
>> I am a non programmer and I have a small site in development. And one of
>> the things I need is for the contact form to send emails automatically when
>> someone fill the form out and hits submit. I tried many ways like PHP and
>> others but no luck. I do not know how to program. Can someone please
>> provide a guide or tips in simple language, so I can finally get it
>> working. Any help is appreciated.
>>
>> p.s. I figured out a way for the form to send the email, but it needs to
>> open my outlook to send it. I need something that does not need a mailing
>> program to work.
>>
> --
> 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] Sending emails from a contact form

[Ryne Everett]

Check out django-anymail  for a
pretty straightforward way of using a few mailing services.

On Sun, Jul 31, 2016 at 9:34 PM,  wrote:

> I am a non programmer and I have a small site in development. And one of
> the things I need is for the contact form to send emails automatically when
> someone fill the form out and hits submit. I tried many ways like PHP and
> others but no luck. I do not know how to program. Can someone please
> provide a guide or tips in simple language, so I can finally get it
> working. Any help is appreciated.
>
> p.s. I figured out a way for the form to send the email, but it needs to
> open my outlook to send it. I need something that does not need a mailing
> program to work.
>
> --
> 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] Re: UnicodeDecodeError: 'locale' codec can't decode byte 0xe2 in position 0: Invalid or incomplete multi

[Ryne Everett]

Iain, I don't think the filename issue is related to the OP's issue, but
you might find this PR relevant:
https://github.com/stephenmcd/mezzanine/pull/1609.

On Sun, Jul 31, 2016 at 11:33 AM, Iain Mac Donald <
mezzan...@picturenow.co.uk> wrote:

>
> You don't have the sample data installed, do you?
>
> I had an error message similar to that which I thought should have been
> resolved by setting:
> SHOP_CURRENCY_LOCALE = 'en_GB.utf8'
>
> but actually there was still a problem with the encoding of the
> files/filenames of the sample gallery. I deleted that gallery and
> everything was fine.
>
> --
>
> Regards,
> Iain.
>
> --
> 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] Blog category hangs

[Ryne Everett]

You have a breakpoint at line 30 in mezzanine/blog/views.py which is
blocking indefinitely as is to be expected. Upgrading to any mezzanine
release should fix this, e.g., `pip install -U mezzanine`.

On Fri, Jul 29, 2016 at 3:43 AM, Bojan Kogoj  wrote:

> Sometimes without any reason, it hangs and won't load.
>
> [image: screen shot 2016-07-28 at 16 39 24]
> 
>
> That is the only thing I get from it, no errors or anything else, browser
> has a spinning circle as if it is loading
> If I try to wget I get this:
>
>
> vagrant@vagrant-ubuntu-trusty-64:~$ wget localhost:8000/blog/category/food
> / --2016-07-28 14:43:36-- http://localhost:8000/blog/category/food/
> Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost
> (localhost)|127.0.0.1|:8000... connected. HTTP request sent, awaiting
> response...
>
> I already asked on StackOverflow
> 
> with no luck
>
> Anyone has an idea why this is happening? Comes and goes with no apparent
> reason.
>
>
> --
> 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] What does this mean in urls.py " and specify its URL (in the Meta Data section) " ?

[Ryne Everett]

I think the part you're asking about is:

specify its URL (in the Meta Data section) as "/"
>

This does not refer to the `Meta` class, it refers to the `slug` field
which `Page` inherits from `mezzanine.core.models.Slugged`. That line could
likely be clarified a bit.

On Mon, Jul 25, 2016 at 3:25 AM, nikhil parmar  wrote:

> Hey guys,
>
> What does the above line signify ? # This pattern gives us a normal
>>> ``Page`` object, so that your
>>
>> # homepage can be managed via the page tree in the admin. If you
>> # use this pattern, you'll need to create a page in the page tree,
>> # and specify its URL (in the Meta Data section) as "/", which
>> # is the value used below in the ``{"slug": "/"}`` part.
>> # Also note that the normal rule of adding a custom
>> # template per page with the template name using the page's slug
>> # doesn't apply here, since we can't have a template called
>> # "/.html" - so for this case, the template "pages/index.html"
>> # should be used if you want to customize the homepage's template.
>> # NOTE: Don't forget to import the view function too!
>>
>>
>
>
>> url("^$", "mezzanine.pages.views.page", {"slug": "/"}, name="home"),
>>
>>
>
> If I have a theme and its homepage is like -
>
> class HomePage(Page, RichText):
> '''
> A page representing the format of the home page
> '''
> heading = models.CharField(_("Heading"), max_length=200,
> default=_("Hello, world!"),
> help_text=_("The heading under the icon blurbs"))
> subheading = models.CharField(_("Subheading"), max_length=1000,
> default=_("This is a template for a simple marketing or "\
> "informational website. It includes a large callout called "\
> "a jumbotron and three supporting pieces of content. Use it "\
> "as a starting point to create something more unique."),
> help_text=_("The subheading just below the heading"))
> heading_button = models.CharField(_("Button text"), max_length=200,
> default=_("Learn more"))
> heading_link = models.CharField(_("Button link"), max_length=200,
> blank=True, default=_("#"),
> help_text=_("Optional, if provided the heading button will be 
> visible."))
> iconbox_heading = models.CharField(_("Iconbox heading"), max_length=200,
> null=True, blank=True,
> help_text=_("Optional, if provided the iconbox heading will be 
> visible."))
> content_heading = models.CharField(_("Content heading"), max_length=200,
> default=_("About us"))
>
> class Meta:
> verbose_name = _("Home page")
>
> verbose_name_plural = _("Home pages")
>
>
>
> Do I need to declare the "/" url in the Meta class of homepage?
>
> --
> 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] install Cartridge 0.11.0 on windows (via cygwin)

[Ryne Everett]

As for issue (2) you need to downgrade to html5lib<=0.999. This is
pinned in bleach so I'm not sure why it wasn't constrained. (I had this
problem too.) You can fix it with `pip install -U bleach`.

On Thu, Jul 21, 2016 at 8:31 PM, Alain Turcotte 
wrote:

> I am trying to install Cartridge 0.11.0 on windows (via cygwin), and i
> have 2 bugs:
>
>
> 1)
>
> "mezzanine-project -a cartridge atcart" give me the error :
>
> CommandError: 'atcart' conflicts with the name of an existing Python
> module and cannot be used as a project name. Please try another name.
>
>
>
> 2)
>
> "python manage.py createdb --noinput" give me the error :
>
> erreur : No module named 'html5lib.sanitizer'
>
>
>
> the source of the problem is in the package "bleach" , in the __init__.py
> :
>
> import html5lib
>
> from html5lib.sanitizer import HTMLSanitizer
>
>
>
> any suggestion ?
>
>
>
> --
> 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] Need some help with assigning user site permission in a view

[Ryne Everett]

Ah, that makes sense. I guess you can't pass ManyToManyField's in the
constructor. Try:

siteperms = SitePermissions.objects.create(user=user)
siteperms.sites.add(site)

On Thu, Jul 21, 2016 at 5:15 PM, zruu <usr1...@gmail.com> wrote:

> Hi Ryne,
>
> Thanks for the quick reply. That was what I was looking for. I have a form
> on the front end that a user can create a site, and a user account at the
> same time. I want to automate this to minimize the administration as
> possible.
>
> However I tried that, and I got the error:
>
> 'sites' is an invalid keyword argument for this function
>
>
>
> Den torsdag 21 juli 2016 kl. 23:07:40 UTC+2 skrev Ryne Everett:
>>
>> SitePermission.objects.create(user=user, sites=(site,))
>>
>> I question whether this is really what you want to do, but without a
>> better idea what your goal is it's all I can offer.
>>
>> On Thu, Jul 21, 2016 at 4:56 PM, zruu <usr...@gmail.com> wrote:
>>
>>> Hey guys,
>>>
>>> I really need your help. I'm stuck at the moment. Maybe is too late.
>>> However. I need to in my class view add site permission instead of using
>>> through the admin. I have no clue how to do this.
>>>
>>> I looked through the Mezzanine code and all I found was this piece of
>>> code that looks something of value:
>>>
>>> sites = user.sitepermissions.sites.all()
>>>
>>> *What I want to accomplish is to first to create the site object in my
>>> view:*
>>>
>>> site = Site.objects.create(name=name, domain=domain)
>>>
>>> Then set permission for my user to that site. How could I do this?
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] Need some help with assigning user site permission in a view

[Ryne Everett]

SitePermission.objects.create(user=user, sites=(site,))

I question whether this is really what you want to do, but without a better
idea what your goal is it's all I can offer.

On Thu, Jul 21, 2016 at 4:56 PM, zruu  wrote:

> Hey guys,
>
> I really need your help. I'm stuck at the moment. Maybe is too late.
> However. I need to in my class view add site permission instead of using
> through the admin. I have no clue how to do this.
>
> I looked through the Mezzanine code and all I found was this piece of code
> that looks something of value:
>
> sites = user.sitepermissions.sites.all()
>
> *What I want to accomplish is to first to create the site object in my
> view:*
>
> site = Site.objects.create(name=name, domain=domain)
>
> Then set permission for my user to that site. How could I do this?
>
>
>
> --
> 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] Bad Gateway

[Ryne Everett]

A couple causes of gunicorn timeouts I've seen is larger files that don't
transfer within the default --timeout (30 seconds). This isn't necessarily
your problem but if it is you can increase the timeout. I've also seen it
when streaming files, in which case the solution is to make the workers
asynchronous (-k gevent). Going from memory here so no promises.

On Thu, Jul 21, 2016 at 12:08 PM, loevdav 
wrote:

> Hi Ken,
>
> Thanks.
>
> Yes I can but I'm not sure where do you want to get because the issuet
> happens on different sites and on different actions (sometimes just loading
> the home page and other time isnide the admin).
>
> I have been looking on the web and it looks like some people solved it by
> increasing the number of workers for gunicorn. But these sites have very
> very  low traffic and do not have any complex queries or operations.
>
> The more complex sites are on a server of their own and I have no issue.
>
> Anyway thanks and let me know what you want to try with runserver.
>
> Thanks
> David
>
>
> On Thursday, July 21, 2016 at 4:16:39 PM UTC+2, Kenneth Bolton wrote:
>>
>> Are you able to use the django runserver? It is very hard for me to tell
>> where the problem might be, so I would step through each piece until I find
>> the root cause, starting with the django runserver.
>>
>> hth,
>>
>> ken
>>
>> On Thu, Jul 21, 2016 at 6:06 AM, loevdav  wrote:
>>
>>> Hi Ken,
>>>
>>> Thanks a lot for the reply:
>>>
>>> Here are the logs:
>>>
>>>
>>> *Error log*
>>>
>>> [2016-07-01 10:30:43 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:1105)
>>> [2016-07-01 10:30:49 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:6783)
>>> [2016-07-01 10:35:53 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:7129)
>>> [2016-07-01 10:41:32 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:7317)
>>> [2016-07-01 11:25:37 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:7802)
>>> [2016-07-01 11:30:44 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:8969)
>>> [2016-07-01 12:45:47 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:11499)
>>> [2016-07-01 15:25:46 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:17183)
>>> [2016-07-01 15:30:43 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:17363)
>>> [2016-07-06 23:00:35 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:27959)
>>> [2016-07-08 09:25:56 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:13078)
>>> [2016-07-08 09:30:50 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:13287)
>>> [2016-07-08 09:40:54 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:13675)
>>> [2016-07-08 09:45:52 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:13876)
>>> [2016-07-08 10:45:47 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:14081)
>>> [2016-07-08 10:55:52 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:16225)
>>> [2016-07-13 11:05:51 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:23348)
>>> [2016-07-13 11:15:53 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:24537)
>>> [2016-07-13 11:20:47 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:24786)
>>> [2016-07-13 12:00:47 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:28216)
>>> [2016-07-15 12:30:44 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:29462)
>>> [2016-07-20 12:05:40 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:19347)
>>> [2016-07-20 12:35:37 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:25708)
>>> [2016-07-20 12:55:42 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:30319)
>>> [2016-07-21 09:10:45 +] [3496] [CRITICAL] WORKER TIMEOUT (pid:15845)
>>>
>>>
>>> *nginx error log*
>>>
>>> 2016/04/27 21:17:00 [info] 30913#0: *266 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30913#0: *268 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *270 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *272 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *274 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *276 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *278 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *280 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:00 [info] 30912#0: *282 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:42 [info] 30912#0: *295 client 79.44.98.211 closed
>>> keepalive connection
>>> 2016/04/27 21:17:42 [info] 30912#0: *301 client 79.44.98.211 closed
>>> keepalive connection
>>>
>>> *Supervisor log*
>>>
>>> /home/mars/.virtualenvs/domus/local/lib/python2.7/site-packages/mezzanine/pages/templatetags/pages_tags.py:134:
>>> RemovedInDjango110Warning: render() must be called with a dict, not a
>>> Context.
>>>   return t.render(Context(context))
>>>
>>> /home/mars/.virtualenvs/domus/local/lib/python2.7/site-packages/django/template/defaulttags.py:499:
>>> RemovedInDjango110Warning: Reversing by 

Re: [mezzanine-users] tel: being stripped from anchor href when saving a RichTextField. How do I allow it?

[Ryne Everett]

You may just need to upgrade to 4.1.0. See
https://github.com/stephenmcd/mezzanine/pull/1473.

On Wed, Jul 20, 2016 at 10:18 PM, RandomDude  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.
>

-- 
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] Where are the migration files for mezzanine's built-in apps?

[Ryne Everett]

The migrations for mezzanine's apps reside in the source code. Unless you
modified mezzanine's models (e.g., with the `EXTRA_MODEL_FIELDS` setting),
you wont cause migrations to mezzanine's apps.

On Tue, Jul 19, 2016 at 7:52 AM, Keith Irwin  wrote:

> Hopefully this is an easy question for somebody in the loop.
>
> I seem to have fudged my schemas by creating a new app.  It's giving me a
> type error, so maybe I forgot to turn off MODELTRANSLATION before executing
> makemigrations/migrate.
>
> I just want to revert to the state I was in before the app existed.
> Fortunately, I was smart enough to keep a second copy of my dev.db, which I
> restored.
>
> So I use runserver with the restored dev.db and my project runs fine, data
> and all, just like before.  However, I get the traditional message "You
> have unapplied migrations"
>
> I run showmigrations and get a neat list of applied and unapplied
> migrations.  I want to delete all these unapplied migrations, returning
> (undoing makemigrations) to the state of the restored db.  In my own apps,
> I can just delete the unapplied migrations/*.py files.  But what about
> mezzanine's built-in apps (blog, pages, etc)  How do I delete those
> migrations.
>
> In other words, I know how to unapply migrations (manage.py migrate
> appname 000#), but how do I unmake the unapplied migrations?
>
> I haven't found any answers googling, so it's possible that I completely
> misunderstand how migrations/dbs work...
>
> --
> 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 Theme

[Ryne Everett]

Did you put the django wiki's urlpatterns before mezzanine's? A common
pitfall is that mezzanine eats any url pattern so it must be last.

On Mon, Jul 18, 2016 at 3:47 PM, Richard  wrote:

> Hi,
> Thank you for your advice on that. I'm trying to use the Django-Wiki,
> a general wiki app for Django. I was able to configure to use with the
> Mezzanine cms, but i have issues creating a new article.
> " *This slug conflicts with an existing URL.*
>
> This will be the address where your article can be found. Use only
> alphanumeric characters and - or _. Note that you cannot change the slug
> after creating the article."
>
> I'm trying to figure out why there is a conflict even if i provide some
> random name. It's not even picking a single slug. Hopefully i should be
> able to come out with a solution.
>
>
> Thank you,
>
> Richard.
>
>
>
> On Thursday, July 14, 2016 at 8:36:31 AM UTC-5, Eduardo Rivas wrote:
>>
>> It looks like the wiki hasn't been updated since 2014. You will need to
>> find and install the version of Mezzanine that was current at that time
>> (I think Mezzanine 3.1 + Django 1.6). You could try to update it to
>> support later versions of Django and Mezzanine too.
>>
>> Another approach is to look for a wiki solution for Django in general,
>> not Mezzanine specifically. A project like that might be more active.
>>
> --
> 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] Drum auto tags issue.

[Ryne Everett]

>
> Is there any best practise to setup a development environment? Or just run
> `python setup.py install` each time after I change the source code.


Use `python setup.py develop` (
http://setuptools.readthedocs.io/en/latest/setuptools.html?#development-mode)
or `pip install -e ` (
https://pip.pypa.io/en/stable/reference/pip_install/#editable-installs).

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

> You are great! I have forked drum and plan to do some modifications.
>
> Is there any best practise to setup a development environment? Or just run
> `python setup.py install` each time after I change the source code.
>
>
> On Fri, Jul 15, 2016 at 1:20 PM Stephen McDonald  wrote:
>
>> 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:
>
>>

Re: [mezzanine-users] Completely Remove Shipping From Cartridge.

[Ryne Everett]

You might consider the alternative approach of overriding the checkout
views, making the shipping fields HiddenInput fields, and setting their
default value to zero. The benefits of doing it this way are you wouldn't
have to modify the templates and you wouldn't have to override the form
validation.

I don't think anyone's going to be able to give you a more specific answer
unless you include a traceback for your KeyError.

On Fri, Jul 8, 2016 at 4:10 PM, Andrew Fulton  wrote:

> How would i go about completely removing shipping from cartridge? I have
> everything to do with shipping removed from the templates, I popped all the
> fields in my CustomOrderForm, but yet on the last step of the checkout
> (confirmation page) when i click next, i get a keyError on
> 'shipping_detail_first_name' which i assume means that that field is
> null/was never filed out. How do i get around that? Is there some other
> method/class i need to override?
>
> My CustomOrderForm class:
>
> class CustomOrderForm(BraintreeOrderForm):
>
>
> def __init__(self, *args, **kwargs):
> super(CustomOrderForm, self).__init__(*args, **kwargs)
> self.fields.pop('additional_instructions')
> self.fields.pop('same_billing_shipping')
> self.fields.pop('remember')
> for field in BraintreeOrderForm._meta.fields:
> if(field.startswith('shipping')):
> self.fields.pop(field)
>
> --
> 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] React Mezzanine project starter kit

[Ryne Everett]

Something I've been meaning to try out for a while is contributor Alex
Hill's djpj project: https://github.com/AlexHill/djpj. I'm assuming he uses
it with mezzanine projects and if page load performance is your primary
concern it may be an alternative solution.

On Sun, Jun 19, 2016 at 5:21 PM, Niels Jakob Buch  wrote:

> Hi there, I am working on a front-end that has become annoying because of
> too many page loads and has decided to move into using ReactJS.
>
> Anyone has experiences to share with Mezzanine (not only Django) on this
> topic?
>
> --
> 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] monkey patch a function?

[Ryne Everett]

>
> Thanks for the great suggestion and helpful example!


You're welcome.

Do you have any suggestion regarding adding extra step into the checkout
> process? Like when the user clicks on the product, select the quantity and
> sizes, then there is a "Next" button to let the user continue adding more
> customization to the selected product.


Here's a couple ideas that come to mind.

   1. *Override the checkout_steps view just like you are the product view.*
   I dislike this approach because it's a lengthy, complex view you'll have to
   maintain and maintain compatibility with cartridge.
   2. *Use a custom product model and add the necessary fields to the
   product.* This functionality hasn't been merged in yet, but I'm pretty
   sure it will be. See https://github.com/stephenmcd/cartridge/pull/293.
   I'd be a little hesitant to put this into production in this development
   state, but if you can wait a few weeks or months it will be a much more
   maintainable solution in the long run.


On Thu, Jun 16, 2016 at 5:50 PM, Tran <nhantran...@gmail.com> wrote:

> Thanks for the great suggestion and helpful example!
>
> Do you have any suggestion regarding adding extra step into the checkout
> process? Like when the user clicks on the product, select the quantity and
> sizes, then there is a "Next" button to let the user continue adding more
> customization to the selected product.
>
> On Wednesday, June 15, 2016 at 6:14:00 AM UTC-6, Ryne Everett wrote:
>
>> I don't think there is any reason to monkey patch a view when you can
>> just override it in your urls.py by putting the urlpattern you want to
>> override above the cartridge urls. You can see an example of how I override
>> the product view in cartridge-downloads:
>> https://github.com/ryneeverett/cartridge-downloads#urlspy.
>>
>> On Tue, Jun 14, 2016 at 8:11 PM, Tran <nhant...@gmail.com> wrote:
>>
>>> I am trying to monkey patch the def product() in cartridge.shop.views by
>>> recreating the function in another app, but it doesn't work.
>>>
>>> in my app_name/page_processor.py, I did
>>>
>>> import cartridge
>>>
>>> def modified_product():
>>>   stuff...
>>>
>>> cartridge.shop.views.product = modified_product
>>>
>>> Do you think I did the right way? I am not sure if I imported cartridge
>>> correctly or the shop.views doesn't allow monkey patch
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to mezzanine-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] monkey patch a function?

[Ryne Everett]

I don't think there is any reason to monkey patch a view when you can just
override it in your urls.py by putting the urlpattern you want to override
above the cartridge urls. You can see an example of how I override the
product view in cartridge-downloads:
https://github.com/ryneeverett/cartridge-downloads#urlspy.

On Tue, Jun 14, 2016 at 8:11 PM, Tran  wrote:

> I am trying to monkey patch the def product() in cartridge.shop.views by
> recreating the function in another app, but it doesn't work.
>
> in my app_name/page_processor.py, I did
>
> import cartridge
>
> def modified_product():
>   stuff...
>
> cartridge.shop.views.product = modified_product
>
> Do you think I did the right way? I am not sure if I imported cartridge
> correctly or the shop.views doesn't allow monkey patch
>
> --
> 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] Re: max upload size ignored

[Ryne Everett]

Oh, figured it out. There's a setting `FILEBROWSER_MAX_UPLOAD_SIZE` which 
also needs to be set.

On Tuesday, April 19, 2016 at 5:10:57 PM UTC-4, David Hoese wrote:
>
>
> I'm trying to increase the max upload size for uploads to my media 
> library, but can't seem to get anything to work. I've added a 
> "FILEBROWSER_MAX_UPLOAD_SIZE" and a "MAX_UPLOAD_SIZE" (just to be sure) and 
> set them to 40 * 1024 * 1024 which should be 40MB. I've also tried 5MB to 
> see if I can make any kind of a change, but no matter what I do the limit 
> seems to be at about 10MB. I'm running Mezzanine 4.1.0 and file browser 
> 0.4.3.
>
> Does anyone have any ideas?
>

-- 
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] AppRegistryNotReady("Models aren't loaded yet.")

[Ryne Everett]

Two things (not exhaustive) come to mind that could cause this:


   - Your app is higher in the INSTALLED_APPS order than cartridge so your
   models.py gets loaded before cartridge's.
   - You're importing (perhaps indirectly) your models.py from your
   __init__.py. Models cannot be imported at init-time.


On Tue, Jun 14, 2016 at 5:36 AM, Tran  wrote:

>
> Hello,
>
> I encountered the error* AppRegistryNotReady("Models aren't loaded yet.")*
> whenever I added * "from cartridge.shop.forms import AddProductForm"*
> into my apps_name/models.py to monkey patch some functions in the source
> code. I did look up online and it seemed people got this error all have
> django 1.8 or higher. Has anyone encountered this and might have an idea
> how to fix it?
>
> A temporarily fix I found is to move all monkey patch from
> app_name/models.py to the shop source code page_processors.py.
> This is the tutorial I followed (the author used the old django version
> http://bitofpixels.com/blog/collecting-additional-information-on-a-per-product-basis-in-cartridge/
> )
>
> I don't want to modify/add any source code because they are ignored by
> git. Any ideas are appreciated!
>
> 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] Re: Link model - external vs internal URLs

[Ryne Everett]

I wonder if there isn't some sort of validation or coercion we could do 
without narrowing the use cases. As far as I can tell, the protocol (http, 
https, etc) is required or it becomes a relative link. For example:

   - 'https://www.example.com' -> 'https://www.example.com'
   - 'www.example.com' -> 'localhost:8000/www.example.com'
   - 'example.com' -> 'localhost:8000/example.com'

These are all ways people are used to using urls, even if they're 
technically incomplete. I think they can also all be parsed in such a way 
that they're unambiguously external.

On Sunday, July 5, 2015 at 8:28:50 PM UTC-4, Stephen McDonald wrote:
>
> Hi all,
>
> We're looking at fixing some issues around the Link model. Its original 
> intention was for external links (to other websites), but people currently 
> use it with internal links as well to achieve different scenarios with site 
> navigation. If you have other examples of this that you depend on, could 
> you chime in here: 
> https://github.com/stephenmcd/mezzanine/issues/1345#issuecomment-118676898
>
> Thanks
>
>
> -- 
> 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] Novice Python question about Cartridge model: Order

[Ryne Everett]

>
> Can you recommend a better, more feature-rich way to step through my
> Python programs?


Sometimes I use ptpdb  which is
the most advanced python debugger I'm aware of. It's a little slow though,
so I mostly just use pdb.

On Thu, Jun 9, 2016 at 5:31 PM, Ryan Hewitt 
wrote:

> Kenneth,
>
> This is good advice generally.  Still, I like to approach projects this
> way because I believe it forces me to flex all sorts of mental developer
> muscles that would otherwise atrophy.  I don't want to lose the ability to
> construct and explore a data model in my head and I find it educational to
> work bottom-to-top.  Perhaps I'm just a masochist?
>
> Also: I come from an enterprise, IDE-heavy Java background and from there
> moved into full stack JavaScript.  In both of these languages I have
> experience with fantastic step-through debuggers and inspectors.  In Python
> I've so far been constrained to logging, the REPL, and to pdb.set_trace().
> I only just found that I can use pdb interactively when Django is in Debug
> mode.  Can you recommend a better, more feature-rich way to step through my
> Python programs?
>
> On Thursday, June 9, 2016 at 12:36:31 PM UTC-7, Kenneth Bolton wrote:
>>
>> Start with a working installation, then try to understand what it
>> does. Going the other direction is like learning to read with only an
>> alphabet and no primer texts.
>>
>> -ken
>>
>> On Thu, Jun 9, 2016 at 3:19 PM, Ryan Hewitt 
>> wrote:
>> > I'm simultaneously learning Django, Mezzanine and Cartridge.  For years
>> I've
>> > used Python only for small projects and I'm not as familiar with
>> debugging
>> > and tooling as I should be.  I'm trying to grok the Cartridge codebase
>> as
>> > fully as possible before using it in my project.
>> >
>> > I'm confused about the following block of code in cartridge.models
>> >
>> >
>> > from mezzanine.core.models import SiteRelated
>> > ...
>> > class Order(SiteRelated):
>> > ...
>> > def setup(self, request):
>> > ...
>> > for item in request.cart:
>> > product_fields = [f.name for f in
>> SelectedProduct._meta.fields]
>> > item = dict([(f, getattr(item, f)) for f in
>> product_fields])
>> > self.items.create(**item)
>> >
>> >
>> >
>> > I can't seem to resolve "self.items".  I don't see "items" being set
>> > anywhere in this class or the Mezzanine SiteRelated, or in Django
>> Model, or
>> > Django ModelBase.  It's not set from
>> > cartridge.shop.models.Order.session_fields, I don't see this being set
>> by
>> > cartridge.shop.managers.OrderManager or any of its super classes.  It
>> does
>> > not seem to inherit from anything resembling dict, nor does dict.items
>> have
>> > a create function.  Further, I've downloaded PyCharm and set up a
>> virtualenv
>> > - the IDE can't seem to resolve it either.
>> >
>> > Surely the Order model isn't broken.  What am I overlooking?
>> >
>> > Link on GitHub:
>> >
>> https://github.com/stephenmcd/cartridge/blob/ffd5aea45febc43b160b4b381fbf5d2cc5a51725/cartridge/shop/models.py#L487
>> >
>> > Cartridge==0.11.0
>> >
>> > Django==1.9.5
>> >
>> > Mezzanine==4.1.0
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Mezzanine Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to mezzanine-use...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 let account users to editing anywhere but not only in admin dashboard?

[Ryne Everett]

I think things ought to only appear editable if the user has permission to
edit the model. I can't say for sure if this is actually implemented but it
probably is.

On Fri, Jun 3, 2016 at 3:58 AM, Travis <travis@gmail.com> wrote:

> Hi Ryne,
>
> Thanks for your reply, but did all users should use inline-editing,
> include account users of the website?
> And what permission should be assigned to them?
>
> On Friday, June 3, 2016 at 9:29:04 AM UTC+8, Ryne Everett wrote:
>>
>> I believe you're looking for
>> http://mezzanine.jupo.org/docs/inline-editing.html.
>>
>> On Thu, Jun 2, 2016 at 6:45 AM, Travis <travi...@gmail.com> wrote:
>>
>>> Hi guys,
>>> how could i add editing to somewhere like blog post detail page, to let
>>> users make their own blog post.
>>> Or should all editing must be 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-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 let account users to editing anywhere but not only in admin dashboard?

[Ryne Everett]

I believe you're looking for
http://mezzanine.jupo.org/docs/inline-editing.html.

On Thu, Jun 2, 2016 at 6:45 AM, Travis  wrote:

> Hi guys,
> how could i add editing to somewhere like blog post detail page, to let
> users make their own blog post.
> Or should all editing must be 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.
>

-- 
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] keepachangelog.com

[Ryne Everett]

That's a great idea Mike. I like that better than any of the ideas I've
heard so far. There is still some discipline required -- every substantial
commit must address a ticket -- but that's a good practice anyway.

On Tue, May 31, 2016 at 7:50 PM, Mike Dewhirst <mi...@dewhirst.com.au>
wrote:

> On 1/06/2016 6:12 AM, Ryne Everett wrote:
>
>>  ### Why can’t people just use a `git log` diff?
>>
>> Because log diffs are full of noise — by nature. They could not
>> make a suitable
>> change log even in a hypothetical project run by perfect humans who
>> never make
>> typos, never forget to commit new files, never miss any part of a
>> refactoring.
>> The purpose of a commit is to document one atomic step in the process
>> by which
>> the code evolves from one state to another. The purpose of a change
>> log is to
>> document the noteworthy differences between these states.
>>
>>
> We use Trac for ticketing and modified the ticket to include a custom
> field called, wait for it ... "Release note" ... which is filled in when
> the ticket is written. It contains the exact words the ticket writers want
> used when release notes are compiled.
>
>
> --
> 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] Re: Cannot install Drum successfully

[Ryne Everett]

Seems that the pypi package is out of date. That was fixed here:
https://github.com/stephenmcd/drum/pull/22. You can install straight from
github with `pip install -U git+https://github.com/stephenmcd/drum.git`.

On Sat, May 28, 2016 at 12:04 AM, Xuwen Fang  wrote:

> Thank you! I uncommented the "mezzanine.pages" and made migrations so I
> could enter the admin site.
>
> However, I still got an error when posting and commenting on links on the
> site. After I post or comment, the page shows:
>
> NameError at /link/create/
> name 'reduce' is not defined
> Request Method: POST
> Request URL: http://127.0.0.1:8000/link/create/
> Django Version: 1.9.6
> Exception Type: NameError
> Exception Value:
> name 'reduce' is not defined
> Exception Location: 
> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/drum/links/models.py
> in save, line 61
> Python Executable: /home/xuwen/workspaces/python/bbs/bin/python
> Python Version: 3.4.3
> Python Path:
> ['/home/xuwen/workspaces/python/bbs/xc_bbs',
>  '/home/xuwen/workspaces/python/bbs/lib/python3.4',
>  '/home/xuwen/workspaces/python/bbs/lib/python3.4/plat-x86_64-linux-gnu',
>  '/home/xuwen/workspaces/python/bbs/lib/python3.4/lib-dynload',
>  '/usr/lib/python3.4',
>  '/usr/lib/python3.4/plat-x86_64-linux-gnu',
>  '/home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages']
>
>
> But the posts and comments had been processed because I can see the links
> and comments after refreshing the home page.
> I'm sorry for not being good at django...
>
>
>
>
>
>
> 在 2016年5月28日星期六 UTC+8上午10:00:30，Xuwen Fang写道：
>
>> Hello.
>> I want to install a Drum instance and follow the instructions on
>> https://github.com/stephenmcd/drum
>> And after "python manage.py createdb --noinput", it shows the following:
>>
>>
>>
>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/mezzanine/utils/conf.py:47:
>> UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django
>> requires. Will fall back to the domains configured as sites.
>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/django/template/utils.py:37:
>> RemovedInDjango110Warning: You haven't defined a TEMPLATES setting. You
>> must do so before upgrading to Django 1.10. Otherwise Django will be unable
>> to load templates.
>>   "unable to load templates.", RemovedInDjango110Warning)
>>
>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/drum/links/urls.py:39:
>> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
>> will be removed in Django 1.10. Update your urlpatterns to be a list of
>> django.conf.urls.url() instances instead.
>>   name="link_list_tag"),
>>
>> /home/xuwen/workspaces/python/bbs/xc_bbs/xc_bbs/urls.py:12:
>> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
>> will be removed in Django 1.10. Update your urlpatterns to be a list of
>> django.conf.urls.url() instances instead.
>>   ("^", include("mezzanine.urls")),
>>
>> System check identified some issues:
>>
>> WARNINGS:
>> ?: (mezzanine.core.W01) Please update your settings to use the TEMPLATES
>> setting rather than the deprecated individual TEMPLATE_ settings. The
>> latter are unsupported and correct behaviour is not guaranteed. Here's a
>> suggestion based on on your existing configuration:
>>
>> TEMPLATES = [{'APP_DIRS': True,
>>   'BACKEND':
>> 'django.template.backends.django.DjangoTemplates',
>>   'DIRS':
>> ('/home/xuwen/workspaces/python/bbs/xc_bbs/templates',),
>>   'OPTIONS': {'builtins': ['mezzanine.template.loader_tags'],
>>   'context_processors':
>> ('django.contrib.auth.context_processors.auth',
>>
>>  'django.contrib.messages.context_processors.messages',
>>
>>  'django.core.context_processors.debug',
>>
>>  'django.core.context_processors.i18n',
>>
>>  'django.core.context_processors.static',
>>
>>  'django.core.context_processors.media',
>>
>>  'django.core.context_processors.request',
>>  '
>> django.core.context_processors.tz',
>>
>>  'mezzanine.conf.context_processors.settings',
>>
>>  'mezzanine.pages.context_processors.page')}}]
>>
>> ?: (mezzanine.core.W02) TEMPLATE_DEBUG and DEBUG settings have different
>> values, which may not be what you want. Mezzanine used to fix this for you,
>> but doesn't any more. Update your settings.py to use the TEMPLATES setting
>> to have template debugging controlled by the DEBUG setting.
>>
>> Operations to perform:
>>   Apply all migrations: sites, django_comments, core, redirects, admin,
>> generic, auth, links, contenttypes, sessions, conf
>> Running migrations:
>>   Rendering model states... DONE
>>   Applying contenttypes.0001_initial... OK
>>   Applying auth.0001_initial... OK
>>   Applying admin.0001_initial... OK
>>   Applying admin.0002_logentry_remove_auto_add... OK
>>   Applying 

Re: [mezzanine-users] Cannot install Drum successfully

[Ryne Everett]

o.contrib.auth.context_processors.auth',
>
>  'django.contrib.messages.context_processors.messages',
>
>  'django.core.context_processors.debug',
>
>  'django.core.context_processors.i18n',
>
>  'django.core.context_processors.static',
>
>  'django.core.context_processors.media',
>
>  'django.core.context_processors.request',
>  '
> django.core.context_processors.tz',
>
>  'mezzanine.conf.context_processors.settings',
>
>  'mezzanine.pages.context_processors.page')}}]
>
> ?: (mezzanine.core.W02) TEMPLATE_DEBUG and DEBUG settings have different
> values, which may not be what you want. Mezzanine used to fix this for you,
> but doesn't any more. Update your settings.py to use the TEMPLATES setting
> to have template debugging controlled by the DEBUG setting.
>
> System check identified 2 issues (0 silenced).
> May 28, 2016 - 02:43:29
> Django version 1.9.6, using settings 'xc_bbs.settings'
> Starting development server at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
>
>
>
> Is there something wrong with the templating settings? I didn't find a
> TEMPLATE directory in the whole project directory.
>
>
>
>
> 在 2016年5月28日星期六 UTC+8上午10:34:44，Ryne Everett写道：
>>
>> No, that ought to work. What is the "error page" you're getting? What
>> does the console show for that request?
>>
>> On Fri, May 27, 2016 at 10:27 PM, Xuwen Fang <fxu...@gmail.com> wrote:
>>
>>> No. In the virtualenv, I installed Django-1.9.6. This is according to
>>> what "pip list" shows. Is that matter? Should I install a lower Django
>>> version?
>>>
>>> 在 2016年5月28日星期六 UTC+8上午10:10:39，Ryne Everett写道：
>>>>
>>>> Do you have django-1.10 installed per chance? Mezzanine doesn't support
>>>> 1.10 yet.
>>>>
>>>> On Fri, May 27, 2016 at 9:50 PM, Xuwen Fang <fxu...@gmail.com> wrote:
>>>>
>>>>> Hello.
>>>>> I want to install a Drum instance and follow the instructions on
>>>>> https://github.com/stephenmcd/drum
>>>>> And after "python manage.py createdb --noinput", it shows the
>>>>> following:
>>>>>
>>>>>
>>>>>
>>>>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/mezzanine/utils/conf.py:47:
>>>>> UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django
>>>>> requires. Will fall back to the domains configured as sites.
>>>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>>>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/django/template/utils.py:37:
>>>>> RemovedInDjango110Warning: You haven't defined a TEMPLATES setting. You
>>>>> must do so before upgrading to Django 1.10. Otherwise Django will be 
>>>>> unable
>>>>> to load templates.
>>>>>   "unable to load templates.", RemovedInDjango110Warning)
>>>>>
>>>>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/drum/links/urls.py:39:
>>>>> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
>>>>> will be removed in Django 1.10. Update your urlpatterns to be a list of
>>>>> django.conf.urls.url() instances instead.
>>>>>   name="link_list_tag"),
>>>>>
>>>>> /home/xuwen/workspaces/python/bbs/xc_bbs/xc_bbs/urls.py:12:
>>>>> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
>>>>> will be removed in Django 1.10. Update your urlpatterns to be a list of
>>>>> django.conf.urls.url() instances instead.
>>>>>   ("^", include("mezzanine.urls")),
>>>>>
>>>>> System check identified some issues:
>>>>>
>>>>> WARNINGS:
>>>>> ?: (mezzanine.core.W01) Please update your settings to use the
>>>>> TEMPLATES setting rather than the deprecated individual TEMPLATE_ 
>>>>> settings.
>>>>> The latter are unsupported and correct behaviour is not guaranteed. Here's
>>>>> a suggestion based on on your existing configuration:
>>>>>
>>>>> TEMPLATES = [{'APP_DIRS': True,
>>>>>   'BACKEND':
>>>>> 'django.template.backends.django.DjangoTemplates',
>>>>>   'DIRS':
>>>>> ('/home/xuwen/workspaces/python/bbs/xc_bbs/templates

Re: [mezzanine-users] Cannot install Drum successfully

[Ryne Everett]

No, that ought to work. What is the "error page" you're getting? What does
the console show for that request?

On Fri, May 27, 2016 at 10:27 PM, Xuwen Fang <fxu...@gmail.com> wrote:

> No. In the virtualenv, I installed Django-1.9.6. This is according to what
> "pip list" shows. Is that matter? Should I install a lower Django version?
>
> 在 2016年5月28日星期六 UTC+8上午10:10:39，Ryne Everett写道：
>>
>> Do you have django-1.10 installed per chance? Mezzanine doesn't support
>> 1.10 yet.
>>
>> On Fri, May 27, 2016 at 9:50 PM, Xuwen Fang <fxu...@gmail.com> wrote:
>>
>>> Hello.
>>> I want to install a Drum instance and follow the instructions on
>>> https://github.com/stephenmcd/drum
>>> And after "python manage.py createdb --noinput", it shows the following:
>>>
>>>
>>>
>>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/mezzanine/utils/conf.py:47:
>>> UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django
>>> requires. Will fall back to the domains configured as sites.
>>>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
>>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/django/template/utils.py:37:
>>> RemovedInDjango110Warning: You haven't defined a TEMPLATES setting. You
>>> must do so before upgrading to Django 1.10. Otherwise Django will be unable
>>> to load templates.
>>>   "unable to load templates.", RemovedInDjango110Warning)
>>>
>>> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/drum/links/urls.py:39:
>>> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
>>> will be removed in Django 1.10. Update your urlpatterns to be a list of
>>> django.conf.urls.url() instances instead.
>>>   name="link_list_tag"),
>>>
>>> /home/xuwen/workspaces/python/bbs/xc_bbs/xc_bbs/urls.py:12:
>>> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
>>> will be removed in Django 1.10. Update your urlpatterns to be a list of
>>> django.conf.urls.url() instances instead.
>>>   ("^", include("mezzanine.urls")),
>>>
>>> System check identified some issues:
>>>
>>> WARNINGS:
>>> ?: (mezzanine.core.W01) Please update your settings to use the TEMPLATES
>>> setting rather than the deprecated individual TEMPLATE_ settings. The
>>> latter are unsupported and correct behaviour is not guaranteed. Here's a
>>> suggestion based on on your existing configuration:
>>>
>>> TEMPLATES = [{'APP_DIRS': True,
>>>   'BACKEND':
>>> 'django.template.backends.django.DjangoTemplates',
>>>   'DIRS':
>>> ('/home/xuwen/workspaces/python/bbs/xc_bbs/templates',),
>>>   'OPTIONS': {'builtins': ['mezzanine.template.loader_tags'],
>>>   'context_processors':
>>> ('django.contrib.auth.context_processors.auth',
>>>
>>>  'django.contrib.messages.context_processors.messages',
>>>
>>>  'django.core.context_processors.debug',
>>>
>>>  'django.core.context_processors.i18n',
>>>
>>>  'django.core.context_processors.static',
>>>
>>>  'django.core.context_processors.media',
>>>
>>>  'django.core.context_processors.request',
>>>  '
>>> django.core.context_processors.tz',
>>>
>>>  'mezzanine.conf.context_processors.settings',
>>>
>>>  'mezzanine.pages.context_processors.page')}}]
>>>
>>> ?: (mezzanine.core.W02) TEMPLATE_DEBUG and DEBUG settings have different
>>> values, which may not be what you want. Mezzanine used to fix this for you,
>>> but doesn't any more. Update your settings.py to use the TEMPLATES setting
>>> to have template debugging controlled by the DEBUG setting.
>>>
>>> Operations to perform:
>>>   Apply all migrations: sites, django_comments, core, redirects, admin,
>>> generic, auth, links, contenttypes, sessions, conf
>>> Running migrations:
>>>   Rendering model states... DONE
>>>   Applying contenttypes.0001_initial... OK
>>>   Applying auth.0001_initial... OK
>>>   Applying admin.0001_initial... OK
>>>   Applying admin.0002_logentry_remove_auto_add... OK
>>>   Applying contenttypes.0002_remove_content_type_name... OK
>>>   Applying auth.0002_alter_permission_name_max_length... OK
>>

Re: [mezzanine-users] Cannot install Drum successfully

[Ryne Everett]

Do you have django-1.10 installed per chance? Mezzanine doesn't support
1.10 yet.

On Fri, May 27, 2016 at 9:50 PM, Xuwen Fang  wrote:

> Hello.
> I want to install a Drum instance and follow the instructions on
> https://github.com/stephenmcd/drum
> And after "python manage.py createdb --noinput", it shows the following:
>
>
>
> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/mezzanine/utils/conf.py:47:
> UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django
> requires. Will fall back to the domains configured as sites.
>   warn("You haven't defined the ALLOWED_HOSTS settings, which "
> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/django/template/utils.py:37:
> RemovedInDjango110Warning: You haven't defined a TEMPLATES setting. You
> must do so before upgrading to Django 1.10. Otherwise Django will be unable
> to load templates.
>   "unable to load templates.", RemovedInDjango110Warning)
>
> /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/drum/links/urls.py:39:
> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
> will be removed in Django 1.10. Update your urlpatterns to be a list of
> django.conf.urls.url() instances instead.
>   name="link_list_tag"),
>
> /home/xuwen/workspaces/python/bbs/xc_bbs/xc_bbs/urls.py:12:
> RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and
> will be removed in Django 1.10. Update your urlpatterns to be a list of
> django.conf.urls.url() instances instead.
>   ("^", include("mezzanine.urls")),
>
> System check identified some issues:
>
> WARNINGS:
> ?: (mezzanine.core.W01) Please update your settings to use the TEMPLATES
> setting rather than the deprecated individual TEMPLATE_ settings. The
> latter are unsupported and correct behaviour is not guaranteed. Here's a
> suggestion based on on your existing configuration:
>
> TEMPLATES = [{'APP_DIRS': True,
>   'BACKEND': 'django.template.backends.django.DjangoTemplates',
>   'DIRS':
> ('/home/xuwen/workspaces/python/bbs/xc_bbs/templates',),
>   'OPTIONS': {'builtins': ['mezzanine.template.loader_tags'],
>   'context_processors':
> ('django.contrib.auth.context_processors.auth',
>
>  'django.contrib.messages.context_processors.messages',
>
>  'django.core.context_processors.debug',
>
>  'django.core.context_processors.i18n',
>
>  'django.core.context_processors.static',
>
>  'django.core.context_processors.media',
>
>  'django.core.context_processors.request',
>  '
> django.core.context_processors.tz',
>
>  'mezzanine.conf.context_processors.settings',
>
>  'mezzanine.pages.context_processors.page')}}]
>
> ?: (mezzanine.core.W02) TEMPLATE_DEBUG and DEBUG settings have different
> values, which may not be what you want. Mezzanine used to fix this for you,
> but doesn't any more. Update your settings.py to use the TEMPLATES setting
> to have template debugging controlled by the DEBUG setting.
>
> Operations to perform:
>   Apply all migrations: sites, django_comments, core, redirects, admin,
> generic, auth, links, contenttypes, sessions, conf
> Running migrations:
>   Rendering model states... DONE
>   Applying contenttypes.0001_initial... OK
>   Applying auth.0001_initial... OK
>   Applying admin.0001_initial... OK
>   Applying admin.0002_logentry_remove_auto_add... OK
>   Applying contenttypes.0002_remove_content_type_name... OK
>   Applying auth.0002_alter_permission_name_max_length... OK
>   Applying auth.0003_alter_user_email_max_length... OK
>   Applying auth.0004_alter_user_username_opts... OK
>   Applying auth.0005_alter_user_last_login_null... OK
>   Applying auth.0006_require_contenttypes_0002... OK
>   Applying auth.0007_alter_validators_add_error_messages... OK
>   Applying sites.0001_initial... OK
>   Applying conf.0001_initial... OK
>   Applying core.0001_initial... OK
>   Applying core.0002_auto_20150414_2140... OK
>   Applying django_comments.0001_initial... OK
>   Applying django_comments.0002_update_user_email_field_length... OK
>   Applying django_comments.0003_add_submit_date_index... OK
>   Applying generic.0001_initial... OK
>   Applying generic.0002_auto_20141227_0224... OK
>   Applying links.0001_initial... OK
>   Applying redirects.0001_initial... OK
>   Applying sessions.0001_initial... OK
>   Applying sites.0002_alter_domain_unique... OK
>
> Creating default site record: 127.0.0.1:8000 ...
> Creating default account (username: admin / password: default) ...
>
>
>
> Then after I "python manage.py runserver", the
> http://127.0.0.1:8000/admin/ shows an error page.
> Please tell me how I can solve 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, 

Re: [mezzanine-users] Re: Cartridge Admin Questions

[Ryne Everett]

Thanks for your responses Josh, my own are inline:


> 1. Most clients I have worked with have existing SKUs for products so this
> makes it easier for those to be tied together.


Fair enough.

2. There might be another reason but its also a limitation of Django
> Inlines. Also there is a way to change this functional but can cause other
> issues.


It seems like it would just be a matter of changing the `extra` or
`min_num` attribute on the inline. Perhaps I'll encounter the "other
issues" if I try this.

3. This is a tough one as we wouldn't want the Unit Price to be required,
> as I have had clients add products but not want them available for sale.


There's already a `Product.available` field to handle this use case. Rather
than make the `ProductVariation.unit_price` required, what if we made the
`Product.available` validator require there to be at least one variation
with a price in order to set it to `True`?


On Wed, May 11, 2016 at 10:51 PM, Josh B <josh.batche...@wearetopsecret.com>
wrote:

> Hey Ryne,
>
> 1. Most clients I have worked with have existing SKUs for products so this
> makes it easier for those to be tied together.
> 2. There might be another reason but its also a limitation of Django
> Inlines. Also there is a way to change this functional but can cause other
> issues.
> 3. This is a tough one as we wouldn't want the Unit Price to be required,
> as I have had clients add products but not want them available for sale.
>
>
> On Wednesday, May 11, 2016 at 12:18:36 PM UTC-6, Ryne Everett wrote:
>>
>> The following observations and screenshots are from a fresh cartridge
>> 0.11 project I just made.
>>
>>1. Why are sku fields editable? Cartridge uses them essentially as
>>foreign key's. Is there any use case for editing a sku from the admin?
>>Seems like a user could really screw things up with no appreciation for
>>what's going on under the hood.
>>2. You can't edit ProductVariation's until you initially save the
>>Product:  Is this intentional, a bug, or a limitation of django admin
>>inlines?
>>3. Until one adds a "unit price" to a variation, a product is
>>unavailable: But there is no indication that this is a problem in the
>>admin. Is this intentional, a bug, or a limitation of django admin? It
>>seems to me that this is probably unfixable without addressing #2 -- if 
>> you
>>have to save the Product before editing the ProductVariation's, then
>>causing the Product validation to fail when a ProductVariation is missing 
>> a
>>required field is not an option.
>>
>> --
> 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] Cartridge Admin Questions

[Ryne Everett]

The following observations and screenshots are from a fresh cartridge 0.11
project I just made.

   1. Why are sku fields editable? Cartridge uses them essentially as
   foreign key's. Is there any use case for editing a sku from the admin?
   Seems like a user could really screw things up with no appreciation for
   what's going on under the hood.
   2. You can't edit ProductVariation's until you initially save the
   Product:  Is this intentional, a bug, or a limitation of django admin
   inlines?
   3. Until one adds a "unit price" to a variation, a product is
   unavailable: But there is no indication that this is a problem in the
   admin. Is this intentional, a bug, or a limitation of django admin? It
   seems to me that this is probably unfixable without addressing #2 -- if you
   have to save the Product before editing the ProductVariation's, then
   causing the Product validation to fail when a ProductVariation is missing a
   required field is not an option.

-- 
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] Introducing Cartridge Downloads

[Ryne Everett]

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.

Re: [mezzanine-users] Re: Cartridge with Stripe and Zebra is swallowing errors?

[Ryne Everett]

I had the exact same thoughts until I found out that there is built-in
stripe support. It hasn't made a docs release yet, but here's my pr
documenting it: https://github.com/stephenmcd/cartridge/pull/284.

On Wed, Apr 13, 2016 at 2:29 PM, Geoffrey Eisenbarth <
geoffrey.eisenba...@gmail.com> wrote:

> I just got the same errors with Mezzanine 4.1.0, stripe 1.32.0, Cartridge
> 0.11.0, and cartridge-stripe 0.1.3. Looks like cartridge-stripe hasn't been
> updated in forever, but I'll try to find the issue and make a pull request.
> At this point it might have been worth it to just go with Braintree, which
> seems to have more active developement wrt mezzanine and cartridge.
>
>
> On Friday, June 7, 2013 at 7:46:50 PM UTC-5, Rob Lineberger wrote:
>>
>> The issue was an incompatibility with templates and Django 1.5.1.  Tim
>> Watts put in a fix and pushed the code so this issue is fixed.  Thanks for
>> the suggestions!
>>
>> On Wednesday, June 5, 2013 1:30:52 PM UTC-4, Rob Lineberger wrote:
>>>
>>> Still no dice. I started over with a clean virtualenv and installed
>>> zebra, cartridge-stripe, and then cartridge. Changed the settings.py file
>>> with my stripe dev tokens, then fired up the vanilla install.  When I add a
>>> red pony to the cart and checkout, I get the errors:
>>>
>>>
>>>- (Hidden field last_4_digits) This field is required.
>>>- (Hidden field stripe_token) This field is required.
>>>
>>>   According to the Cartridge Change Log, Stripe Integration was added in
>>> version 0.7.0 .  Do I need to explicitly install zebra and
>>> cartridge-stripe? I am missing a boat somewhere.
>>>
>> --
> 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] No Metadata editing enabled in admin, no fields visible

[Ryne Everett]

You might look in the developer console for errors.

On Tue, Mar 29, 2016 at 6:12 AM, Iain Mac Donald  wrote:

> On Tue, 29 Mar 2016 03:00:27 -0700 (PDT)
> byezy  wrote:
>
> > doesn't work. any other thoughts?
>
> *I think* I had a similar problem a while back but I didn't make a
> note. From memory the browser that had the problem had dom storage
> disabled. Enabling dom storage fixed the problem.
>
> On Firefox set:
> dom.storage.enabled true
>
> --
>
> Regards,
> Iain.
>
> --
> 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] No Metadata editing enabled in admin, no fields visible

[Ryne Everett]

I think it is "folded" by default and clicking the header bar expands it.

On Tue, Mar 22, 2016 at 9:30 PM, byezy  wrote:

> Hi,
>
> I have just installed the latest Mezzanine and am learning my way around.
> Total noob.
>
> When logged in as an administrator if I create or edit a page, I do not
> see metadata fields... I can see the header bar but there's nothing below
> it.
>
> What am I missing?
>
> Thanks n 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.
>

-- 
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: Require.js integration

[Ryne Everett]

>
> I'm also interested in a more modern admin UI.  However, for the reasons
> outlined in this post, it will almost certainly never make it into the
> official mezzanine package, so its best to keep that in mind.
>

Nice. I hadn't seen that post before. But I'm not sure if it's entirely
accurate anymore. I've heard murmurings (can't find them now) that it's not
really possible/practical to use mezzanine without
grappelli-safe/filebrowser-safe any more, but I haven't tried myself.

Also, I'm not sure if those principles are really in conflict with "a more
modern UI." Stephen doesn't want to add dependencies, but that doesn't
necessarily mean he wouldn't accept a PR updating the templates/stylesheets.


> Override/Overextend the template /admin/base.html, and whatever other
> admin UI elements you want to replace.  You can easily put whatever version
> of jQuery you want in here.  This would insulate you having to fit within
> the mezzanine principles and workflow.
>

Override/Overextend is a key part of the mezzanine principles and workflow.
:)

On Mon, Mar 14, 2016 at 10:10 AM, Derek Adair  wrote:

> I'm also interested in a more modern admin UI.  However, for the reasons
> outlined in this post ,
> it will almost certainly never make it into the official mezzanine package,
> so its best to keep that in mind.  There are a couple things that could be
> done here for more long-term solutions;
>
>1. Submit a PR to grappelli_safe
> using an updated
>version of jQuery (no idea how this will be received, but i'm pretty sure
>if it doesn't break anything it'd be welcomed).  I can't say for sure, as
>i'm not the owner of the project here, but, there is likely room for stuff
>like;
>- Boostrap Integration
>   - Better S3 Integration (i'm figuring this one out right now
>   actually)
>  - I'm interested in S3 direct upload myself
>   - Any other feature you are willing to work on, that doesn't go
>   against the principles Stephen outlined in the above linked issue.  If 
> it
>   is not something you are willing to contribute you will likely not gain
>   much traction.
>2. Override/Overextend the template /admin/base.html, and whatever
>other admin UI elements you want to replace.  You can easily put whatever
>version of jQuery you want in here.  This would insulate you having to fit
>within the mezzanine principles and workflow.
>3. Fork grappelli_safe and release your own pre-packaged and pypi
>ready admin ui for mezzanine - django-bootstrap
> could help you
>here, but wouldn't be necessary.
>
> I'd be very interested in a bootstrap compatible Admin UI with more user
> centric features, so let me know if you do any work towards these ends.
>
> On Monday, March 14, 2016 at 9:15:09 AM UTC-5, Encolpe Degoute wrote:
>>
>> Yeh, it's a good tip too.
>>
>> My goal is to be able to integrate complex themes like gentelella (
>> https://github.com/puikinsh/gentelella -
>> https://colorlib.com/polygon/gentelella/index.html) with a better
>> visibilty for js plugins.
>>
>> It could also make easier to handle js library in separate django
>> packages.
>>
>> Thanks
>>
>> Le lundi 14 mars 2016 14:47:25 UTC+1, Derek Adair a écrit :
>>>
>>> This would be interesting.  I am on board.  As i'm pretty new here i'm
>>> not so sure if it belongs in the source code, but it'd be pretty easy to
>>> implement this in a reusable way if not.
>>>
>>> Also if you or anyone else is interested in a different solution you can
>>> run jQuery in no conflict mode
>>> 
>>>  and
>>> get the same result.
>>>
>>> On Monday, March 14, 2016 at 5:42:31 AM UTC-5, Encolpe Degoute wrote:

 Hello,

 After some hours spent javascript version conflict -- I need jQuery 1.9
 or 2.0 and default mezzanine installation use 1.7 from 2011 -- I remembered
 that require.js can do the trick.
 Is there some interrest in this integration or someone again it ?

 Regards,
 Encolpe

>>> --
> 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] Re: Mezzanine + Grapelli?

[Ryne Everett]

>
> Apologies, i read your comments as advocating for folding it into the code
> base. But please let me clarify what that means to me.  I am not advocating
> for or against keeping these projects in the same repository, I am
> advocating for a clean break from the forks and ownership of these projects
> (which has all but already happens it seems).  If there is no feasible
> upgrade path these projects probably deserve their own namespace,
> documentation and TLC.
>
> To me it would be easier to extend and customize in the sense of a much
> lower learning curve.   Currently there are Mezzanine specific features in
> each of the projects that are made much more difficult to discover by not
> only the lack of documentation, but the naming conventions.  A new
> developer can easily miss the subtle implications of the decision to fork
> these projects and it is by far and away not clear that there has been a
> clean break until you try to upgrade grappelli/filebrowser.
>
> I mean something as simple as just changing the names of these projects
> would go a LONG way here.  Mezzanine-filebrowser + mezzanine-admin sounds
> good to me and would add tons of clarity to the dependency chain.
>

Gotcha. I agree that renaming them mezzanine- would make the break
clearer, but I don't think that's necessary. As for documentation, I'm sure
documentation patches would be accepted.

On Sun, Mar 13, 2016 at 10:09 AM, Derek Adair <d...@derekadair.com> wrote:

> Clearly I suck at collaborating via text.  I'm not very experienced in it,
> I work much better when I can have discussions in person so its a challenge
> to articulate on these forums.  Thank you all for your patience and
> responses.
>
>
> On Sunday, March 13, 2016 at 9:58:22 AM UTC-5, Derek Adair wrote:
>>
>> Apologies, i read your comments as advocating for folding it into the
>> code base. But please let me clarify what that means to me.  I am not
>> advocating for or against keeping these projects in the same repository, I
>> am advocating for a clean break from the forks and ownership of these
>> projects (which has all but already happens it seems).  If there is no
>> feasible upgrade path these projects probably deserve their own namespace,
>> documentation and TLC.
>>
>> To me it would be easier to extend and customize in the sense of a much
>> lower learning curve.   Currently there are Mezzanine specific features in
>> each of the projects that are made much more difficult to discover by not
>> only the lack of documentation, but the naming conventions.  A new
>> developer can easily miss the subtle implications of the decision to fork
>> these projects and it is by far and away not clear that there has been a
>> clean break until you try to upgrade grappelli/filebrowser.
>>
>> I mean something as simple as just changing the names of these projects
>> would go a LONG way here.  Mezzanine-filebrowser + mezzanine-admin sounds
>> good to me and would add tons of clarity to the dependency chain.
>>
>>
>> On Saturday, March 12, 2016 at 8:55:17 PM UTC-6, Ryne Everett wrote:
>>>
>>> I'm all for bringing these projects into the code base if this is the
>>>> case. (says the guy w/ zero commits/PRs) I think that would have alleviated
>>>> a very significant part of my confusion and you certainly wouldn't get
>>>> people like me asking this question in 20 different ways.
>>>
>>>
>>> That's a heavy-handed way to deal with a documentation issue.
>>>
>>> It would also make extending and customizing the look and feel a lot
>>>> easier.
>>>
>>>
>>> How so?
>>>
>>> On Sat, Mar 12, 2016 at 9:39 PM, Derek Adair <d...@derekadair.com>
>>> wrote:
>>>
>>>> I'm all for bringing these projects into the code base if this is the
>>>> case. (says the guy w/ zero commits/PRs) I think that would have alleviated
>>>> a very significant part of my confusion and you certainly wouldn't get
>>>> people like me asking this question in 20 different ways.  It would also
>>>> make extending and customizing the look and feel a lot easier.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Mezzanine Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to mezzanine-use...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 use wildcard solution to display content

[Ryne Everett]

I think you need to do some url rewriting outside of django. I haven't
looked at this solution very closely but maybe it will give you some ideas:
http://stackoverflow.com/questions/29938338/django-multi-tenancy.

On Sun, Mar 13, 2016 at 5:06 AM, wh4n  wrote:

> Hello guys,
>
> I have a problem I don't know how to solve. Mezzanine takes cares of the
> multi tenancy. But how can I display other content based on subdomain? For
> example:
>
> I have a site called *thomas.example.com * and
> another site called *andrea.example.com *
>
> I want a solution to grab with sort of a dynamic/wildcard url to display
> the content based on the user (the same as the domain). To demonstrate:
>
> url(r'(?!www)\w+', 'main.blog_urls', name='wildcard'),
>
> The view:
>
> def wildcard(request, wildcard):
> subcontent = Blogpost.objects.filter(user=wildcard)
> return render(request, 'index.html', {'subcontent': subcontent})
>
> I have no clue what so ever how to go further with this.
>
> --
> 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 look and feel not rendering when Debug=False

[Ryne Everett]

http://mezzanine.jupo.org/docs/frequently-asked-questions.html#static-files

On Sun, Mar 13, 2016 at 4:30 AM, Venkateswararao Thota <
thota.v@gmail.com> wrote:

> Looks like the static contents not loading when Debug=False, Any
> suggestions?
>
> --
> 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] Re: Mezzanine + Grapelli?

[Ryne Everett]

>
> I'm all for bringing these projects into the code base if this is the
> case. (says the guy w/ zero commits/PRs) I think that would have alleviated
> a very significant part of my confusion and you certainly wouldn't get
> people like me asking this question in 20 different ways.


That's a heavy-handed way to deal with a documentation issue.

It would also make extending and customizing the look and feel a lot easier.


How so?

On Sat, Mar 12, 2016 at 9:39 PM, Derek Adair  wrote:

> I'm all for bringing these projects into the code base if this is the
> case. (says the guy w/ zero commits/PRs) I think that would have alleviated
> a very significant part of my confusion and you certainly wouldn't get
> people like me asking this question in 20 different ways.  It would also
> make extending and customizing the look and feel a lot easier.
>
> --
> 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] Re: Mezzanine + Grapelli?

[Ryne Everett]

I'm inclined to agree that this information isn't the easiest to find even
though it's in the FAQ.

I would suggest replacing the paragraph in each project's readme:

This repository exists for bug fixes and minor enhancements, and should
> some day become redundant, once the original {% project %} becomes a
> feasibly stable dependency target.


with a line incorporating that canonical FAQ link.

On Sat, Mar 12, 2016 at 8:50 PM, Ryne Everett <ryneever...@gmail.com> wrote:

> I was about to suggest adding that to the FAQ but then I realized it's
> already there.
> http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-are-grappelli-and-filebrowser-forked
>
> On Sat, Mar 12, 2016 at 8:44 PM, Stephen McDonald <st...@jupo.org> wrote:
>
>> The forks have diverged from their origins significantly - features
>> removed, Mezzanine specific things added. The fact they're separate repos
>> from Mezzanine is insignificant, their code bases might as well be part of
>> Mezzanine itself. This has been thrashed out multiple times on this list
>> already.
>>
>> On Sun, Mar 13, 2016 at 12:40 PM, Derek Adair <d...@derekadair.com> wrote:
>>
>>> I've spent about 1-2 hours looking for this specific subject on this
>>> forum and in google in general and i'm not getting much results other than 
>>> this
>>> page
>>> <https://groups.google.com/forum/#!searchin/mezzanine-users/grappelli$20alternative$20%7Csort:relevance/mezzanine-users/Z9R4XX7K1B8/MyCW2Gia-EsJ>
>>>  which
>>> pretty much confirms that its just not been done b/c its a lot of work AND 
>>> *there
>>> really isn't much reason too*? is that correct?  I really am coming
>>> from the same perspective of the poster in that thread and i'm just trying
>>> to get a feel for what the best option is.
>>>
>>> Could you maybe give me a tl;dr; other than just not worth the effort?
>>> Just trying to understand.
>>>
>>> On Saturday, March 12, 2016 at 6:30:55 PM UTC-6, Derek Adair wrote:
>>>>
>>>> Thank you for updating those repositories it just didn't paint a very
>>>> good picture when i'm trying to debug issues and it looks like a very
>>>> stagnant project.
>>>>
>>>> I'll do some more digging but I really just wanted to engage the
>>>> community to see if anyone else has done any work on this or gauge the
>>>> interest.  based on the responses it sounds like pretty much no.
>>>>
>>>> On Saturday, March 12, 2016 at 2:42:22 PM UTC-6, Stephen McDonald wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Mar 13, 2016 at 7:19 AM, Derek Adair <d...@derekadair.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>1. Better support from the grapelli project.  There are issue's
>>>>>>that are ancient in both repositories with zero interaction from the
>>>>>>project owners.
>>>>>>
>>>>>>
>>>>> There were 9 open issues across the grappelli/filebrowser forks a
>>>>> moment ago - half of them were out of date and long ago resolved, so I've
>>>>> closed those now. Among the remaining are a couple of feature requests, a
>>>>> couple of obscure platform issues (Windows etc), and the one that you
>>>>> recently commented on.
>>>>>
>>>>> So realistically,  there's one issue - the one you claim to have lost
>>>>> a lot of time on. Let's not get carried away here.
>>>>>
>>>>>
>>>>>>1.  There are almost NO docs on either of these projects.  Any
>>>>>>issues are very complicated to debug because of this.
>>>>>>2. The longer this project waits to do this the harder it will
>>>>>>be.  Best to just get this over with now.
>>>>>>3. Less work.  Why even bother maintaining a fork when those
>>>>>>reasons have presumably been resolved.
>>>>>>
>>>>>> This should have been done immediately once it was at all possible to
>>>>>> for all of the above reasons.  I haven't even really compared
>>>>>> feature sets these are just philosophical reasons why I believe
>>>>>> upgrading is the right decision here.  However, I *completely* get
>>>>>> why it has been put off.  This kind of work is *horrible* and rife
>>>>>> with potential br

Re: [mezzanine-users] Re: Mezzanine + Grapelli?

[Ryne Everett]

I was about to suggest adding that to the FAQ but then I realized it's
already there.
http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-are-grappelli-and-filebrowser-forked

On Sat, Mar 12, 2016 at 8:44 PM, Stephen McDonald <st...@jupo.org> wrote:

> The forks have diverged from their origins significantly - features
> removed, Mezzanine specific things added. The fact they're separate repos
> from Mezzanine is insignificant, their code bases might as well be part of
> Mezzanine itself. This has been thrashed out multiple times on this list
> already.
>
> On Sun, Mar 13, 2016 at 12:40 PM, Derek Adair <d...@derekadair.com> wrote:
>
>> I've spent about 1-2 hours looking for this specific subject on this
>> forum and in google in general and i'm not getting much results other than 
>> this
>> page
>> <https://groups.google.com/forum/#!searchin/mezzanine-users/grappelli$20alternative$20%7Csort:relevance/mezzanine-users/Z9R4XX7K1B8/MyCW2Gia-EsJ>
>>  which
>> pretty much confirms that its just not been done b/c its a lot of work AND 
>> *there
>> really isn't much reason too*? is that correct?  I really am coming from
>> the same perspective of the poster in that thread and i'm just trying to
>> get a feel for what the best option is.
>>
>> Could you maybe give me a tl;dr; other than just not worth the effort?
>> Just trying to understand.
>>
>> On Saturday, March 12, 2016 at 6:30:55 PM UTC-6, Derek Adair wrote:
>>>
>>> Thank you for updating those repositories it just didn't paint a very
>>> good picture when i'm trying to debug issues and it looks like a very
>>> stagnant project.
>>>
>>> I'll do some more digging but I really just wanted to engage the
>>> community to see if anyone else has done any work on this or gauge the
>>> interest.  based on the responses it sounds like pretty much no.
>>>
>>> On Saturday, March 12, 2016 at 2:42:22 PM UTC-6, Stephen McDonald wrote:
>>>>
>>>>
>>>>
>>>> On Sun, Mar 13, 2016 at 7:19 AM, Derek Adair <d...@derekadair.com>
>>>> wrote:
>>>>
>>>>>
>>>>>1. Better support from the grapelli project.  There are issue's
>>>>>that are ancient in both repositories with zero interaction from the
>>>>>project owners.
>>>>>
>>>>>
>>>> There were 9 open issues across the grappelli/filebrowser forks a
>>>> moment ago - half of them were out of date and long ago resolved, so I've
>>>> closed those now. Among the remaining are a couple of feature requests, a
>>>> couple of obscure platform issues (Windows etc), and the one that you
>>>> recently commented on.
>>>>
>>>> So realistically,  there's one issue - the one you claim to have lost a
>>>> lot of time on. Let's not get carried away here.
>>>>
>>>>
>>>>>1.  There are almost NO docs on either of these projects.  Any
>>>>>issues are very complicated to debug because of this.
>>>>>2. The longer this project waits to do this the harder it will
>>>>>be.  Best to just get this over with now.
>>>>>3. Less work.  Why even bother maintaining a fork when those
>>>>>reasons have presumably been resolved.
>>>>>
>>>>> This should have been done immediately once it was at all possible to
>>>>> for all of the above reasons.  I haven't even really compared feature
>>>>> sets these are just philosophical reasons why I believe upgrading is
>>>>> the right decision here.  However, I *completely* get why it has been
>>>>> put off.  This kind of work is *horrible* and rife with potential
>>>>> breaking changes.
>>>>>
>>>>> I'll get back to you with some features, as for specific rasons there
>>>>> are some pain points in integrating with django storages/s3boto... which
>>>>> would have been alleviated in the new grapelli version.  The new
>>>>> filebrowser looks to be a lot cleaner with handling 3rd party integrations
>>>>> (like s3boto).
>>>>>
>>>>> I'm also just curious why this hasn't been done and doesn't really
>>>>> seem to even be talked about.
>>>>>
>>>>
>>>> It's been talked about extensively on this list many times, if you dig
>>>> around you'll be able to paint a much clearer picture than all the
>>>>