|
Drew
|
May 21, 2018 at 4:15 pm
Hi, the main plugins I have set up are LearnDash LMS, PaidMembershipsPro, Events Espresso 4, BuddyPress, bbPress.
The website we’re building will be a barre instructor training portal to become certified. It will be blended learning (e-learning + live training) and we want to enable visitors to go 2 different routes:
1. Start with a “Basics” online course only OR
2. Dive right into Level One training (e-learning + live training)
ROUTE #1 – START WITH BASICS
Fundamentals of Barre (online ONLY) $XXX
1. If visitor only wants to take initial online ONLY course before deciding to take the Level One e-learning + live instructor training course
2. Then visitor purchases Fundamentals of Barre through Basic Barre “Membership”
3. An account is created with access to the course – but no access to forums/groups – visitor is now a student
—–
Any further than Fundamentals of Barre requires recurring monthly subscription payment plan
—–
Level One (e-learning + live training) $XXX (Prerequisite = Fundamentals of Barre)
1. Student views Level One live trainings and chooses the event to sign up for
2. Student purchases BarreAmped Membership
3. 4-6 week online course
4. Student attends live 2-day training
5. Take final quiz online afterwards
6. After student completes Level One course, student can proceed to view Level Two live trainings and choose the training event to sign up for and purchase
8. Future levels continue to stay under BarreAmped Membership with monthly subscription
ROUTE #2 – DIVE INTO BARREAMPED CERTIFICATIONS
Fundamentals of Barre (online ONLY) $XXX + Level One (e-learning + live training) $XXX (Prerequisite = Fundamentals of Barre) + Membership monthly subscription
1. If visitor wants to go straight into training to become a barre instructor
a. view Level One live trainings
b. Choose the event to sign up for
c. Which incurs a discount on the Fundamentals of Barre + Level One combo with BarreAmped Membership at checkout
2. An account is created with instant access to Fundamentals course and enrolled in a Level One live training – with access to Live training group forum/network – visitor is now a student
3. Student must complete Fundamentals before accessing Level One course
4. 4-6 week online course
5. Student attends live 2-day training
6. Take final quiz online afterwards
8. After student passes course, student can proceed to view Level Two live trainings and choose the training event to sign up for & purchase
10. Future levels continue to stay under BarreAmped Membership with monthly subscription
///
Right now I have the Events Espresso Registration Checkout page marked to require BarreAmped membership but that seems to create an extra step (losing the event you’re signing up for) which doesn’t seem seamless since the visitor would have to go back and find the specific live training. Could you please advise on the best way to seamlessly integrate Events Espresso + Learndash + PaidMembershipsPro according to this workflow in outline and this visual workflow I created? I welcome recommendations on simplifying and improving!
Thanks for your support!
|
|
Josh
|
May 21, 2018 at 7:05 pm
Hi Drew,
Normally the log in step will redirect the user back to the registration page after they’ve completed the log in form and they don’t lose the event. May I ask are you using a different page other than wp-login.php for the log in page?
|
|
Drew
|
May 22, 2018 at 1:54 pm
Thanks Josh,
No, I am using wp-login.php for the log in page. I am looking for a seamless way for the Registration Checkout page to check whether the user is a member or not before being able to checkout.
https://app.box.com/s/r33m11cubwczkhnouulxsh3us36cndkq
|
|
Josh
|
May 22, 2018 at 2:31 pm
The WP User add-on for Event Espresso adds this. In the case of whether they’re a member or not, you can set up specific tickets for non-members and members within the same event by using the Ticket Capability Requirement feature. So if the member has the required capability, they’ll be able to select tickets that non-members cannot access. More info here:
https://eventespresso.com/wiki/wp-user-integration/#ee4usage
|
|
Drew
|
May 23, 2018 at 9:23 am
Looks like WP User add-on is what I’m looking for. I gather it will work well with PaidMembershipsPro levels?
I will post back here if I have any questions as I get it set up. Thanks for the direction!
|
|
Josh
|
May 23, 2018 at 9:59 am
It will depend on whether PaidMemberships Pro’s levels make use of the WordPress capabilities system. If you can assign specific WP capabilities to PM Pro’s levels, then yes it should work well.
|
|
Drew
|
May 23, 2018 at 4:20 pm
I successfully set up the WP User add-on and we’re getting close.
Currently it requires a visitor to be logged in to register for an event. That’s good and what we want at that to happen at the initial visit of a non-member. But what if the student is already a member at the “Basic” level and we need the student to upgrade to the next membership level before registering for an event?
I found in another forum a link to a plugin for setting the membership status, so I was able to use pmp_role_X in the ‘capability’ section to restrict access. However, it hides the price and registration button from the user (who is at the basic level) from registering for it at all. I would like either non-member/member to still be able to see the price and register for the event but then run into a notification or page that requires a membership upgrade.
Here is a screenshot of how it looks for me right now: 
Thanks!
|
|
Tony
|
May 24, 2018 at 7:04 am
Hi there,
EE doesn’t have the functionality to restrict tickets after the user has selected them (on step 1) out of the box.
The minimum required capability on a ticket determines if the user can select that ticket in the ticket selector, so if they don’t have the capability they see the above. You can change the text displayed to non-members it that helps make it clearer that users need to be a specific type of member if that helps?
Altering EE so that the user can select a ticket and then see a notice preventing them from registration unless they register will require custom development on both the ticket selector and single page checkout.
|
