Jason (Lead Developer)

Thanks for the follow-up :-)

What is your fault then?

You are right. We VERY rarely provide refunds, simply because we make it a point NOT to advertise something that is not possible with our software. We expect you to get what you paid for. If you did not, we will be happy to give you a refund, and make it a point to change and/or modify what was broken, or what was confusing, etc.

Example Of A Valid Refund Request

When I uninstall s2member the other plugins work correctly. This is an issue only with s2member pro installation. I understand that you cannot guarantee the plugin compatibility with other plugins, but you do guarantee installation and in this case it does not install without breaking other aspects of my site.

Other aspects of your site being 3rd-party components and plugins, which, as I mentioned previously, are absolutely NOT covered by our terms of service. We sell and support s2Member, not WordPress itself, or other 3rd party components, plugins, themes, etc.

Thanks for the heads up on this thread :-)

Can I put %%full_coupon_code%% or %%coupon_code%% in the New User Notification email message?

Here is a simpler solution to this. Please follow the instructions below.

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/)

Details received again. Still the same issue.

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

Regarding this EOT/deletion type: auto-eot-cancellation-expiration-demotion

This occurs whenever s2Member’s Auto EOT System (powered by WP Cron) finds a User/Member with an EOT Time that is less than or equal to the current time (e.g. the time at which the CRON job is running). In other words, this event occurs whenever an EOT or deletion occurs, as a result of a customer having been associated with an Auto-EOT Time. s2Member expires the account at the specified Auto-EOT Time.

See: WordPress® -› Users -› Edit any User account and find this section.

It is possible for a User to be demoted (or even deleted) when an EOT occurs (based on your EOT Behavior configuration in s2Member). If they are simply demoted (the default behavior), in the future they might upgrade and/or purchase something new, causing the account to be re-instated. I think this is what you’re describing.

There is no way for s2Member to predict what the customer will do in the future, so all you can do is listen for EOT/Deletion events and react based on what is happening at the present time.

Is it possible if they’re renewing a subscription this would get triggered?

It’s possible. I’m not aware of this occurring, but it IS possible. It just depends on what (if any) notifications that your payment gateway is sending back to your server for s2Member® to process during an account upgrade/downgrade. You can use s2Member’s API Notification for EOTs/Deletions, to listen for events like this.

See: Dashboard -› s2Member® -› API / Notifications -› EOT/Deletion Notifications

If you would like us to review your s2Member log files, we might be able to tell you more about any EOT events that are occuring on your installation, immediately followed by a renewal. If you’d like us to review your log files, please submit those privately. See: s2Member® » Private Contact Form

Please let us know if problems persist :-)

Thanks for your patience.

~ Details received, but we were unable to access your Dashboard for the purpose of running diagnostics.

Thanks for your patience Conor.

~ Details received. Investigating now.

Interesting! Thank you. I’m going to review this shortly!

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

To Clarify; Do we need to have PayPal Pro to accept payments on our site, or are there other PayPal services we can use, if we use the Pro Form, provided by s2Member?

See also: Pre Sale FAQs » To use s2Member® Pro Forms, will I have to use PayPal® Pro?

Please let us know if you have any other questions/concerns.

Thanks for the heads up on this thread :-)

The wp_authenticate function is what logs a user into WordPress. Luckily, WordPress makes this a pluggable function. Meaning, you can define it yourself, and WordPress will use your version of the function instead of it’s default version.

Here is the default version of the function in WP v3.5.

/**
 * Checks a user's login information and logs them in if it checks out.
 *
 * @since 2.5.0
 *
 * @param string $username User's username
 * @param string $password User's password
 * @return WP_Error|WP_User WP_User object if login successful, otherwise WP_Error object.
 */
function wp_authenticate($username, $password) {
	$username = sanitize_user($username);
	$password = trim($password);

	$user = apply_filters('authenticate', null, $username, $password);

	if ( $user == null ) {
		// TODO what should the error message be? (Or would these even happen?)
		// Only needed if all authentication handlers fail to return anything.
		$user = new WP_Error('authentication_failed', __('<strong>ERROR</strong>: Invalid username or incorrect password.'));
	}

	$ignore_codes = array('empty_username', 'empty_password');

	if (is_wp_error($user) && !in_array($user->get_error_code(), $ignore_codes) ) {
		do_action('wp_login_failed', $username);
	}

	return $user;
}

A modified version might look something like this.

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/)

/**
 * Checks a user's login information and logs them in if it checks out.
 *
 * @since 2.5.0
 *
 * @param string $username User's username
 * @param string $password User's password
 * @return WP_Error|WP_User WP_User object if login successful, otherwise WP_Error object.
 */
