Hello, In such cases, I try to contribute my fixes to the third-party project.
If this is not possible (or until it is done), rather than copy the third party code in my project and go through the hassle of having to maintain it, I prefer monkey-patching, especially if there are only a few fixes. http://stackoverflow.com/a/6647776/662345 Regards, Antonis Antonis Christofides http://djangodeployment.com On 2016-11-03 11:11, Peter Dermott wrote: > > I'm currently working on my first Django app after years of working with > WordPress and right now I'm feeling a little lost so please be gentle. > > > I'm using the Mezzanine / Cartridge combo to set up an online store for the > company I'm working with, so far I've been extending the base cartridge models > and overriding templates to do what I need (adding extra fields, different > types of product variations etc) but over the last few days there have been a > couple of instances where I've hit brick walls. > > > The first is using the SagePay payment processor. The SagePay docs aren't > really aimed at django or python and the django-payments app I've been looking > at wants to use its own form in order to accept the card details. The > Cartridge form system is a little confusing to me and it doesn't appear to be > too friendly to messing with it. > > > The second is something even simpler where I just want to adjust the way that > product variations are output in the cart, again though the forms system was > getting in the way so I've resorted to a pretty disgusting hack to get it to > do what I need. > > > So, to the question...Would it be OK just to clone the Cartridge app in my > project and make all the overrides I need there? Would this cause massive pain > when new releases comes out? Are there any other potential drawbacks I should > be aware of and what is considered the best practice with this? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com > <mailto:django-users+unsubscr...@googlegroups.com>. > To post to this group, send email to django-users@googlegroups.com > <mailto:django-users@googlegroups.com>. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/0ccd2679-2639-44fc-8277-dba72fe46102%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/0ccd2679-2639-44fc-8277-dba72fe46102%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/99e7c0b6-484b-c022-5193-92474ec4235a%40djangodeployment.com. For more options, visit https://groups.google.com/d/optout.
