-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uninitialized constant ActiveMerchant::Billing::Integrations::Helper (NameError) #1357
Comments
This is due to integrations being extracted to the offsite_payments gem, but we have a compatibility layer that should let it still work. Can you give me a full stack trace so I can try to figure out why the compatibility layer's not working? |
Gemfile: gem "activesupport", "~> 4.2.0.beta1"
gem "activerecord", "~> 4.2.0.beta1"
gem 'activemerchant', "~> 1.44.0", :require => 'active_merchant' Gemfile.lock: activemerchant (1.44.0)
active_utils (~> 2.2.0)
activesupport (>= 3.2.14, < 5.0.0)
builder (>= 2.1.2, < 4.0.0)
i18n (>= 0.6.9)
json (~> 1.7)
nokogiri (~> 1.4)
offsite_payments (~> 2.0.0) full stack trace:
/vagrant_data/apps/mobile-api/lib/payment/integrations/mdpay/helper.rb: line 10 ...
class Helper < ActiveMerchant::Billing::Integrations::Helper
... |
@ZhangHanDong looks like you have a custom integration there; I would not expect it to work after an upgrade unless you adapt it to https://github.com/Shopify/offsite_payments. We built backwards compatibility for all built-in integrations in ActiveMerchant, but were not able to cover the case of external sub-classes. I'd recommend either locking ActiveMerchant to the last version, or tweaking your integration to use https://github.com/Shopify/offsite_payments. Sorry for the trouble! |
Thanks. I have locked ActiveMerchant to 1.43.3. |
… offsite_payments issue: activemerchant/active_merchant#1357
Hello, bin/rails server -d -p3005 |
gem 'activemerchant', "~> 1.44.0", :require => 'active_merchant'
No such problem when i use version 1.43.3
The text was updated successfully, but these errors were encountered: