Mezzanine 1.3 and Cartridge 0.7 released

127 views
Skip to first unread message

Stephen McDonald

unread,
Dec 25, 2012, 10:35:16 PM12/25/12
to mezzani...@googlegroups.com
Hi all,

I've just released Mezzanine 1.3 and Cartridge 0.7! As discussed recently, these releases contain changes for one of the longest periods between releases to date, with the largest number of changes yet smallest number of new features - a really good sign for the project.

Please make sure to run migrations when upgrading - if you've subclassed Displayable you will also need to generate new migrations and run them for your models.

Here's an overview of what's new:

Project:

- Full support for Django 1.5
- Improved support for Lettuce test runner
- Improved support for django-compressor 
- Updated to latest client libraries (jQuery/jQuery UI/Boostrap)
- All previous versions now tagged in GitHub/Bitbucket
- Separation of mandatory and optional fixtures during installation
- Configurable upload_to handlers per file fields
- Configurable spam filters (previously akismet only)
- Configurable "search in" options in public search form
- Support for custom markup formats in content description generation
- Support for custom markup formats in comment rendering
- Multi-tenancy now supports is_staff across Django Admin and live-editing 
- Multi-tenancy support in sitemaps
- Support for excluding pages/content from sitemaps

Deployment:

- JVM/Jython compatibility
- Improved automated deploys: locale and ssl config fixes

Pages:

- Improved drag/drop support for reordering the page tree

Forms:

- New DOB field type in the forms builder app
- Support for custom field types in the forms builder app

Blogs:

- More granular template blocks throughout the blog app
- Recent posts template tag in blog app supports tag/category filtering
- Next/previous blog post in blog detail view- Ownable model filtering in Django Admin now configurable

Shop (Cartridge):

- New payment handler for Stripe
- Better support for currency locale on Windows

That's it! A big thanks to everyone who has contributed features and fixes, provided community support, and for sharing the awesome sites they've built using Mezzanine and Cartridge.

--
Stephen McDonald
http://jupo.org

Josh Cartmell

unread,
Jan 7, 2013, 2:15:24 PM1/7/13
to mezzani...@googlegroups.com
The migrate command requires you have to install South.  First revert to the version of mezzanine you were using prior to the upgrade.  Then install south and sync you database (that creates the south tables):
python manage.py syncdb

Next you have to fake the migrations that were present in the version of Mezzanine you started with (since the database is already up to the point of whichever version of Mezzanine you created it with south doesn't need to try to run the migrations again):
python manage.py migrate --fake

Now upgrade mezzanine and run the migrations:
python manage.py migrate

That might not all be exactly right (I think it is though) but it give's you an idea of what you need to do.

On Mon, Jan 7, 2013 at 11:06 AM, Max Resnick <max.r...@gmail.com> wrote:
Hi All -

Can someone give me some tips on completing this upgrade  I've seen coments about using "python manage.py migrate" but that doesn't seem to work, actually the command doesn't list using the -help switch. 

I dropped in the new update, and now I get "current transaction is aborted, commands ignored until end of transaction block" when trying to runserver.  

I've also run createdb and syncdb. 

Thanks, and I apologize if this a dumb question.  At this point I really haven't done much with my site, I can easily just start over, but I really don't want to.

Thanks!!!
Max

Tom Brander

unread,
Feb 23, 2013, 11:52:39 AM2/23/13
to mezzani...@googlegroups.com
Just a note that this was very helpful for the update to Mezzanine 4.1.2 A few other notes that could help someone..

Another point for me was,, Copy virtual env using the "cpvirtualenv oldone  newone" commane (see vitual env wrapper doc)
Then do easy_install -U mezzanine cartridge (to the new virtual env)

(I made a copy of my DB file both before and after running syncdb and south)

use the old virtual env  and use south as below, then switch to the new one and run python manage.py migrate

And run python mange.py runserver and you should be back in business.. (and updated!)

Tom Brander

unread,
Feb 23, 2013, 11:54:11 AM2/23/13
to mezzani...@googlegroups.com
Duh Mezzanine 1.4.2
Reply all
Reply to author
Forward
0 new messages