On Wed, Dec 23, 2009 at 4:52 AM, Leonig Mig <[email protected]> wrote:
> > I can see the real way to add new and custom functionality would be > via the "signals" mechanism rather than overriding some class or > hacking the underlying code. That's a good decoupled design, I'm > encouraged to continue evaluating satchmo as I think it could be a > nice fit for what I want to do. > Yes, most of the time you can do everything via signals. We strongly discourage forking the core Satchmo files via hacks, as it makes upgrading an iffy and difficult proposition. > My main concern is disabling features I do not need. Three concrete > examples: > > 1. Subscription stuff. > 2. Discount codes. > 3. Multisite - I will never need multisite. > The subscription stuff is disabled by not having the satchmo_ext.newsletter module activated. All the existing templates work automatically with it removed. Discount codes. They are part of the core Product models, but if you want to disable them, just don't refer to them in your templates. If you don't even want them in your admin, then in one of your admin.py files, do this: from product.models import Discount admin.site.unregister(Discount) Multisite. Can't really be removed, since "site" is a field on very many core modules. However, we'd accept a patch similar to what we did to remove translations from the admin screens on single-language sites. It wasn't that tricky, and it makes the admin interface nicer for people who don't need it. Basically, flip a setting, and your admin gets simpler. -- Bruce Kroeze http://www.ecomsmith.com It's time to hammer your site into shape. -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
