I’m still reading through old threads on using WP SSO, but I was curious if sharing our roadmap might surface any advice. Are there things we should look out for? Things we should avoid?
Our Stack:
WordPress (foundation)
MemberPress (manages user accounts)
LearnDash (LMS, course creation)
Discourse (private, member community)
Our Desired Onboarding Experience:
Visitor arrives on our WP site (content marketing) & converts to paid member.
– We’re thinking about a 24-hour free trial (w/ auto-conversion).
TL0 gets read-only access to the bulk of the categories.
TL0-1 promotion requires 5 minutes posting an introduction.
After 24hrs, member’s card is charged, membership is official, auto-promoted to TL1.
WP SSO would manage accounts so that only paid/current members have access to both community and LMS content.
I’m curious if there’s either a simpler or better way to do this. Reducing new member friction is important, but so is ensuring longterm scalability, ya know?
From your onboarding list, it looks like you are hoping to override the Discourse trust level system. I think a better approach would be to use Discourse group membership to control access to your site’s content. For details about how this works, see Understanding groups and category permissions.
The WP Discourse plugin has a couple of functions that you can use to add and remove users from groups. Details are in this topic: Manage group membership in Discourse with WP Discourse SSO. That topic uses the PaidMembershipsPro plugin as an example, but the same idea should work with MemberPress.
Those threads were helpful. I’ve got WP Discourse installed and connected to Discourse. I might even have some new (better) ideas for our onboarding experience. Thank you, @simon!
I stopped short of making any SSO decisions, though. Afraid the more I read about these, the more my brain goes in circles and I get dizzy. Could I trouble you for a bit more advice on this front?
Given: WordPress & MemberPress + Discourse + LearnDash… and wanting to pay gate everything that isn’t a blog post…
If Discourse is SSO CLIENT, we’d use MemberPress to manage accounts in WordPress and access to LearnDash courses. This was how we approached things from the start, so it inherently makes sense, if not from a place of implementation/scalability best practices.
If Discourse is SSO PROVIDER, we’d need to source and implement a paygate on the Discourse side (none of which I’ve seen so far instill much confidence, to be honest). If we could dump MemberPress on the WP side, it might be worth the switch, but I’m not sure how this would work with wanting synced users in WP accessing LMS content at special, member-prices, while the general public was presented full retail.
Does this make sense? Tried to make this clear, but I’m getting a bit turned around.
I feel like one email to Jay would handle this, but every dollar spent on dev is a dollar we don’t have for the rest of our startup plans. (Feels more and more like we should defer to Jay.)
MemberPress가 WordPress에서 보호된 콘텐츠에 접근할 수 있는 사용자를 어떻게 결정하는지 알아낼 수 있다면, 동일한 데이터를 사용하여 Discourse의 SSO 로그인을 제한할 수 있습니다. 이를 수행하려면 이 주제의 두 번째 게시물인 일부 WP 사용자가 Discourse에 로그인하지 못하도록 하는 방법에 있는 두 함수에 조건문을 추가해야 합니다. 해당 조건문은 사용자 계정이 정지된 경우 true를 반환해야 합니다.
원하시는 것은 구현 가능하지만, 제가 링크한 두 함수의 조건문에 무엇을 넣어야 하는지 파악하기 위해 WordPress 개발자의 도움이 필요할 수 있습니다.
