Create a Membership Website – Configure Autoresponder and Email
Good morning everybody and welcome to our fifth week in our live How to Create a Membership Website tutorial series. So today what we are going to do is to wrap up our conversation about content protection and then we are going to move on to autoresponder configuration.
When I originally envisioned this course I was only going to teach AWeber because that’s what I like best and that’s what I really use but a couple of people mentioned that they’d like to see the same thing for Mail Champ. In the course of my preparation this week I realized that that was too much material to actually get through in the session that’s available here.
I have prepared the materials so I’d like perhaps a show of hands or some sort of indication that you are interested in seeing both AWeber and Mail Champ. I would do the Mail Champ presentation immediately after the rest of the material is finished. If nobody here really cares about Mail Champ then I won’t worry about it at all.
Create a Membership Website – Manage Content Protection
I’ll just dive into it. So WP eMember has seven levels of content protection as we mentioned a last week. The first level of protection is with the content visible to absolutely everybody whether they are logged in or not. The second is with content visible only to the public. So as soon as you are logged in it’s no longer visible to you. And then visible to everybody who is logged in regardless of your account status. And by that what I mean regardless of whether or not you are current. So even though your account may have expired because you had an account you can log in.
And then we have visible to all logged in whose accounts are current. So if your account has expired you can’t access content that has that level of protection. The next most specific is content that is visible to specific membership levels. This is, of course, what we are talking about most often. So if you’ve purchased the course on How to Create a Membership Site then you can see all of the content that is protected for that membership level. As long as your account is current but no one else can see that and you can’t see any of the other stuff.
Next you have a possibility of having content that is visible to specific members only and so member ID 1 could see content that is specific to that member and not to anybody else. And then finally you have site wide protection and that site wide protection generally takes the form of the site being entirely inaccessible unless you log in.
So those are the seven levels of content protection. We talked about how to configure that from the dashboard and how to configure that from the post or page edits and from the category last week. This week we are going to talk about how to do it in-line. There are really five methods of getting to that place. Last week I said there were four but in fact there are five.
The first is the protection from the WP eMember admin screens which we’d covered last week. The second is protection from the post or page edit screens. The third is More tagged protection and so it’s possible for you to take a blog add a More tag which allows people to see the first part of the blog but everything beyond the More tag is protected so that’s a possibility.
Create a Membership Website – In-line Content Protection with Shortcodes
The next one is in-line protection which is what we are going to talk about right now. And that is the post or page itself may not be protected in any way but there is protection that is added by way of shortcodes surrounding content that protects it in one way or the other.
And then the final way is programmatic protection which we may talk about as well. But really without any programming whatsoever the first four are really the ways to take care of that. So what I want you to do is take a look on the site. Down under Week 5 Resources I have this WP eStore shortcodes cheat sheet, if you take a look at that that’s what we are going to talk about here right now. This functions exactly the same way as the shortcodes work in WP eStore. Here’s where you’ve got the different levels of in-line content protection.
So for example this shortcode eMember Protected means that content that’s in between these two shortcodes is only viewable by people who are logged in and who have access to the post. So for example, if you have a post that is entirely unprotected if you wrap this section in eMember Protected or if you wrap a piece of content inside of these two shortcodes then that content will be available to logged in members and it will be hidden to those people who are not logged in.
The next level is where you have the choice of specifying a membership level for the content that you are wrapping. So for example, if you want this content to be available to membership levels 1,2 and 3 then you would use this here, eMember Protected for 1 where 1, 3 and 5 here are the level numbers or the level IDs.
And so if you want to make something that’s available for only one specific membership level then you would put the membership level ID in here. If it was available to more than one then you would put a dash between each number. This allows for you, for example, to have different content on the same page for different levels. You could easily have a block of content that was available for level number 1 and then another block of content that was available for level number 2 and another that would be available for level number 3 and all of them on the same page but of each of them wrapped with a shortcode of a different number in here.
Then you have that very specific member. The content might be restricted to a very specific member and can be wrapped in these shortcodes so eMember Protected and them member ID equals and then you would put the member ID there. If you wanted to put multiple member IDs then you would use the hyphens in here but the chances are you would do this for a specific member only and not for a group of members because it’s highly cumbersome to do it for a group of members.
And the next one is very similar to the first except that it doesn’t check to make sure that the membership has expired. Here if the eMember logs in and their membership is expired they are not going to be able to view it but here if the member is logged in they’ll be able to view it even if their membership is expired.
And so there may be situations in which, for example, you want the Upgrade button or something like that that’s available to a member whose account has expired but you still want to protect it. You would use this shortcode for that. And then if you wanted to have content that was available only to people who are not logged in so it’s essentially the inverse of the first one. Then what you would do is you would use this shortcode and if you leave off the ID number and if you just use the eMember Protected—actually you know what this is a flaw in my format and I’m going to fix this, this is the wrong shorcode here.
This is the same shortcode as there but it’s supposed to be a different one so I’m going to fix this sheet for you and get that on there this week. But the shortcode that belongs in here doesn’t take a membership ID it simply blocks out a piece of code or a piece of content that would be available to somebody if they are not logged in, otherwise it’s not visible.
We’ll mostly do this kind of a thing on a page by page basis as we work on our content. Nevertheless you can certainly take a block of content, for example, you could have an invitation for people to join or you could have a call to action but not on every page and then inside of it and that call of action would be wrapped by these shortcodes. So if you are logged in then you don’t see that call to action and you just keep on going. But if you are not logged in then you will see the call to action.
You might also, if you are supporting your site partially by advertising, show ads to people who are not logged in and so you could put your picture using a shortcode for inserting Google ad or some other kind of ad. So you could wrap that shortcode in this shortcode which would then show ads to people who are not logged in but would hide the ads from people who are logged in, that sort of thing.
So that’s what these shortcodes do. They give you that in-line content protection where you can have a page that’s going to be available to everyone but then you have portions of the page that you have segregated off and will only be available to specific users there. And that pretty much wraps up the in-line content protection.