Jason (Lead Developer)

Thanks for the heads up on this thread :-)

Sorry, I’m not that familiar with the WPML plugin yet. What do the URLs to your feeds look like exactly? Is there a language variable passed through; or how are these three URLs different? Thanks!

I will most likely suggest URI Restrictions for this.
See: Dashboard -› s2Member® -› Restriction Options -› URI Access Restrictions

Thanks for the heads up on this thread :-)

s2Member® waits for one of these IPN txn_type values before it does anything.

subscr_eot
recurring_payment_expired
recurring_payment_suspended_due_to_max_failed_payment
recurring_payment_profile_cancel

s2Member® also deals with refunds/chargebacks, and these are indicated by IPNs that include payment status values like: refunded, reversed, reversal or initial_payment_status=failed

Investigation completed.

I found that your WordPress® installation has had some different versions of bbPress installed on it from the past. It seems to have caused some mild database corruption with respect to Roles/Capabilities in WordPress®. Your default set of Roles/Capabilities for WordPress® was missing several important things.

Please let us know if problems persist :-)

Very welcome!

Looks good Ronnie.

In this part of your code.
strtotime('+14 hours') — keep in mind that is UTC time; it’s NOT your local time.

Thanks for your patience.

I just took a look at your installation and I ran diagnostics against s2Member® and s2Member® Pro.

Your installation directory here: /wp-content/plugins/s2member-pro/ is incomplete. It appeared to be missing the entire /includes/ directory (like it failed during your upload perhaps).

I tried to delete the entire directory and upload a fresh copy for you, but during my upload the server is returning random errors with “password failed”. This could indicate that my access is limited in some way; or it could indicate a larger problem with this server

I would make an attempt yourself to re-upload a fresh copy of the latest release of s2Member® Pro. Then run the s2Member® Server Scanner to be sure you don’t get any checksum errors. For your convenience, I’m uploading the s2Member® Server Scanner for you. So just run this scanner after you re-upload to make sure everything made it in there OK :-) Visit: /academy/s2-server-scanner.php in your browser.

Thanks Ronnie!

Thanks for your patience.

We will be introducing a filter for this (at the very least) in the next maintenance release. I’m attaching a PATCH file for you in the mean time; in case you’d like to jump the gun a bit. Please unzip and upload the attached file, allowing it to override your existing copy of /s2member/includes/classes/utils-time.inc.php

PATCH: http://d1v41qemfjie0l.cloudfront.net/s2member/uploads/utils-time.inc_.php_.zip

Then follow these instructions to apply the Filter you desire.

Please create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
(NOTE: these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins)
(See also: http://www.s2member.com/kb/hacking-s2member/)

Regarding Eduan’s response earlier. I’m sorry about that Ronnie. I don’t think he meant to come off as being rude; but I can see why you might have that impression. I will notify Eduan about this. He’s a good guy.

Why on earth would someone give out 1 day for free if he has the option to only sell 1 day access?
Why would you even code it to auto behave like that.. The option should atleast be there “Do you want to be a serious business or do you want to give away stuff for free?”

This is meant as a grace period, because often times a customer does NOT understand how these times work; particularly when they are in a different time zone. So while it might be something that you’re not thrilled about (and I can understand that); this is an edge case. Most site owners will agree that a grace period is ideal in most scenarios; because a customer being upset they lost access too soon, is usually not desirable. Even if it’s handled perfectly (i.e. right on time); anything too soon, from a customer’s perspective, will result in negativity.

One extra day in the case of a 1 day access though, I can see where that would become an issue. I will see what we can do about this in the next release; even beyond the filter I’m preparing here for you.

Thanks for your reply :-)

We’re going to run some tests now. Please stand by for a second notification that we have completed the tests.

Thanks for your inquiry. ~ We appreciate your patience :-)

You can use the WordPress® function get_users()

Example code:

<?php
foreach(get_users('role=s2member_level1') as $user)
	echo $user->ID.'<br />';
?>

See also: Knowledge Base » s2Member® Roles/Capabilities
See also: Knowledge Base » Changing Roles/Capabilities via PHP

Thanks for your inquiry. ~ We appreciate your patience :-)

Please correct this mistake in your Simple Shortcode Conditional and try this again for us. Please let us know if you have any further trouble. See also: Knowledge Base » Simple Shortcode Conditionals

[_s2If !current_user_can("access_s2member_ccap_mainfiles")]

Should be: [_s2If !current_user_can(access_s2member_ccap_mainfiles)]
No quotes inside a Shortcode Conditional please; that messes up the Shortcode parser unfortunately.

Thanks for your inquiry. ~ We appreciate your patience :-)

Anyhow, the original question was whether or not a post can be BOTH available to paid members and as a pay-per-post for non-members. The answer given was yes, however, the man in the video linked in that answer specifically states not to put a paid membership restriction and a single post restriction in the same post because the functions will create a conflict

This is correct. Perhaps I did misunderstand the question. I’m not entirely sure because that particular topic never received any additional replies. You are correct though, that DOES create a conflict. The video is correct.

What I meant is that both functionalities are possible with s2Member®. It IS possible to sell Membership Access, and also to sell Specific Posts/Pages that do not require Membership.

It’s not possible to protect a Specific Post/Page being sold through s2Member®, with Membership Access also. This is because s2Member® will force a User to satisfy all requirements before being allowed to view the content. Being a Member is not necessarily enough to access a Post or Page that is protected by Specific Post/Page Access; that Member needs to have purchased that Specific Post/Page for themselves.

This is actually what makes Specific Post/Page Access powerful though. It’s functionality is completely independent from Membership. Being a Member does not give them access to that Specific Post/Page; they need to purchase that Post or Page like anyone else.

Possible solution for you.

Duplicate the content you’re selling across two different Posts/Pages. Make one of them available to Members; and sell one of them through Specific Post/Page Access to non-Members (or even to existing Members — that’s fine too). That should do it!

This plugin that I wrote, could really help with that. You would create and store the content just ONE time, but use it as a Snippet and duplicate it into multiple Posts/Pages.

See: Knowledge Base » WP Snippets (A Plugin for WordPress®)

Please let us know if you have any other questions/concerns :-)