Jason (Lead Developer)

Thanks for your purchase :-)

Please log into your customer account here at s2Member.com and post this question in our Customer Support Forum for assistance. The account you are currently posting under is tied to a free community user status.

Also, please clarify just a bit further and try to narrow this down to specific questions about s2Member functionality. That will give you the best chance of getting an answer that helps you accomplish what you need to.

s2Member® » Customer Support Forum

Roles/Caps in the database look fine, but it would appear to me that you have a plugin misbehaving somewhere (i.e. something is modifying Roles/Caps at runtime; which is not showing up in plugins like Enhanced Cap Manager). I would suggest that you disable one plugin at a time until the Quick Cache menu appears on the left.

If you can narrow it down to a particular plugin conflict, I will investigate this further for you, to find out why.

Thanks for your patience.

I find there are no IPNs from PayPal to indicate that a Recurring Profile has been terminated or expired due to having reached your MAXFAILEDPAYMENTS value of 2. This has not occurred yet on your installation.

I do see several failed payments, but nothing that s2Member should respond to yet. s2Member will wait for one of these IPN txn_type values before it triggers an EOT event for a paying Member.

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

I also confirmed that s2Member is sending the MAXFAILEDPAYMENTS and AUTOBILLOUTAMT variables on your installation. And we are. You are correct, this is controlled by the s2Member rra="" Shortcode Attribute.

As seen in your paypal-api.log file.

'AUTOBILLOUTAMT' => 'AddToNextBilling',
'DESC' => 'Smart Insights Expert membership',
'MAXFAILEDPAYMENTS' => '2',

Possible Solutions for you…

I think part of the problem here, is that you are billing on a Yearly basis. Unfortunately, there is no PayPal API parameter that allows s2Member® to specify when billing should be reattempted in the event of failure. This is left in the hands of PayPal (and/or whatever agreement you have with PayPal). Failed payments are supposed to be retried every few days, not every year. See this related thread.

However, it appears from your log files that a failed payment is being rescheduled for a retry the following year (not anytime soon). Thus, allowing MAXFAILEDPAYMENTS=2, could mean that you allow a customer to fail payment for up to 2 years; and not until the 3rd failed payment in their 3rd year would the account be suspended.

So here are two possible solutions:

1. Contact PayPal and find out what can be done with your account to have payments automatically retried within 10 days of the initial failed payment having occurred. From what I understand, this is supposed to be retried every few days, not every year. See this related thread.

2. Or, do not allow failed payments (i.e. rra="0" in your s2Member® Shortcode).

Thanks for the follow-up :-)

Here is a quick example:

<?php
$user_id = get_current_user_ID();
$user_field_values = get_user_field('my_field_ID', $user_id);

if(is_array($user_field_values))
	{
		foreach($user_field_values as $value)
			echo $value.'<br />';
	}
?>

Replace my_field_ID with the unique ID you assigned the Custom Registration/Profile Field in s2Member.
See: Dashboard -› s2Member® -› General Options -› Registration/Profile Fields

See also: Knowledge Base » ezPHP Plugin for WordPress®

Thanks for the follow-up :-)

If you’d like to submit a Dashboard login we will investigate this. Thanks!
Please use: s2Member® » Private Contact Form

Great! Thanks for reporting back :-)

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

Yes, with s2Member® Pro it is possible to customize your Auto-Return Thank You page in several ways; and also to use a success="" Attribute in your Shortcode, which makes it possible to design your own :-)

Regarding the existing implemention and PayPal’s ToS. I’m not aware of any issues in the existing release; so please post the exact message that you received upon completing checkout and we will investigate that for you. Your customers should be greeted with both a Thank-You message confirming the transaction, and also an email receipt; as configured here. See: Dashboard -› s2Member® -› PayPal® Options -› Signup Confirmation Email

Thanks for the follow-up :-)

On the server that is running Mod Security, I would watch your s2Member® log files carefully (particularly in the latest release of s2Member; keep tabs on your s2-http-api-debug.log file) for any server issues that result in 403, 404, or 503 errors. You can also monitor your web server logs for Mod Security issues.

Thanks for the heads up on this thread :-)

Please use s2Member® API Function: get_user_field()

If the value is an array; you will get the array containing the selected values.

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

This is sort of a false positive; but not really. Let me explain, because there IS an issue here.

The Camera plugin contains this line of code:

require (ABSPATH . WPINC . '/pluggable.php');

This prevents other plugins from being able to override functions inside pluggable.php; which is what WordPress® intends (i.e. these are pluggable functions that can optionally be defined by plugins — instead of by WordPress® itself). Loading the pluggable.php file too soon, will remove the ability for other plugins to accomplish this. Hence, the conflict that you are seeing.

Generally speaking, a plugin should really NOT include/require the pluggable.php file at all. Instead, it should simply wait until the WordPress® init Hook has been fired, at which point any functionality it needs from the pluggable functions will be available already; so there’s no need for a plugin developer to include it.

I would contact the developer of this plugin and point them to this thread. They probably just didn’t realize.
See also: http://codex.wordpress.org/Pluggable_Functions

Thanks for the follow-up :-)

I will assume that player_key="playerkey" actually contains a real JW Player key, correct?

I will also assume that where you have fancy quotes in this post, that happened because you did not wrap the Shortcode with <code> tags, correct? You should have single quotes around the value of your file location:
Example: player_option_blocks="logo:{file:'/jwplayer6/test2.png'}"

If all of that is correct, it actually sounds like your JW Player license key is simply not working on this domain where your JW Player is located. Can you please confirm this for us? Thanks!

If problems persist, you can submit a Dashboard login and we’ll review things for you. Or, you might also want to contact Longtail Video to ask about the validity of your JW Player key on this domain. Just to be sure. The fact that you have a JW Player logo at all, suggests the key is not working properly.

Thanks for the heads up on this thread :-)

While Crisitan investigates this, you might also take a look at this section of your Dashboard.
Dashboard -› s2Member® -› PayPal® Options -› PayPal® PDT Integration