A Discourse plugin that allows payments and subscription management via Stripe.
Go to file
Rimian Perkins 1074d84901 feedback error when plan creates and updates 2019-10-31 12:41:02 +11:00
app user cancels subscription 2019-10-31 10:01:41 +11:00
assets feedback error when plan creates and updates 2019-10-31 12:41:02 +11:00
config format the amount in admin 2019-10-31 11:41:01 +11:00
db/migrate users can have more than one customer id 2019-10-30 11:22:40 +11:00
lib/discourse_patrons controller spec runs 2019-09-11 18:32:09 +10:00
spec user cancels subscription 2019-10-31 10:01:41 +11:00
test/javascripts format the amount in admin 2019-10-31 11:41:01 +11:00
.eslintrc appease eslint 2019-08-27 20:18:02 +10:00
.gitignore update .gitignore 2017-10-08 23:18:22 +01:00
.ruby-version upgrade ruby 2019-08-25 11:51:06 +10:00
.travis.yml enable discourse-plugin-ci 2019-08-27 19:52:25 +10:00
LICENSE Initial commit 2017-01-30 10:52:35 +11:00
README.md basic subscribe page 2019-10-10 13:52:55 +11:00
jsapp add success handler 2019-09-12 07:43:27 +10:00
plugin.rb list subscriptions 2019-10-29 11:43:32 +11:00

README.md

Discourse Patrons

Build Status

Accept payments from visitors to your Discourse application. Integrates with Stripe.

This is a newer version of https://github.com/rimian/discourse-donations.

Installation

Creating Subscription Plans

When users subscribe to your Discourse application, they are added to a user group. You can create new user groups or use existing ones. Of course, you should be careful what permissions you apply to the user group.

Testing

Test with these credit card numbers:

  • 4111 1111 1111 1111

Warranty

This software comes without warranties or conditions of any kind.

Credits

Many thanks to Chris Beach and Angus McLeod who helped on the previous version of this plugin.

Known issues

  • CSS is mucked up in Safari and probably Firefox too.
  • The phone number isn't sent to Stripe

TODOs

  • Confirm dialog CSS isn't the best.
  • Check against other themes (works ok with light and dark)
  • Validate the model properly. Not in the stripe component
  • Show the transaction on the thank you page.
  • Work out where to put the helper tests. Name collision!