Community Support Forums

Hi Jason and s2Members!

I have just recently downloaded and started using your s2Member plugin. Very impressed with what I have seen so far.

I am creating a membership site for a client and I am wanting to know is there a way of drip feeding or making content restricted. They are wanting a one time fee to gain access to their membership site.

But want the content to only be available the longer the customer stays a member. So as an example.

Member A. Pays for the membership in January 2012 and he is given module 1 then the next month module 2 and the next month module 3 and so on and so on

Member B. Pays for the member ship in March 2012 and he is given module 1 then the next month module 2 and the next month module 3 and so on and so on.

Is this possible with out having a recurring billing system in place?

So the longer the customer stays the more content they are going to receive.

Also if we have a site with squeeze, sales and blog pages should we set up the membership site on a sub or add on domian

i.e www.member.domainname.com
or www.domainname.access.com
or just have it going through as a page www.domainname.com/members?

Many Thanks

Craig

Hi Craig,

Thank you for the KUDOS. Glad you're enjoying the plugin!

Content Dripping is possible with s2Member but will require some PHP scripting. Please see WP Admin -> s2Member -> API/Scripting -> s2Member Content Dripping. This can be done with recurring subscriptions or single-payment type accounts.

Hi Raam,

Thanks for the reply. I was wondering that I must have got lost in among all the other enquirers. I will look into it and if I need any assisitant I will be back for some guidance.

Also what do you think of adding the membership site on a sub domain? Is this normal practice?

Cheers

Craig

You can use s2Member on a sub-domain as long as all the protected content is also on the sub-domain.

In other words, if you have WordPress with s2Member running on members.example.com, but you have protected content on another WordPress installation at example.com, members.example.com users won't be able to access protected content on example.com (the installations won't share information).

You can easily use example.com to sell membership and simply point the signup URLs at the s2Member installation hosted on members.example.com; that will work. (Again, all protected content needs to be hosted on members.example.com, not example.com).

Does that make sense?

Thanks again Raam,

Yes so just keep the membership/site content inside the sub domain and sell it from the main domain. If I was to add content to the main domain I would not be able to protect that content as the plugin would be set on the sub domain.

That's right. Well that's how I see it from your explanation.

Craig

Yup, that's correct.

Let us know if you have any other questions!