Upgrading Satchmo - Hints/Tips

0 views
Skip to first unread message

mikeho...@googlemail.com

unread,
Oct 7, 2008, 4:59:43 AM10/7/08
to Satchmo users
Hi guys

About a year ago I started looking at Satchmo (0.6 at the time) and
got working on a demo site straight away.

At the time I pretty much rolled my sleeves up and got stuck in not
really giving much thought to upgrading in the future. As times gone
on I've hacked at Satchmo quite alot (templates, views and models) and
am beginning to feel a little uncomfortable at the thought of
upgrading.

Before I begin upgrading I think its probably going to be the least
painful if I checkout a fresh copy of 0.6 diff the changes against my
current working copy unpick what I've done and then look at upgrading
to future versions of Satchmo.

Whats the common wisdom on seperating things out to prevent this
happening again?

- models -> custom apps and use inheritance to add additional fields
etc?
- views -> override view behaviour
- templates -> define alternative templates in local_settings

mikeho...@googlemail.com

unread,
Oct 7, 2008, 5:23:12 PM10/7/08
to Satchmo users
Anyone got any thoughts on this?

Looking through things a little more this evening I've got about 24
files I've made some sort of modification to and to be honest it isn't
anywhere near as bad as I'd initially thought.

Models - fine just inherit and add/override as necessary.
Views - just wrap these in another view or rewrite dependent upon
requirements
Templates - shouldn't be a problem once I've configured
local_settings.py


Urls - whats the common wisdom on adding/removing/changing as
required, looks like thisis just a list of tuples so should be
relatively straightforward to add/remove but what about finding and
replacing as required.

Urls - Hmm any tips on this

On Oct 7, 9:59 am, "mikehowar...@googlemail.com"

Chris Moffitt

unread,
Oct 7, 2008, 8:31:18 PM10/7/08
to satchm...@googlegroups.com


Urls - whats the common wisdom on adding/removing/changing as
required, looks like thisis just a list of tuples so should be
relatively straightforward to add/remove but what about finding and
replacing as required.

Urls - Hmm any tips on this

There are probably others with more experience on this but I don't think there's a problem changing URL files around. Since they are mostly just pointing to views, there should be little concern about modifying them and managing the upgrade process.

Other probably have even more tips but so far it sounds like you're doing things the right way.

-Chris

mikeho...@googlemail.com

unread,
Oct 8, 2008, 4:12:07 AM10/8/08
to Satchmo users
Thanks for the reply Chris.

Just want to make sure that I do everything right this time round to
prevent any future heartache. Reading some of Bruce's comments he
seems fairly confident that pretty much everything can be done using
inheritance, middleware and careful use of url overiding which is
pleasing to hear.
Reply all
Reply to author
Forward
0 new messages