Best way is to use a virtualenv and pin your Django version in
requirements.txt.
It's highly recommend you develop all python projects in separate
virtual environments. This is a great guide, and also explains how to
pin (freeze) requirements:
There's a Django application called Django admin sortables. It allows you
to drag and drop any model you want. The documentation is comprehensive and
easy to integrate with Mezzanine.
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To
I think Django wouldn't know how to create your application's tables
without the migration files. Migrations are required with every concrete
model in Django 1.7 and up.
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from
Have you peeked into the TinyMCE docs? I'm sure there must be something
you can do to change this behavior in tinymce_setup.js.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from
Yep, the symlink works great in production too.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more
I think the two approaches described here are the best options: Add
target=_blank via Javascript or inject a field into the Link model to
toggle this functionality.
Another option would be to check in the menu template if the target url
starts with http or https and add the target attribute
I don't think you need to fork TinyMCE to achieve this. The editor is
highly customizable and you can make it look and work as you desire via
the configuration file (already explained by another person).
Here's the configuration option for controlling the available styles.
Add/remove to your
You have two options:
- Use the the top-level templates directory defined in settings.py
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/project_name/settings.py#L199.
You can also change this to whatever path you like.
- You can create a theme app and put
Hi everybody.
A project I'm working on has multi-tenancy enabled and a per-site media
library. However, the client would like to have some media files be
available to all sites. Is there a way to implement this? My two options
(which I will try out in the coming week):
- Disable
Not sure if it's even related, but what happens if you comment out the
__unicode__ method in your custom 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
If that's the case, it sounds like a naming problem. What was the name of
the old project and the app inside it (folder names)?
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it,
Here's how I'd do it:
Create a Service model, where you store the service type, ID, etc. Then
create a MapPage and a ServicePage which could be related to the Service
model via many to many relations.
Your users can then log into the admin, create and manage services, and
easily add them to
Yep, Django 1.6 is out of the picture. Mezzanine only supports the two
latest Django releases (1.7 and 1.8).
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Yeah, a server restart is required when you create new template tags for
Django to pick them up.
As for your template code, try putting {% test_text Flowers are nice
as my_text %} inside the block you want to use the variable (in your
case: {% block main %}).
--
You received this message
If you only want to override the add/change/delete permissions for the
BlogPost admin, you can do so by registering your own BlogPostAdmin
class instead of Mezzanine's. In the class methods you'll be able to
make all checks to grant permissions using custom logic. You'll also
need to modify
That should work without issue, though I generally like to bundle all
the as tags on top of the block.
{% block main %}
{% get_sitewide_content as sitewide %}
h1my text/h1
{{ sitewide.foobar }}
{% endblock %}
Also, be careful with the blocktrans tag, you need to explicitly bind
any variable
As an alternative, you can also use SingletonAdmin and a template tag to
make model data available anywhere in the site. Josh wrote about it and
I follow this pattern all the time:
http://bitofpixels.com/blog/on-singletonadmins-and-sitewidecontent-editing-sitewide-content-in-mezzanines-admin/.
What's your stack (OS, python version, Mezzanine version, etc)?
Could you share your FABRIC settings?
If you're using Mezzanine 4, there's a logs folder in your home
directory. That's a good place to look.
--
You received this message because you are subscribed to the Google Groups Mezzanine
Perhaps something like this:
https://docs.djangoproject.com/en/1.8/ref/settings/#migration-modules?
Not sure how that's gonna work when Mezzanine itself ships some new
migrations in the future. Maybe one has to toggle MIGRATION_MODULES
manually to apply the correct migrations.
--
You
How many verbatim tags are you using? You should wrap the whole block of
Angular template tags in a single set of verbatim tags to turn off
Django template rendering for that part only.
Also, have you tried out django-angular to integrate both frameworks? It
provides a bunch of utilities that
If you're already defining a verbatim block there's no need to wrap
stuff in verbatim tags inside it.
|
{%verbatim myblock%}
{{some text}}
{%endverbatim myblock%}
|
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this
Hmm, I remember trying both before without problem. Off the top of my head
(and take this with a grain of salt), install mezzanine first from git on
the virtual env, but make sure it is recognized as 3.1.10. Then install
cartridge from git. It will check in the virtual env that mezzanine 3.1.10
is
Also, bear in mind that you need sudo privileges in your server to use
Mezzanine's included fabfile (a VPS gives you that, hence the
recommendation to use Digital Ocean). Deploying to shared hosting
environments is another deal.
--
You received this message because you are subscribed to the
Hi Brandon. Adding to Ken's answer:
Are you using the latest version from the master branch, or the stable
version from pip?
For the latest version, the documentation was updated to include a
tutorial that should take you from a blank VPS to a working Mezzanine
site.
Hey everybody!
I'm planning to attend DjangCon 2015 (US), and wanted to know if any fellow
Mezzanine developers are coming too. Maybe we can organize a mini-meetup in
there! :D
I'm also interested in finding somebody willing to share a room. The
organizers have negotiated a special price in a
Have you tried deploying the same site using Python 2? It might just be a
matter of insufficient resources for what you're trying to do.
You can also try changing your application server from Apache to Gunicorn
or uwsgi, or just enable more workers for your site. Also, make sure you're
using the
Hey Lee.
Their Readme says it's compatible up to Django 1.5. You're using 1.8 or
1.7. Could you verify against a vanilla Django project to see if you get
the same error?
https://github.com/dokterbob/django-newsletter/blob/master/README.rst#compatibility
--
You received this message because you
Yep, only available in the development branch (which is very stable now).
Documentation here:
https://github.com/stephenmcd/mezzanine/blob/master/docs/multi-lingual-sites.rst.
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe
Hey. Can you try running fab restart and see if it fixes 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
Congrats, Steve!
How about you speak about Cartridge this time, or Drum? Or perhaps going
a little more meta, about what it is to see your project grow into
something used around the world and that has spawned a whole ecosystem.
Could be a great talk for anyone involved in Python and open
I've used JSON dumps in the past with mixed results. Generally, a
single, monolithic dump of all the data almost never works on the first
try. Some general tips:
- Make sure you run createdb again when you have changed your settings
to use Postgres. The JSON dump only populates the DB, but it
Mezzanine's blog comes with a template tag that can pull recent posts
into your template context, optionally filtering by category.
Documentation here:
http://mezzanine.jupo.org/docs/packages.html?highlight=recent_posts#mezzanine.blog.templatetags.blog_tags.blog_recent_posts
--
You received
Nice :)
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit
Hi Jean.
Yes, you can retrieve content from your custom pages too. I see two
possibilities:
- If your desired page structure allows it, you can create the pages
from which you want to pull the content as children of the page that
will show the snippets. This way the child pages are
Hello, taedori.
Do you have any more details one what exactly is failing? What do you
see when you visit the site without www? From what you've explained, it
sounds like everything is setup correctly. Are you sure your DNS
settings point both domain variants to the server were you're
Hi Gerhard. Here's what you need to do to:
1. Create a Page in the admin and manually set the slug to /.
2. In urls.py, comment out line 39.
3. Then, un-comment line 54.
Basically you want to tell Mezzanine to use the Page with the slug /
as the homepage, instead of directly rendering the
Hi Jonathan.
Are you using the Django development server, or a standalone application
server (gunicorn, uwsgi, Apache, etc)?
I've encountered similar errors when running outside the development
server, and the fix was to enable the appropriate locales in the server
configuration.
--
You
Ah, ok. See if your OS level and database locales include Spanish.
Also, create a blog post with special characters in the Mezzanine admin
to see if it also raises the exception. Perhaps it is an issue only with
imported posts.
--
You received this message because you are subscribed to the
Hi Tom. For your particular requirements, I would say no, Mezzanine
lacks this feature. There are some projects out there that are meant to
do it for vanilla Django
https://github.com/s-block/django-nested-inline and for Grappelli
https://github.com/datahub/grappelli-nested-inlines. In the
Hi! The createdb command is only for initially populating the database and
doing other bootstrapping required on first run. The other commands you see
there are required for subsequent deployments, they do the following:
- collectstatic: Gets all static resources from every installed app into a
Also, you can take a look at the issues marked as release blocker in
the issue tracker to get a sense of what is actually keeping the next
release from happening.
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group
Try adding this to your settings: USE_L10N = True.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more
It depends on the level of integration you want to achieve. Disqus supports
Facebook login, so if you're interested in the comment part only, I
recommend that. This option only requires filling up the correct settings
in the admin (as far as I remember).
You can also insert Facebook's
Add the extra variations to settings.OPTION_TYPE_CHOICES (the default
settings.py has it commented out, so it should be easy to find). Then make
and run the migrations (South or built-in, depending on your Django
version). The new column(s) will be added to you DB and the appropiate
changes
Yep, Josh's description is spot-on. Just bear in mind that the version of
jQuery currently being shipped with Mezzanine is not supported by the
latest version of Bootstrap. This is discussed here:
I join everybody else and send you a big thanks for your role in this
community, Josh. To me, Mezzanine is not only an outstanding piece of
software, but also a community worth imitating.
Have a great time in the new job :)
--
You received this message because you are subscribed to the Google
I think you meant to post to this thread instead of the other, as your
latest question has to do with your custom app.
Are you using migrations in soulapp2? As the link that appears in the
Traceback says: Be aware, however, that unmigrated apps cannot depend on
migrated apps.
Hmm, weird, as I'm testing out master with Django 1.7.7, and createdb runs
okay without the settings flag (only getting the test runner warning).
However, createdb fails with Django 1.8, but others have noted that it has
to do with some changes in the management command API. May be worth to
Here's my take on the createdb issue. The version checking feels dirty, but
it works. https://github.com/stephenmcd/mezzanine/pull/1247
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails
Glad you figured it out. Just be careful, as it is strongly discouraged
that you enable DEBUG in production as it exposes many sensitive
information of your server setup. See if you can get the logging or email
report approaches working instead.
--
You received this message because you are
Thanks, Federico. I'm really interested in getting feedback on the
deployment process and the new documentation, so please share your
experience when ready :)
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group and
Hey Lou. Are you running the development server or a production
installation? If you're in your local development machine, make sure DEBUG
= True in your local_settings.py module to get the full traceback in the
development server. If you're in production, see if you've configured any
logging
Thanks to all for your kind words and support through-out, it's one of the
reasons that make this community so special.
I just want to point out that the PR included a mini-tutorial in the
Deployment section of the docs (see here
Hello Dennis. I actually needed to do this for a project a few years ago.
As far a I know, Mezzanine doesn't support multiple blogs out of the box.
What I did was create a Blog model, which simply had a slug and title,
and then add it as FK to the standard BlogPost and BlogCategory models.
Ok, PR sent :) https://github.com/stephenmcd/mezzanine/pull/1216
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
Hey Josh, thanks a lot, but I think I'll just build on top of the mercurial
code present in the current fabfile.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
It looks to me like you could use some sort of user profile. Mezzanine
(Django, really) supports associating a profile model to each User object.
In this profile model you can define as many fields of any kind as you like
(as you'd do with any model). Mezzanine's docs contain a useful overview
Gotcha. Well, guess we better support hg for completeness sake (and
it'll be useful for me to learn).
The rollback task will work as usual for VCS users, but I don't really
know what to do in case of rsync. Ideas:
* No rollback support if DEPLOY_METHOD = rsync
* Gzip the whole project
Hey everybody, quick question: is mercurial support in the fabfile very
important? The new fabfile uses direct pushes to the server instead of
pulls from external sites, and this is something I've only tested with git,
and I was wondering if we can drop mercurial support on the fabfile
Hey Tomlin, thanks for your kind words, it's great to see the project being
helpful.
I've made important progress refactoring Mezzanine's default fabfile, I
hope it'll be ready soon. I also have plans to make a screencast explaining
the deployment of Mezzanine, as it is one of the common
Got it. I'll get to it soon.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit
Hi Graham. Why do you say this needs to happen before pre-save? The idea of
that signal is that it let's you do anything you wish before inserting data
into the DB. If you found out that the Title is not unique, you can raise
the appropriate errors and abort the save until the user corrects the
I did a quick test and commenting line 2 works alright.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more
Currently only the development version. You'll need to clone from the repo
to get Django 1.7 support.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
At the end of the day, theming a Mezzanine/Django site is a matter of
loading the correct scripts and stylesheets. It seems like
django-bootstrap-themes uses some custom template tags to do so. The demo
website (http://mezzanine.jupo.org/blog/) used to have a theme-switching
widget, perhaps
Hey Stephen, I tried the latest version of Mezzanine with one of my sites
and all went smoothly. It just required following Django's instructions
https://docs.djangoproject.com/en/1.7/topics/migrations/#libraries-third-party-apps
for the new built-in migrations. After that, the database was up
Just to clarify, I followed Django's instructions in my own project, didn't
have to touch Mezzanine at all.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hey, so Django 1.7 has just been officially released. From what I gather
from the GitHub issue linked by Steve, all works fine in Mezzanine. I
wanted to ask how are migrations going to work now. Since we are supporting
Django 1.5 and 1.6, does that mean we will support both South and the new
Thanks for your answer, Thomas. I'll try to migrate some of my sites to 1.7
and report back how it goes.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
By the way, the page I've translated so far is Admin Customization.
2014-08-21 4:44 GMT-06:00 Stephen McDonald st...@jupo.org:
Awesome! I'll try and work out how to build html from that shortly.
On Thu, Aug 21, 2014 at 9:47 AM, Eduardo Rivas jerivasmel...@gmail.com
wrote:
Ok, so I got
Hello everyone. I created a fabfile that deploys Mezzanine sites to
Webfaction. It is not a drop-in replacement for the one provided with
Mezzanine (I'm planning on releasing one since I've moved to hosting my
sites on a VPS). Anyways, the point is that I've managed to drop
gunicorn_django
Thanks a lot Steve for setting everything up! I'll give it a shot as
soon as I can.
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I don't have experience with Sphinx, but I found this
http://sphinx-doc.org/intl.html. Apparently you can generate translation
catalogs in gettext, so we could use Transifex as we already do with
Mezzanine. Here is a blogpost
Hi Paul. It seems like you sorted out the issue you were linking too. Are
there any others?
I finally found some time to come back to this, and noticed the front-end
language selector is gone. The problem is in the condition for rendering the
template
Yeah, I've got the pull request ready, but the dropdown on which you select
the repo you want to compare your changes with won't list Mathias' fork of
Mezzanine.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group
Hey Luigi. By default, Django Compressor will simply concatenate (join)
your static files. This is good because it will save HTTP requests to your
site, and your visitors will get all your static files in one request
(instead of many). If you also want to minify your files (remove whitespace
Hi Matt. Mezzanine supports user access control in a self-service
configuration that might be useful for you. You can have your users request
an account (fill in their details and password), but they will not be
granted access to the site (they can't log in) until an authorized member
clears
Also, my explanation is really just a rephrasing of what you can find in
the official docs:
http://mezzanine.jupo.org/docs/user-accounts.html#account-approval. In that
page you'll also find info about the more traditional Click here to verify
your account approach, and details on Mezzanine's
Great, 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
Just saw 3.1.7 got pushed to PiPy. Any news on that? :)
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more
I couldn't tell. Webfaction is the only hosting provider I've used so
far.
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Well, a Webfaction account is essentially a VPS with limited permissions
and a bunch of stuff preinstalled, so what you can do with it depends on
how well you use your RAM, bandwidth and disk space. A good thing about
Webfaction is that the database server (Postrges or MySQL) and Nginx server
Thanks for the interest guys. Ibn, I recommend you take a look at the
Webfaction docs and read the fabfile to have an idea of what it does. Some
knowledge of Postgres and Git will also be useful. Finally, when you
deploy, keep in mind many settings have default values in fabsettings.py,
so
Awesome news, and really looking forward for 3.2!
I have some questions regarding thumbnails in RichText fields. What size
will they be? Can they be configured in some way by content editors, or
developers? I made a quick search on the docs (which already report as
3.1.5) for thumbnail and
Hey everybody. I've been trying out Mathias master branch and everything is
working smoothly. As I said, I'm also exploring ways to enable toggling
translation fields in the Admin. Turns out Model Translation (MT) provides
two admin classes (docs
Odd, I just created a project without issue. This is my venv:
Django==1.6.5
Mezzanine==3.1.3 #From Mathias' branch
Pillow==2.4.0
South==0.8.4
argparse==1.2.1
bleach==1.4
django-debug-toolbar==1.2.1
django-modeltranslation==0.7.3
filebrowser-safe==0.3.3
future==0.9.0
grappelli-safe==0.3.10
I should have read the whole Stack Overflow thread! It looks like Django
has built in ways of doing it.
https://docs.djangoproject.com/en/1.6/topics/testing/tools/#overriding-settings
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To
I think you can access the settings module like every other place in the code
base. This example recommends the setup and teardown methods for modifying
settings in unit tests: http://stackoverflow.com/a/913596. Hope that helps :-)
--
You received this message because you are subscribed to
Great! Hopefully your commits will be merged soon and I'll work over that.
--
You received this message because you are subscribed to the Google Groups Mezzanine
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Have you collected your static files? Make sure you run collectstatic on
every deployment, and all Mezzanine resources will be made available for
production.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and
Actually, the CACHE directory and the files with random letters and numbers
are created by Django Compressor (via the {% compress %} template tag). It
bundles all your static assets and serves them in a single file to avoid
multiple HTTP requests. You might want to disable it to get your files
Aaaahh, I get what you mean for #1, and yes, changing the value in
non-default languages to something other than the direct translation of
Submit fixes it.
#2 and #4 look like they've been fixed, thanks a lot.
#5 is looking pretty great. However, I don't thinks SHOP_CURRENCY_LOCALE
should be
Sorry, I didn't understand your explanation on point 1. Could you
elaborate a little bit more? The issue I was describing is that the
Submit button is not showing the active language text in the form, but
rather the default language value.
About number 2, I actually had this working a while
Ok, I finally got some time to try this out. I've never used Model
Transaltion, so maybe I'm making some noob mistake. This is what I've done:
mkvirtualenv modeltranslation
git clone https://github.com/Kniyl/mezzanine.git mt-mezzanine
cd mt-mezzanine
pip install -e .
pip install south
Just before running createdb, one has to cd mt_test, of course.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
Yep, that's it. Removing debug toolbar fixes it.
I'll continue testing and reporting back anything I find. Thanks a lot for
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
I checked out the DB and the content_model of those pages is not
category, but rather richtextpage, form or link, as expected.
However, the table shop_category did have some demo categories with ids
matching those of the pages in question. I will test later if deleting
Product Categories from
As I understand, Sales can be applied either to individual Products, or to
whole Categories. However, there's something about Category-wide Sales that
confuses me. If you create a Sale from the Sales admin and apply it to a
Category, the changes are ignored until you go to the Page admin and
Hello! I'm developing a site with Cartridge and I've noticed that all Pages
in my page tree appear as valid categories for a Product. See the attached
screenshot. The expected outcome is that only those Pages that start with
Collections should be selectable as Categories for a Product (as they
I've really been looking forward to this one. Hopefully I will have time to
try it out with the development version of some sites that currently use
alternative translation approaches.
Are we going to translate urls at all? Django gives two possible choices:
mark the url patterns for
201 - 300 of 321 matches
Mail list logo
