Statistics: Posted by Jason Caldwell — June 4th, 2011, 10:46 am
Statistics: Posted by dartd — June 4th, 2011, 1:34 am
$ws_plugin__s2member_temp_a_pp = ($GLOBALS["WS_PLUGIN__"]["s2member"]["o"]["specific_ids"]) ? (array)get_posts ("post_type=any&include=" . $GLOBALS["WS_PLUGIN__"]["s2member"]["o"]["specific_ids"]) : array ();
Statistics: Posted by Jason Caldwell — June 4th, 2011, 1:31 am
Statistics: Posted by dartd — June 4th, 2011, 1:10 am
- Your Membership Options Page
- Your Home Page
- Your Login Welcome Page
- Your Download Limit Exceeded Page ( if allowing Downloads )
- Any Page that is already protected with standard Page Access Restrictions ( i.e. Membership Protection ).
- Any Post that is already protected with standard Post Access Restrictions ( i.e. Membership Protection ).
Statistics: Posted by Jason Caldwell — June 4th, 2011, 12:45 am
Post/Page IDs in comma-delimited format. Example: 1,2,3,34,8,21 * Note... the word all does NOT work here. Also, please be careful not to create a conflict with other Access Restrictions. If you are going to sell Specific Post/Page Access, you should enter specific Post/Page IDs here; and make SURE that you've NOT already protected any of these Posts/Pages with Member Level Access Restrictions. In other words, if you configure s2Member, in such as a way, that a Post/Page requires Membership Level Access, you cannot sell that same Post/Page through Specific Post/Page Access. Doing so, would create a conflict. Customers that purchased Specific Post/Page Access, would be unable to access the Post/Page - without also having a Membership. Not good. So be careful with this.
Statistics: Posted by Cristián Lávaque — June 4th, 2011, 12:34 am
Statistics: Posted by dartd — June 3rd, 2011, 11:43 pm
Statistics: Posted by Walton — January 25th, 2011, 5:17 am
Statistics: Posted by Jason Caldwell — July 7th, 2010, 4:05 pm
Statistics: Posted by byronyasgur — July 1st, 2010, 4:32 pm