By the way, I am NOT doing this as an admin.
New computer, new user, clean start.
Hey @thebioguy,
I’m having a hard time recreating this frightening issue with the steps you’ve provided.
Are you certain you haven’t skipped any details in your above recreation steps that are necessary to recreate the issue?
Additionally, I think it’s important to note that if a PAID course belongs to a free membership, users enrolled in that membership *will* automatically bypass checkout if they’re logged in as a member of that membership. The use case for this is if you intended to allow users to purchase a bundle of courses (which are not free) at a discounted price because they belong to the membership.
LifterLMS currently (and intentionally) ignores checkout in this scenario. Is this the issue you’re identifying?
Please let me know if something is missing from your above steps to bypass purchase as this sounds very serious if it’s true but I don’t see a way to actually make that happen given the steps you’ve provided.
Thanks,
I have one paid course and one free membership. That, plus the ability to auto enroll into a course when joining a membership and restricting access creates a total of 8 permutations. I find it HARD to believe that you can’t recreate this “frightening” issue.
Why don’t you provide EXACT steps and settings for the scenario I describe below, and we’ll see if if can be done.
One site with Membership restricted pages and a Paid course.
Visitors can not see Membership restricted pages or course material.
Members can see membership-restricted pages but not the course material
Membership is automatic with course purchase.
Since a purchaser is also a member, they see everything.
What are the setting for the
Membership?
Member restricted pages?
Course?
Course lessons?
What are the redirects for the login page?
What are the redirects for the membership page?
What are the redirects for the purchase page and checkout?
I have been working on this for over 6 weeks. Whatever you THINK is intuitive and logical, is not.
Hey @thebioguy,
My point is that this is not an issue in the codebase, it is not a security flaw, it is not a bug. It MAY not be intuitive or logical, but this is the way it works, and it is by design.
I am asking for detailed recreation steps to ensure I am not missing something and that there’s an issue OTHER than that you’re not happy with our feature set and the way things work.
I am *not* going to spend time providing you with the settings because that would be a waste of both your time and mine.
Please see my response in your other ticket for a potential resolution to the feature we’re missing that you very much wish LifterLMS would have.
Again, if I really did miss a step in your original ticket, please let me know.
Thanks.
I’ve read the other post and will try those workarounds.
@thebioguy,
Marking this as resolved but please post a new thread or re-open if you need further assistance here.
Take care,
