Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember General Questions › Hiding content that was published prior to subscription
- This topic has 4 replies, 2 voices, and was last updated 12 years, 10 months ago by martin.
-
AuthorPosts
-
January 6, 2012 at 11:23 am #5200martinMember
Hello,
I am setting up a membership site with wp-eStore and wp-eMember, where subscribers will pay a monthly fee and be given access to weekly blog posts with premium content.
Is it possible to ensure that subscribers only have access in the blog ‘archive’ to the content that has been made available since their subsciption date. For example, someone signing up this week would end up with access to everything published from this week onwards, but a new subsciber in July would only have access to content from that date onwards, and not be able to see any blog posts from before they joined.
I’m imagining that this is quite straightforward, I just can’t see how to implement it!
Many thanks
Martin
January 7, 2012 at 8:30 am #40453adminKeymasterWhen setting up a membership site with weekly or monthly content, users prefer to setup an auto upgrade scheme. This allows your member to start from week1 or month1 when they singup and then progressively get promoted to higher and higher levels which gives them access to later content:
Is that what you are after?
Or something like this?
http://www.tipsandtricks-hq.com/wordpress-membership/membership-site-for-selling-a-course-897
January 9, 2012 at 10:31 am #40454martinMemberHi there – I read the post you recommended, but I’m still not quite sure if what you suggest is the solution or not, as I maybe didn’t explain myself very well.
The idea is *not* that each new subscriber will recieve week 1, then week 2, week 3 etc., based on the date they have joined (which is what I understand by the term ‘dripping content’ – like for a weekly course which must be delivered in a set order), it’s that everyone who is a subscriber at a given time will get access to the same weekly blog post at the same time. For example, on week commencing March 5th, all subscribers (regardless of when they joined) will access the blog post for that week – as it will be time sensitive and relevent to that specific week.
What I’m trying to do is make it so that a person who has subscribed in, say, January, will have access to all the previous weekly blog posts they have read since joining (so they can review them if they like) but that a new subscriber who joins on, say, March 2nd, will only have access to the blog posts from March 5th onwards, which is the next published post (and would therefore have to ‘buy’ back issues – for want of a better way of describing old content – if they wanted to).
Hope that’s a bit clearer, and any advice would be great. Thanks
Martin
January 10, 2012 at 4:10 am #40455adminKeymasterThank you.. I see what you want. You can make a membership level for each month so when someone purchase the membership they have access to that month and the future ones only. It also depends on how granular you want to go.. if you want to make it too granular then it will involve a lot of work.
In general the easiest way to handle this would be to use the category protection.
Here is a rough guideline… When a new month starts, do the following:
– Create a category for this new month
– Put all the article of this month into this category
– Create a new membership level for this month
– Protect the category of this month under this new membership (you can give access to all the older membership levels to this new category so that older members have access to new content too).
– Place buy button for the current month’s membership so new users only have access to current month and future month’s content. They can also buy older content by purchasing the older membership levels if you want to allow it.
– Every year or so you can consolidate your older month’s membership level content and put them all under a yearly category.
January 25, 2012 at 11:43 am #40456martinMemberBrilliant, that’s exactly what I was looking for – thanks very much
-
AuthorPosts
- You must be logged in to reply to this topic.