function wp_authenticate($username, $password) {
	$username = sanitize_user($username);
	$password = trim($password);

	$user = apply_filters('authenticate', null, $username, $password);

	if ( $user == null ) {
		// TODO what should the error message be? (Or would these even happen?)
		// Only needed if all authentication handlers fail to return anything.
		$user = new WP_Error('authentication_failed', __('<strong>ERROR</strong>: Invalid username or incorrect password.'));
	}
	else if($user->has_cap('s2member_level1')) // A Level #1 Member?
		{
			$deny = TRUE; // Deny these Members?
			
			if($deny)
				{
					$user = new WP_Error('authentication_failed', __('<strong>ERROR</strong>: You have been denied access at this time. Please try again later.'));
				}
		}

	$ignore_codes = array('empty_username', 'empty_password');

	if (is_wp_error($user) && !in_array($user->get_error_code(), $ignore_codes) ) {
		do_action('wp_login_failed', $username);
	}

	return $user;
}

Thanks for the heads up on this thread :-)

Regarding PayPal ERP. If you integrate with Pro Forms (recommended), you will have no use for the ERP service. I’ve discussed this with Bruce, and I’m sorry for the confusion. ERP works with PayPal Standard Buttons only. If you are using s2Member Pro Forms, you’re integrating with PayPal Express Checkout and the optional PayPal ERP service is not needed or useful in this scenario.

ERP would be useful ONLY if you were planning to charge on a recurring basis, and only if you are NOT integrating Pro Forms, but instead using PayPal Standard Buttons.

To integrate s2Member Pro Forms (WITHOUT a PayPal Pro account), please see:
Pre Sale FAQs » To use s2Member® Pro Forms, will I have to use PayPal® Pro?

Thanks for reporting this important issue.

Yes, I’ve seen this before. Some web hosts (servers), are configured NOT to allow PHP scripts to run from directories with 777 permissions. This is for added security. You might be able to serve static files from these directories, but accessing a PHP script will cause the server to trigger an error.

Solution: Set permissions to 755 (recommended) on all parent directories.

FYI: HostGator™ is known to do this.

Thanks for your reply :-)

A. In the Page Restrictions area, in Level 1, enter all the IDs of all the restricted pages on the site.

That is correct.

B. Change all paying members of the site from Level 2 to Level 1.
Question: Would this not work if I just left the page restrictions on Level 2 and made all paying members Level 2?

Yes. Either way would be fine.

C. On a per page basis, give every single restricted page on the site the custom capability of “all”

Correct.

D. On a per page basis, give certain pages other custom capabilities, such as “limited”.

Correct.

E. Add the custom code to functions.php to support these custom groupings.

Correct.

Questions:
+ Is there anything else I need to do to make this work?

No. That would be it.

+ If I do it this way it seems that using tags won’t do much, as it will all be based on the custom capabilities. I was hoping I could create the custom capabilities groupings using tags alone, as opposed to adding custom capabilities labels to every single page.
+ Is there any way to bulk assign custom capabilities, as we have many pages on our site?

Now… You might have something like this, which would encompass everything you’re trying to accomplish here, in a more custom way, for your business model.

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/)

<?php
add_action ('wp', 'my_custom_capability_handler');

function my_custom_capability_handler()
	{
		if(is_singular() && has_tag('members-only')) // Restricted?
			{
				if(!current_user_can('access_s2member_ccap_members_only'))
				// Is this a Member that I sold the Custom Capability: `members_only` to?
				// If NOT, we redirect them to the Membership Options Page so they can purchase.
					{
						header('Location: '.S2MEMBER_MEMBERSHIP_OPTIONS_PAGE_URL);
						exit;
					}
				
				if(has_tag('additional-access-required')) // Also requires additional access?
					{
						if(!current_user_can('access_s2member_ccap_additional_access'))
						// Is this a Member that I also sold the Custom Capability: `additional_access` to?
						// If NOT, we redirect them to the Membership Options Page so they can purchase.
							{
								header('Location: '.S2MEMBER_MEMBERSHIP_OPTIONS_PAGE_URL);
								exit;
							}
					}
			}
	}
&#91;/hilite&#93;
&#91;info_box&#93;
If you were to use something like this, all you do is sell Custom Capabilities. You're protecting your content by it's association with the Tags I listed above. Nice! The &#91;hilite path&#93;Dashboard -› s2Member® -› Restriction Options&#91;/hilite&#93; panel would not be used in a case like this, because you're implementing something more custom here.
&#91;/info_box&#93;

<h4>Recommended Reading/Viewing...</h4>
See: Dashboard -› s2Member® -› API / Scripting -› Advanced PHP Conditionals

Video » s2Member (Custom Capabilities)