# ProCourse Memberships 💸 **URL:** \ **Category:** Plugin\ **Tags:** broken\ **Created:** [2017年二月17日 17:14 UTC](https://meta.discourse.org/t/procourse-memberships/57558 "2017-02-17T17:14:34Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![joebuhlig](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joebuhlig/32/193054_2.png) [@joebuhlig](https://meta.discourse.org/u/joebuhlig)\ **Post date:** [2018年十一月13日 13:38 UTC](https://meta.discourse.org/t/procourse-memberships/57558/43 "2018-11-13T13:38:51Z")
Big thanks to @Steven here for the French translation. 🤗 [https://github.com/procourse/procourse-memberships/pull/7](https://github.com/procourse/procourse-memberships/pull/7) ---
**Author:** ![outofthebox](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/outofthebox/32/83708_2.png) [@outofthebox](https://meta.discourse.org/u/outofthebox)\ **Post date:** [2018年十一月14日 16:37 UTC](https://meta.discourse.org/t/procourse-memberships/57558/44 "2018-11-14T16:37:44Z")
Hi @joebuhlig, You and your team have done an outstanding job with this plugin! Thank you for all your hard and excellent work!! ---
**Author:** ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven)\ **Post date:** [2018年十二月5日 16:04 UTC](https://meta.discourse.org/t/procourse-memberships/57558/45 "2018-12-05T16:04:21Z")
It seems there is a bug since this weekend, when I edit an existing membership, everything is fine and works as usual. But since this weekend, when I create a new membership, I can’t save it and when I refresh the page the name is always blank > ![image](https://global.discourse-cdn.com/meta/original/3X/0/a/0a1f11a52725a65ad09e8f7157d268c8e8d714e9.png) > I can’t save the modifications > > ![image](https://global.discourse-cdn.com/meta/original/3X/c/5/c58013539b8017696ad4b9f7f6ac2e873f5c194c.png) > On the left column, the title of the new membership sstays blank There is nothing on /logs Anyone alse noticed this? I have this plugin on only one forum, so it maybe be related to something else. I’ll try to load this plugin only if no one else can repro ---
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [2018年十二月5日 16:28 UTC](https://meta.discourse.org/t/procourse-memberships/57558/46 "2018-12-05T16:28:17Z")
What version of Discourse are you running? When did you last update? I will try to reproduce this later today. ---
**Author:** ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven)\ **Post date:** [2018年十二月5日 17:31 UTC](https://meta.discourse.org/t/procourse-memberships/57558/47 "2018-12-05T17:31:07Z")
I did two upgrades, saturday, and last night. In both the bug occurred. It may have happened before but I didn’t notice. Right now, the forum is on this commit : [https://github.com/discourse/discourse/compare/ba762ea...tests-passed](https://github.com/discourse/discourse/compare/ba762ea...tests-passed) ---
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [2018年十二月5日 18:28 UTC](https://meta.discourse.org/t/procourse-memberships/57558/48 "2018-12-05T18:28:40Z")
I just ran this process on a test server I just upgraded to v2.2.0.beta5 +67 and wasn’t able to reproduce the behavior. What gateway are you using? It could be an issue there as a couple of the gateways do some background processing with the payment processor upon level creation. ---
**Author:** ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven)\ **Post date:** [2018年十二月5日 19:09 UTC](https://meta.discourse.org/t/procourse-memberships/57558/49 "2018-12-05T19:09:15Z")
I’m using Stripe in test mode. I tried with Paypal, still the same issue. I’ll try with other plugins deactivated. ---
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [2018年十二月6日 15:01 UTC](https://meta.discourse.org/t/procourse-memberships/57558/50 "2018-12-06T15:01:03Z")
How did things shake out with other plugins deactivated, @Steven? ---
**Author:** ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven)\ **Post date:** [2018年十二月6日 15:20 UTC](https://meta.discourse.org/t/procourse-memberships/57558/51 "2018-12-06T15:20:28Z")
Same problem, I tried another gateway, deactivating the theme. I don’t have any idea how it could affect the forum. I can give you an access to the forum if you want to check some things ---
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [2018年十二月6日 16:22 UTC](https://meta.discourse.org/t/procourse-memberships/57558/52 "2018-12-06T16:22:11Z")
Do you have the correct test API keys loaded for Stripe? ---
**Author:** ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven)\ **Post date:** [2018年十二月6日 16:34 UTC](https://meta.discourse.org/t/procourse-memberships/57558/53 "2018-12-06T16:34:35Z")
Oh damn, I just found the solution, it was a stupid mistake on my part. So sorry about that 😓 ---
**Author:** ![Joshua\_Kogan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joshua_kogan/32/127595_2.png) [@Joshua\_Kogan](https://meta.discourse.org/u/Joshua_Kogan)\ **Post date:** [2018年十二月20日 21:18 UTC](https://meta.discourse.org/t/procourse-memberships/57558/54 "2018-12-20T21:18:11Z")
A related question: how can I allow non-group members to see the topic posts (in list format), but if they click on the topic, they can’t access the post, until they pay and become a member of the group? I want non-group members of my site to see all of the topics (in the list format), with the hope that it will entice them to pay to access the posts. ---
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [2018年十二月21日 01:05 UTC](https://meta.discourse.org/t/procourse-memberships/57558/55 "2018-12-21T01:05:02Z")
The [ProCourse Teaser](https://github.com/procourse/procourse-teaser) plugin does that. It’s set at the category level so any post in that category shows up in the topic list but allows the ability to redirect to another page if the user doesn’t have access. ---
**Author:** ![Joshua\_Kogan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joshua_kogan/32/127595_2.png) [@Joshua\_Kogan](https://meta.discourse.org/u/Joshua_Kogan)\ **Post date:** [2018年十二月22日 22:33 UTC](https://meta.discourse.org/t/procourse-memberships/57558/56 "2018-12-22T22:33:01Z")
Thanks! Installed, and working perfectly. Any chance that there is a way to make a single post in that category viewable? For example, a pinned “about” category post, that let’s the user know that the content is locked, and they must join to see it. OR, do I need to use the static page plugin to be the narrative in-between category topics and the login page? ---
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [2018年十二月22日 22:35 UTC](https://meta.discourse.org/t/procourse-memberships/57558/57 "2018-12-22T22:35:55Z")
The best way is to use the static pages plugin as you mention. @joebuhlig originally designed Memberships, Teaser, and Static Pages to all work together like that. ---
**Author:** ![Joshua\_Kogan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joshua_kogan/32/127595_2.png) [@Joshua\_Kogan](https://meta.discourse.org/u/Joshua_Kogan)\ **Post date:** [2018年十二月23日 15:22 UTC](https://meta.discourse.org/t/procourse-memberships/57558/58 "2018-12-23T15:22:53Z")
Thanks! I’m off to give it a try! ---
**Author:** ![WorldIsMine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/worldismine/32/455660_2.png) [@WorldIsMine](https://meta.discourse.org/u/WorldIsMine)\ **Post date:** [2019年一月9日 10:12 UTC](https://meta.discourse.org/t/procourse-memberships/57558/59 "2019-01-09T10:12:39Z")
Received this from BrainTree: > Dear David, > > You’ve likely heard about Strong Customer Authentication (SCA) requirements, which are part of the Payment Services Directive (PSD2) regulations that came into effect early last year. We understand that there’s a lot of uncertainty around these changes, so we wanted to reach out to help you begin to prepare. > > ### What does SCA mandate? > > SCA mandates that many transactions will need to be carried out more securely using at least two of these three authentication factors: > > - Knowledge: Something you know, typically a password or PIN. > - Possession: Something you have, such as a device or credit card. > - Inherence: Something you are physically, typically a fingerprint or other biometric. > > ### What do I need to do? > > Moving to 3D Secure 2.0 (3DS 2.0) can help merchants transacting in Europe meet SCA requirements as well as help enhance fraud protection. 3DS 2.0 is also expected to reduce friction in both the web- and mobile-purchase process and can help increase conversions. > > ### When is the deadline? > > Although the date of enforcement isn’t until September 2019, Braintree recommends that merchants be ready to integrate 3DS 2.0 into their checkout experience by April 2019 per the card brands’ guidelines. Will this plugin be affected by this? ---
**Author:** ![joebuhlig](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joebuhlig/32/193054_2.png) [@joebuhlig](https://meta.discourse.org/u/joebuhlig)\ **Post date:** [2019年一月9日 19:32 UTC](https://meta.discourse.org/t/procourse-memberships/57558/60 "2019-01-09T19:32:47Z")
> [@WorldIsMine](#): > > Will this plugin be affected by this? Yes. We have this on our radar. As it stands, Braintree doesn’t seem to have their end prepared for it yet. But we’ll need to make some updates once they nail down the requirements. ---
**Author:** ![WorldIsMine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/worldismine/32/455660_2.png) [@WorldIsMine](https://meta.discourse.org/u/WorldIsMine)\ **Post date:** [2019年一月9日 22:14 UTC](https://meta.discourse.org/t/procourse-memberships/57558/61 "2019-01-09T22:14:00Z")
Thank you for the prompt answer \<3 ---
**Author:** ![kimardenmiller](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kimardenmiller/32/119631_2.png) [@kimardenmiller](https://meta.discourse.org/u/kimardenmiller)\ **Post date:** [2019年一月27日 00:34 UTC](https://meta.discourse.org/t/procourse-memberships/57558/62 "2019-01-27T00:34:37Z")
Is there any way to use or modify this plugin to allow manual subscription update, if say payment were received via some unsupported method, by paper check, etc? Is there any provision for alerting a user before a subscription expires, e.g. so they could send in a manual form of payment before membership lapses? [上一頁](https://meta.discourse.org/t/procourse-memberships/57558.md?page=2) [下一頁](https://meta.discourse.org/t/procourse-memberships/57558.md?page=4)