Membership Plugin causes failed rebuilds

This seems to have happened somewhere in the last 4 Months as today (after 4 months) I was upgrading one of my discourse installs for a customer, Discourse is built against tests-passed so it seems like something in core has changed that is causing builds to fail.

2 Likes

I agree. Found this bug also.

1 Like

Was the solution found by anyone? We are getting

Gem::ConflictError: Unable to activate stripe-3.28.0, because faraday-1.0.1 conflicts with faraday (~> 0.10)

Memberships requires gem 'stripe', '3.28.0', which in turns requires the faraday ~> 0.10.

It appears Discourse now requires the 1.0.1 shown.

Is Membership compatible with > Stripe 5.0, which appears to have removed the Faraday dependency?

UPDATE: Tried to require Stripe 5.0.1 (+ the 1/16/20 commit) and got:

> TypeError: Discourse.Route is undefined
> Url: https://staging.gomomentum.org/assets/plugins/procourse-memberships-0f9c4c358aa6ca7a71c4fb9f2f7dbfbac3f8aeb3afc6abb19532525176b6c4b0.js
> Line: 1
> Column: 1405
> Window Location: https://staging.gomomentum.org/admin/plugins

Can you offer any direction at all?

Plugin requires an overhaul. It cannot be used in it’s given state. We will either have to fix it or sponsor someone to fix it for us.

1 Like