Closed
Bug 1041552
Opened 11 years ago
Closed 10 years ago
[traceback] ImproperlyConfigured: The provider bango is not one of the allowed PAYMENT_PROVIDERS
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mat, Unassigned)
References
()
Details
When viewing an account with a bango payment account set up on dev (like https://marketplace-dev.allizom.org/lookup/user/4771218/summary ), we get:
http://sentry.dmz.phx1.mozilla.com/marketplace-dev/marketplace-dev/group/20124/
Traceback:
mkt.developers.providers in get_provider
ImproperlyConfigured: The provider bango is not one of the allowed PAYMENT_PROVIDERS.
Stacktrace (most recent call last):
File "django/core/handlers/base.py", line 112, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "newrelic/hooks/framework_django.py", line 492, in wrapper
return wrapped(*args, **kwargs)
File "amo/decorators.py", line 32, in wrapper
return func(request, *args, **kw)
File "amo/decorators.py", line 32, in wrapper
return func(request, *args, **kw)
File "amo/decorators.py", line 62, in wrapper
return f(request, *args, **kw)
File "mkt/lookup/views.py", line 86, in user_summary
provider_portals = get_payment_provider_portals(user=user)
File "mkt/lookup/views.py", line 543, in get_payment_provider_portals
provider = get_provider(id=acct.payment_account.provider)
File "mkt/developers/providers.py", line 460, in get_provider
'allowed PAYMENT_PROVIDERS.'.format(p=provider.name))
Filed under Payments and not Admin Tools because I'm not sure how to properly fix it. Using get_provider() here seems to be the right thing to do, is there a nice, clean way to avoid the error while still displaying the info from the payment account ?
Updated•11 years ago
|
Priority: -- → P4
Comment 1•10 years ago
|
||
Based on the recently announced future plans for the Marketplace to remove payments, closing these bugs.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•