I just worked through some changes to one of my custom payment modules
that broke after upgrading. It looks like your config file is wrong
now.
PAYMENT_MODULES = config_get('PAYMENT', 'MODULES')
That won't work any more, since the payment modules aren't configured
in livesettings now. I fixed my module by looking at the authorizenet
module's config. In particular, drop the line above and also remove
the
requires=PAYMENT_MODULES,
line. You might need to make other changes too.
Hope that helps,
Alex
--
Alex Robbins
5Q Communications, Inc.
http://www.5Qcommunications.com/
[email protected]
800-747-4214 ext 913 (p)
http://www.ask5q.com/twitter/
On Tue, Apr 13, 2010 at 4:30 PM, Chris Moffitt <[email protected]> wrote:
> Is beanstream on your path?
>
> When you do a python manage.py shell
> import beanstream
>
> Does it work or give you import errors?
>
> -Chris
>
> On Tue, Apr 13, 2010 at 2:05 PM, John S <[email protected]> wrote:
>>
>> I also tried to integrate the beanstream module (as well as website
>> payment pro) to try to jumpstart my own custom payment module
>> development. I've run into the very same problem - It does not show
>> up in "/settings/" and therefore I can't enable it.
>>
>> 1. There are no errors in my satchmo.log,
>>
>> 2. I have added the module to INSTALLED_APPS in settings.py.
>>
>> 3. Also in settings.py I have added the module to the
>> CUSTOM_PAYMENT_MODULES list in the SATCHMO_SETTINGS dict, like so:
>> SATCHMO_SETTINGS = {
>> 'SHOP_BASE' : '',
>> 'MULTISHOP' : False,
>> 'CUSTOM_PAYMENT_MODULES' : ['beanstream']
>> }
>>
>> 4. I made sure the the config.py file was set up as described in the
>> documentation:
>>
>> from satchmo.configuration import *
>> from livesettings import *
>> from django.utils.translation import ugettext_lazy as _
>>
>> # this is so that the translation utility will pick up the string
>> gettext = lambda s: s
>>
>> PAYMENT_MODULES = config_get('PAYMENT', 'MODULES')
>> PAYMENT_MODULES.add_choice(('PAYMENT_BEANSTREAM', 'beanstream'))
>>
>> PAYMENT_GROUP = ConfigurationGroup('PAYMENT_BEANSTREAM',
>> _('Beanstream Payment Settings'),
>> requires=PAYMENT_MODULES,
>> ordering = 200)
>>
>> config_register_list(
>>
>> ...and so on...
>>
>> 5. I made sure that the modules.py was set up as described in this
>> thread by David Marcin
>>
>> import config
>> PAYMENT_PROCESSOR=True
>>
>>
>>
>> David or anyone else kind enough to help me: do you have any idea what
>> I am doing wrong?
>>
>>
>>
>>
>> On Apr 11, 5:23 pm, David Marcin <[email protected]> wrote:
>> > I think I found the problem by looking at the existing modules. The
>> > package
>> > I downloaded didn't have the following in models.py, which is apparently
>> > now
>> > required:
>> > import config
>> > PAYMENT_PROCESSOR=True
>> >
>> > Also, it appears that CUSTOM_PRODUCT_MODULES is no longer required
>> > (probably
>> > because of the models.py lines?) so the docs ought to be updated to
>> > reflect
>> > this.
>> >
>> > David
>> >
>> > On Sun, Apr 11, 2010 at 5:14 PM, Chris Moffitt <[email protected]>
>> > wrote:
>> > > Take a look in your satchmo.log file and see if you see any errors. I
>> > > suspect there's an error somewhere in your module and when you try to
>> > > import
>> > > it, it errors causing satchmo not to present it.
>> >
>> > > -Chris
>> >
>> > > On Sun, Apr 11, 2010 at 6:51 PM, David Marcin <[email protected]>
>> > > wrote:
>> >
>> > >> Hi satchmo-users,
>> >
>> > >> I want to write a custom payment module. I decided to start by
>> > >> quickly
>> > >> integrating the beanstream module from
>> > >>http://daniel.shortens.net/weblog/satchmo. Unfortunately I can't seem
>> > >> to
>> > >> get the beanstream configuration options to show up. I have included
>> > >> store.beanstream in INSTALLED_APPS and added 'CUSTOM_PAYMENT_MODULES'
>> > >> :
>> > >> ('store.beanstream') to SATCHMO_SETTINGS, but it appears to have no
>> > >> effect.
>> > >> There is no configuration page when I go to localhost:8000/settings.
>> >
>> > >> Have I done something wrong in integrating the module?
>> >
>> > >> David
>> >
>> > >> --
>> > >> 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]<satchmo-users%[email protected]>
>> > >> .
>> > >> For more options, visit this group at
>> > >>http://groups.google.com/group/satchmo-users?hl=en.
>> >
>> > > --
>> > > 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]<satchmo-users%[email protected]>
>> > > .
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/satchmo-users?hl=en.
>>
>> --
>> 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.
>>
>
> --
> 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.
>
--
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.
