After thinking about it a little more, I think the reason is that the getpaid.authorizedotnet payment processor gets conditionally loaded by Products.PloneGetPaid and my understanding is that this happens after the other zcml is loaded and therefore my overrides.zcml gets loaded first and then the actual getpaid.authorizedotnet configure.zcml gets loaded next and hence there's a conflict. In my test fixture, though, the getpaid.authorizedotnet configure.zcml gets loaded *first* and then my overrides.zcml gets loaded after this hence no issues. Any ideas on how to work around this, i.e. other than patching the getpaid.authorizedotnet itself?
Thanks, Tim On Fri, 2010-04-23 at 20:31 +1200, Tim Knapp wrote: > Just further to this, I managed to get this going using the suggestion > from David below (thanks!) and it all works fine in my integration test > but when I start up the production instance I get a Conflict Error as > I've overridden the Authorize.Net payment processor in an > overrides.zcml. Any idea why this doesn't work or how I can get it to > work? (P.S. I have tried using z3c.unconfigure too but that didn't work > either) > > Thanks, > Tim > > On Thu, 2010-04-15 at 22:51 -0700, David Glick wrote: > > On 4/15/10 10:45 PM, Tim Knapp wrote: > > > Hi, > > > > > > Just picking up on this thread again as I'm *actually* implementing this > > > now. I'm actually (selfishly) only interested in getting this to work > > > rather than developing a more generally useful solution. Looking at the > > > code here[1] if I just override the processor adapter in an > > > overrides.zcml and modify the processor function to return different > > > options dependent on contents of the order would this work. > > > > > > thanks, > > > tim > > > > > > [1] > > > http://code.google.com/p/getpaid/source/browse/getpaid.authorizedotnet/trunk/src/getpaid/authorizedotnet/authorizenet.py > > > > > Yes, I think so, as long as you can make sure an order doesn't contain > > multiple items that need to be processed with different accounts. It's > > a similar approach to what the recurring billing branch does > > (authorize.net has a separate API for recurring payments). > > David > > > > -- GetPaid for Plone: http://www.plonegetpaid.com (overview info) | http://code.google.com/p/getpaid (code and issue tracker) You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@googlegroups.com To unsubscribe from this group, send email to getpaid-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en?hl=en
