[mezzanine-users] Login Menu with Mezzanine
Hello, I work on a project who turn in Python with Django Mezzanine, but I neet to creat a form with login, password and submit button. It will write in database and log or not into website. Do you know, how doing that ? PS : Excuse me if my english is bad, I'm French... Thanks Matthieu -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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] Newbie question: Trying to deploy mezzanine website. Gunicorn fails
I ran $ fab all It went through without any errors except during restart it said $ kill -HUP `cat /home/ebs/my_website/project/gunicorn.pid` - [46.101.48.67] out: sudo password: [46.101.48.67] out: /bin/bash: line 0: kill: (20703) - No such process [46.101.48.67] out: Fatal error: sudo() received nonzero return code 1 while executing! Requested: kill -HUP `cat /home/ebs/my_website/project/gunicorn.pid` Executed: sudo -S -p 'sudo password:' /bin/bash -l -c kill -HUP \`cat /home/ebs/my_website/project/gunicorn.pid\` Aborting. Disconnecting from 46.101.48.67... done. and now I see a 502 error on the webpage. How can I troubleshoot this error? 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.
Re: [mezzanine-users] blogroll module and/or widget?
Hi Christoph, My understanding of the term blogroll is simply a list of links to blogs the site author likes. Mezzanine does not ship with a blogroll application, but it would be a great exercise for an aspiring Python/Django/Mezzanine developer to build one. An alternative would be to take one of the existing Django blogroll applications and follow its documentation to add it to your Mezzanine project. hth! -ken On Mon, Jul 13, 2015 at 10:19 AM, Josh Cartmell joshcar...@gmail.com wrote: Hi Christoph, could you explain a bit more what you mean by blogroll? Here's what Mezzanine's blog looks like, http://mezzanine.jupo.org/blog/ (that's just random content from the test site that is editable by anyone). On Fri, Jul 10, 2015 at 11:37 AM, Christoph Pingel pingel...@gmail.com wrote: Hi, I'm new to Mezzanine, but I did a few django projects years back, I think with django 1.2 ... Is there a module for a blogroll for the mezzanine blog app? A google search on the site for 'blogroll' returned empty. Thanks for any input, best regards, Christoph // Christoph Pingel, MA • developer • pingel...@gmail.com -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. 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] blogroll module and/or widget?
Hi Christoph, could you explain a bit more what you mean by blogroll? Here's what Mezzanine's blog looks like, http://mezzanine.jupo.org/blog/ (that's just random content from the test site that is editable by anyone). On Fri, Jul 10, 2015 at 11:37 AM, Christoph Pingel pingel...@gmail.com wrote: Hi, I'm new to Mezzanine, but I did a few django projects years back, I think with django 1.2 ... Is there a module for a blogroll for the mezzanine blog app? A google search on the site for 'blogroll' returned empty. Thanks for any input, best regards, Christoph // Christoph Pingel, MA • developer • pingel...@gmail.com -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. 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 upgrade an existing Mezzanine 3.1.9 project to Mezzanine 4.0.0?
I have a site that I'll need to upgrade relatively soon. I am also planning on documenting the process and writing up a blog post about it. I don't know exactly when that will happen, but I'll try to post here when I do. On Mon, Jul 13, 2015 at 4:07 AM, Snowrry Wang snow...@gmail.com wrote: Thanks Stephen. Yes I can try the upgrade guide and document the process. On Monday, July 13, 2015 at 2:23:04 PM UTC+8, Stephen McDonald wrote: We could use a guide - would you be interested in trying the upgrade and documenting the process? On Sat, Jul 11, 2015 at 12:07 PM, Snowrry Wang sno...@gmail.com wrote: Hi, I am really excited about this 4.0 release since it uses latest django 1.7 and 1.8 which has many great things. Previously I had to start my project with Mezzanine 3.1.9 since the latest version was not stable at that time. So now my question is how can I smoothly upgrade my existing project to Mezzanine 4.0? I think there are many big changes including project directory layout, removing of south, etc. I haven't found any documentation about this yet. Thanks in advance. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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] 4.0 needs a TESTING attribute in settings.py
I just installed 4.0 and got an error AttributeError: 'Settings' object has no attribute 'TESTING' when trying to run server. Easily fixed by adding TESTING=False to settings.py. It seems to have happened to a different add-on before and there's a suggestion to add if hasattr(settings, 'TESTING'): to the code. The file where it happens is mezzaninecoremanagement__init__.py on line 12 https://code.osuosl.org/issues/6177 -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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-project mezzanine_project: error: unrecognized arguments: -a
See here for a work-around:
https://groups.google.com/forum/#!msg/mezzanine-users/q8Cu1obn2BA/JyXCXCafwdQJ
On Sun, Jul 12, 2015 at 7:45 AM, Won Jin Kim onejea...@gmail.com wrote:
Hi,
I am new user of mezzanine and catridge.
Today, I tried to install mezzanine and install catridge app, but, failed
as showing following:
# mezzanine-project -a cartridge catrshop
usage: mezzanine-project mezzanine_project [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS]
[--pythonpath PYTHONPATH]
[--traceback] [--no-color]
[--template TEMPLATE]
[--extension EXTENSIONS]
[--name FILES]
name [directory]
mezzanine-project mezzanine_project: error: unrecognized arguments: -a
# mezzanine-project --help
usage: mezzanine-project mezzanine_project [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS]
[--pythonpath PYTHONPATH]
[--traceback] [--no-color]
[--template TEMPLATE]
[--extension EXTENSIONS]
[--name FILES]
name [directory]
Creates a Mezzanine project directory structure for the given project name
in
the current directory or optionally in the given directory.
positional arguments:
name Name of the application or project.
directory Optional destination directory
optional arguments:
-h, --helpshow this help message and exit
--version show program's version number and exit
-v {0,1,2,3}, --verbosity {0,1,2,3}
Verbosity level; 0=minimal output, 1=normal output,
2=verbose output, 3=very verbose output
--settings SETTINGS The Python path to a settings module, e.g.
myproject.settings.main. If this isn't provided,
the
DJANGO_SETTINGS_MODULE environment variable will be
used.
--pythonpath PYTHONPATH
A directory to add to the Python path, e.g.
/home/djangoprojects/myproject.
--traceback Raise on CommandError exceptions
--no-colorDon't colorize the command output.
--template TEMPLATE The path or URL to load the template from.
--extension EXTENSIONS, -e EXTENSIONS
The file extension(s) to render (default: py).
Separate multiple extensions with commas, or use -e
multiple times.
--name FILES, -n FILES
The file name(s) to render. Separate multiple
extensions with commas, or use -n multiple times.
As you can see, there is no -a argument in mezzanine-project at all.
How can I install catridge shopping app with mezzanine-project command?
Thanks in advanced!!
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Stephen McDonald
http://jupo.org
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] How to upgrade an existing Mezzanine 3.1.9 project to Mezzanine 4.0.0?
We could use a guide - would you be interested in trying the upgrade and documenting the process? On Sat, Jul 11, 2015 at 12:07 PM, Snowrry Wang snow...@gmail.com wrote: Hi, I am really excited about this 4.0 release since it uses latest django 1.7 and 1.8 which has many great things. Previously I had to start my project with Mezzanine 3.1.9 since the latest version was not stable at that time. So now my question is how can I smoothly upgrade my existing project to Mezzanine 4.0? I think there are many big changes including project directory layout, removing of south, etc. I haven't found any documentation about this yet. Thanks in advance. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[mezzanine-users] Mezzanine 4.0.0 and Cartridge 0.9.5
First of all congratulations and my thanks for the Mezzanine team for
launching Mezzanine 4.0.0. I have been using the
mezzanine(3.1.10)/cartridge app for a while for a small website and
appreciate how well it has been working.
Today, i tried to create another cartridge project as per cartridge
installations and got the following
$ mezzanine-project -a cartridge cartridge_second
usage: mezzanine-project mezzanine_project [-h] [--version] [-v {0,1,2,3}]
[--settings SETTINGS]
[--pythonpath PYTHONPATH]
[--traceback] [--no-color]
[--template TEMPLATE]
[--extension EXTENSIONS]
[--name FILES]
name [directory]
mezzanine-project mezzanine_project: error: unrecognized arguments: -a
I see that stephen mentioned the following in one of the threads; I will
try if it works for me and document it.
- Create a new Mezzanine project (mezzanine-project project_name)
- Copy settings.py and urls.py from cartridge/project_template into the new
project (project_name/project_name)
- In the copied settings.py, change from local_settings import * to from
.local_settings import * (addition of a period to trigger relative import)
I had a few questions though
1- Will there be a new release of cartridge integrated with mezzanine in
near future and what would be the timeline?
2- Shall I upgrade to mezzanine 4.0.0 and django 1.8 versions for my
current deployment (Cartridge==0.9.5, Django==1.6.8, Mezzanine 3.1.10) ?
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and 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.0 with Cartridge
Fixed here: https://github.com/stephenmcd/cartridge/commit/c6aa87003d41ee203f5070f6601c81b844047e94 On Mon, Jul 13, 2015 at 2:56 PM, Stephen McDonald st...@jupo.org wrote: I can confirm this bug - the demo site doesn't hit it as it defines the SHOP_CURRENCY_LOCALE setting in its settings module. On Sat, Jul 11, 2015 at 11:49 AM, Danny molo...@gmail.com wrote: Hi all, I was wondering if anyone could help me! I've tried the new Mezzanine 4.0 release with cartridge master (which Stephen said should work) and am getting AppRegistryNotReady exception from shop.models.Priced(): BACKTRACE: /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51: 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/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/generic/fields.py:6: RemovedInDjango19Warning: django.contrib.contenttypes.generic is deprecated and will be removed in Django 1.9. Its contents have been moved to the fields, forms, and admin submodules of django.contrib.contenttypes. from django.contrib.contenttypes.generic import GenericRelation Traceback (most recent call last): File manage.py, line 14, in module execute_from_command_line(sys.argv) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/core/management/__init__.py, line 338, in execute_from_command_line utility.execute() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/core/management/__init__.py, line 312, in execute django.setup() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/__init__.py, line 18, in setup apps.populate(settings.INSTALLED_APPS) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/apps/registry.py, line 108, in populate app_config.import_models(all_models) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/apps/config.py, line 198, in import_models self.models_module = import_module(models_module_name) File /usr/lib/python2.7/importlib/__init__.py, line 37, in import_module __import__(name) File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/models.py, line 35, in module class Priced(models.Model): File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/models.py, line 41, in Priced unit_price = fields.MoneyField(_(Unit price)) File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/fields.py, line 46, in __init__ set_locale() File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/utils.py, line 103, in set_locale currency_locale = str(settings.SHOP_CURRENCY_LOCALE) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/conf/__init__.py, line 236, in __getattr__ editable_cache = self._get_editable(request=self._current_request) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/conf/__init__.py, line 152, in _get_editable editable_settings = self._editable_caches[request] = self._load() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/conf/__init__.py, line 191, in _load for setting_obj in Setting.objects.all(): File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/manager.py, line 228, in all return self.get_queryset() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/core/managers.py, line 349, in get_queryset return super(DjangoCSM, self).get_queryset().filter(**lookup) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/query.py, line 679, in filter return self._filter_or_exclude(False, *args, **kwargs) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/query.py, line 697, in _filter_or_exclude clone.query.add_q(Q(*args, **kwargs)) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1309, in add_q clause, require_inner = self._add_q(where_part, self.used_aliases) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1337, in _add_q allow_joins=allow_joins, split_subq=split_subq, File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1149, in build_filter lookups, parts, reffed_expression = self.solve_lookup_type(arg) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1035, in solve_lookup_type _, field, _, lookup_parts = self.names_to_path(lookup_splitted, self.get_meta()) File
Re: [mezzanine-users] Mezzanine 4.0 is released
On Sun, Jul 12, 2015 at 6:27 PM, henri he...@art.bieszczady.pl wrote: Happy to see Mezzanine 4.0 is released. Actually I want to start an new e-commerce project based on Mezzanine and Cartridge on which I would like to implement the new Mezzanine project structure. Is there a chance that Cartridge will be upgraded soon or is it possible to adapt Cartridge by hand to the new structure? This initially works for me: - Create a new Mezzanine project (mezzanine-project project_name) - Copy settings.py and urls.py from cartridge/project_template into the new project (project_name/project_name) - In the copied settings.py, change from local_settings import * to from .local_settings import * (addition of a period to trigger relative import) Thanks a lot for creating this great project. Regards, Henri -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Mezzanine 4.0 with Cartridge
Loosely in my head it shouldn't be, since it's something that needs to be coordinated with system administration tasks (installing locale on the server etc). I'm guessing Mathias made it editable in order to make it translatable, which in theory would allow for multiple currencies - I vaguely recall a conversation around this as well but I don't think we explored it too much. Thinking more about it, it probably won't work - the MoneyField (which all monetary values in the DB use) uses the locale to determine the precision of its underlying DecimalField - I'm pretty sure that setup would break in conjunction with modeltranslation. On Mon, Jul 13, 2015 at 3:11 PM, Danny molo...@gmail.com wrote: Thanks Stephen. Wasn't the SHOP_CURRENCY_LOCALE made editable for a reason? Personally I don't mind either way, but in the 0.9.5. tag it's not editable, but on master it was, so I'm assuming that was changed for a reason. Maybe see https://github.com/stephenmcd/cartridge/commit/79c611bd318ec095073c3b9a729b2bfa7fb4405b#diff-d3220a9516c6f9328cd3c424de02a7ef for the change? Mathias, you made this change, want to comment? Seeya. Danny. On 13 July 2015 at 15:35, Stephen McDonald st...@jupo.org wrote: Fixed here: https://github.com/stephenmcd/cartridge/commit/c6aa87003d41ee203f5070f6601c81b844047e94 On Mon, Jul 13, 2015 at 2:56 PM, Stephen McDonald st...@jupo.org wrote: I can confirm this bug - the demo site doesn't hit it as it defines the SHOP_CURRENCY_LOCALE setting in its settings module. On Sat, Jul 11, 2015 at 11:49 AM, Danny molo...@gmail.com wrote: Hi all, I was wondering if anyone could help me! I've tried the new Mezzanine 4.0 release with cartridge master (which Stephen said should work) and am getting AppRegistryNotReady exception from shop.models.Priced(): BACKTRACE: /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/utils/conf.py:51: 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/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/generic/fields.py:6: RemovedInDjango19Warning: django.contrib.contenttypes.generic is deprecated and will be removed in Django 1.9. Its contents have been moved to the fields, forms, and admin submodules of django.contrib.contenttypes. from django.contrib.contenttypes.generic import GenericRelation Traceback (most recent call last): File manage.py, line 14, in module execute_from_command_line(sys.argv) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/core/management/__init__.py, line 338, in execute_from_command_line utility.execute() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/core/management/__init__.py, line 312, in execute django.setup() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/__init__.py, line 18, in setup apps.populate(settings.INSTALLED_APPS) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/apps/registry.py, line 108, in populate app_config.import_models(all_models) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/apps/config.py, line 198, in import_models self.models_module = import_module(models_module_name) File /usr/lib/python2.7/importlib/__init__.py, line 37, in import_module __import__(name) File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/models.py, line 35, in module class Priced(models.Model): File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/models.py, line 41, in Priced unit_price = fields.MoneyField(_(Unit price)) File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/fields.py, line 46, in __init__ set_locale() File /home/danny/.virtualenvs/mez4/src/cartridge/cartridge/shop/utils.py, line 103, in set_locale currency_locale = str(settings.SHOP_CURRENCY_LOCALE) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/conf/__init__.py, line 236, in __getattr__ editable_cache = self._get_editable(request=self._current_request) File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/conf/__init__.py, line 152, in _get_editable editable_settings = self._editable_caches[request] = self._load() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/conf/__init__.py, line 191, in _load for setting_obj in Setting.objects.all(): File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/django/db/models/manager.py, line 228, in all return self.get_queryset() File /home/danny/.virtualenvs/mez4/local/lib/python2.7/site-packages/mezzanine/core/managers.py, line 349, in get_queryset
[mezzanine-users] Re: Mezzanine 4.0 is released
Congratulations to Stephen and all contributors! I look forward to upgrading soon! Thx El viernes, 10 de julio de 2015, 1:05:16 (UTC+2), Stephen McDonald escribió: Hi all, The new 4.0 release of Mezzanine is finally up on PyPI after 10 months since the last release - a lot has happened! The project site ( mezzanine.jupo.org) hasn't been upgraded yet, that will happen shortly. The full changelog is here: https://github.com/stephenmcd/mezzanine/blob/master/CHANGELOG - it has become quite unwieldy given the variety of commit styles (it's automatically generated from them), so one of the housekeeping tasks we identified upon forming the official core team was to go back and redo it manually. If you'd like to volunteer for that you'd be a superstar. Given that, here's a human written overview of what's new: - The supported Django versions are now 1.7 and 1.8 - Translatable content is now supported via django-modeltranslation - Dropped support for South, given Django 1.7's built-in migrations - TinyMCE upgraded to 4.0 (the previous version was around 3 years old!) - Major refactor of mezzanine.conf.settings resulting in greatly reduced DB queries, and removal of manual use_editable() requirement - Major refactor of bundled fabfile, allowing for non-vcs deploys via rsync, plus many more new features - We now use the same project layout that Django has for several versions, where manage.py and others live outside the project package - A gazillion bugfixes and other minor improvements There could be more - I've just put that list together by skimming the changelog. If I've missed anything noteworthy, please let everyone know in this thread. Speaking of which, if you have an issue, I'd ask that instead of replying here, you start a new email thread. If you know you've found a real bug (eg can actually confirm the problem in the code), please open a GitHub issue. A massive thanks goes out to the newly formed core team who have been the major contributors to all the above, and to everyone else who has chipped in too, on the code base and here on the mailing list with support. Thanks and enjoy! -- 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.
