Jason (Lead Developer)

Thanks for the heads up on this request for support.

@ Brett

Please see this thread for full details on the issue.
http://www.s2member.com/forums/topic/error-compilation-failedposix-on-info-pages/#post-6639
PCRE v8.13 has a known bug which causes this error. Current versions of PHP come with v8.12, so having 8.13 indicates that PCRE is already installed on your server prior to the installation of PHP.

Thanks for the heads up on this request for support.

Yes, that is correct. When an upgrade occurs, the old billing profile (and any recurring charges that were associated with it), are discarded, and a new billing profile is created to take it’s place. This works the same as it does with PayPal Pro.

Thanks for the heads up on this thread.

@Suhaib Siddiqi

You mentioned this URI is being protected properly:
/cometchat/cometchatjs.php

But these are not:

/members/?pid=5&pagetitle=save_searches
/members/?pid=6&pagetitle=privacy_settings
/members/?pid=6&pagetitle=skype_settings
/members/?pid=13&pagetitle=viewed_me
/members/?pid=13&pagetitle=i_viewed
/members/?pid=13&pagetitle=trending
/members/?pid=13&pagetitle=interest_cloud
/members/?pid=1&pagetitle=view_winks
/members/?pid=1&pagetitle=view_friends
/members/?pid=1&pagetitle=my_favourites
/members/?pid=1&pagetitle=my_matches
/members/?pid=1&pagetitle=alerts
/members/?pid=1&pagetitle=blocked

Depending on your permalink settings in WordPress®, these URI Restrictions may or may not work with the trailing /? on the end. If your permalink options in WordPress® do NOT include a trailing slash, then all URIs on your site will NOT have a trailing slash at the end (this is how WordPress® works internally).

If your permalink settings do NOT include a trailing slash, your URI Restrictions need to look like this:

/members?pid=5&pagetitle=save_searches
/members?pid=6&pagetitle=privacy_settings
/members?pid=6&pagetitle=skype_settings
/members?pid=13&pagetitle=viewed_me
/members?pid=13&pagetitle=i_viewed
/members?pid=13&pagetitle=trending
/members?pid=13&pagetitle=interest_cloud
/members?pid=1&pagetitle=view_winks
/members?pid=1&pagetitle=view_friends
/members?pid=1&pagetitle=my_favourites
/members?pid=1&pagetitle=my_matches
/members?pid=1&pagetitle=alerts
/members?pid=1&pagetitle=blocked

Reference article: http://codex.wordpress.org/Using_Permalinks

Thanks for the heads up on this request for support.

s2Member Pro relies upon these fields for tax calculations, and also for AVS matching against fraud screening filters provided by Authorize.Net. While it’s true that Authorize.Net does not absolutely require them, my experience shows that NOT collecting them, can lead to fraudulent transactions, and scrutiny from the Authorize.Net team.

That being said, you are free to remove them if you wish. You will need to create your own custom Pro Form template for checkout, based on the the one provided by s2Member Pro. Please see: Pre Sale FAQs » Is it possible to modify s2Member® Pro Form templates?

Then, in order to bypass s2Member’s server-side validation against these fields, you will need to edit this file:
/s2member-pro/includes/classes/gateways/authnet/authnet-responses.inc.php

Please remove this section of code (starting at line #756) which requires these fields to be submitted:

/* ----------------------------------------------------------------------------------------------------------------- */
else if(in_array($s["card_type"], array("Visa", "MasterCard", "Discover", "Amex", "Maestro", "Solo")) && (!$s["street"] || !is_string($s["street"])))
	$response = array("response" => _x('Missing Street Address. Please try again.', "s2member-front", "s2member"), "error" => true);
/**/
else if(in_array($s["card_type"], array("Visa", "MasterCard", "Discover", "Amex", "Maestro", "Solo")) && (!$s["city"] || !is_string($s["city"])))
	$response = array("response" => _x('Missing City/Town. Please try again.', "s2member-front", "s2member"), "error" => true);
/**/
else if(in_array($s["card_type"], array("Visa", "MasterCard", "Discover", "Amex", "Maestro", "Solo")) && (!$s["state"] || !is_string($s["state"])))
	$response = array("response" => _x('Missing State/Province. Please try again.', "s2member-front", "s2member"), "error" => true);
/**/
else if(in_array($s["card_type"], array("Visa", "MasterCard", "Discover", "Amex", "Maestro", "Solo")) && (!$s["country"] || !is_string($s["country"])))
	$response = array("response" => _x('Missing Country. Please try again.', "s2member-front", "s2member"), "error" => true);
/**/
else if(in_array($s["card_type"], array("Visa", "MasterCard", "Discover", "Amex", "Maestro", "Solo")) && (!$s["zip"] || !is_string($s["zip"])))
	$response = array("response" => _x('Missing Postal/Zip Code. Please try again.', "s2member-front", "s2member"), "error" => true);
/* ----------------------------------------------------------------------------------------------------------------- */

Thanks for the heads up on this thread.

Yes, thank you for reporting this. The file l10n.js is no longer needed in the current WP release. We’ll have this updated in the next maintenance release of s2Member to prevent 404 errors.

Note: l10n.php is something different, it’s not a replacement.

Thanks for the heads up on this request for support.

I’m sorry, but there’s not currently a UI for browsing IPs associated with security breaches. The closest you can get in the UI, is to pull up the user’s account in WordPress, and then check the box to reset IP Restrictions for a specific user. It’s also possible to reset all IP Restrictions from the s2Member -> Restriction Options panel.

Until this feature becomes possible, here’s a function that pulls the information (based on username), in case you’d like to integrate something of your own.

<?php
function s2_login_ips_for($username)
{
	$ips = get_transient('s2m_ipr_'.md5('s2member_ip_restrictions_'.strtolower($username).'_entries'));
	
	// This returns an associative array containing all IPs the user has logged in with, over the last 30 days.
	// Array keys are IP addresses, and array values are timestamps.
	return (is_array($ips)) ? $ips : array();
}
?>

Example usage:

<?php
$user_id = 1;
$user = new WP_User($user_id);
$username = $user->user_login;

foreach(s2_login_ips_for($username) as $ip => $time)
	echo 'You logged in at '.date(DATE_RFC822, $time).' from: '.$ip.'<br />';
?>

Thanks for the follow-ups here.

Thanks for the heads up on this request for support.

Yes, Raam is correct. s2Member’s Authorize.Net integration uses the Authorize.Net ARB system, and in addition, EOTs are suppose to be handled internally by s2Member, so that a customer recieves access to time they’ve already paid for, even after a cancellation occurs.

If this continues to be a problem on your installation, please enable s2Member’s logging routines. Then submit a private Dashboard login for us to review your installation. We’ll be happy to assist with this. Please use: s2Member® » Private Contact Form

See: Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details -› Logging

Thanks for your patience.

Thanks for the heads up on this thread.

The original question was about Google Checkout
Can we setup subscriptions for S2 customers, where they can pay by credit card ?

No, Google® Checkout, very much like PayPal Standard and/or Express Checkout — requires that each customer be associated with a Google account (or be willing to signup for one). That is, a Google® Checkout account (aka: a Google® Wallet).

If you’d like to accept credit cards directly, I recommend PayPal Pro, operating with s2Member Pro Forms. This allows you to accept credit cards directly on your site, and also offer PayPal Express Checkout as an option, to those who prefer to pay with PayPal.

If that’s not an option, I recommend PayPal Enhanced Recurring Payments, which makes it possible to accept credit cards through PayPal Standard Buttons (i.e. no PayPal account required during checkout, even for recurring payments). This is something you’d want to speak with PayPal about. Note that PayPal Enhanced Recurring Payments is NOT as flexible as a PayPal Pro account, so I offer this as a secondary option only.

Thanks for the heads up on this request for support.

Yes, the affiliate program integration supplied by ccBill® is compatible with s2Member.

The actual checkout process for transactions submitted through ccBill®, occurs at ccbill.com; so tracking occurs there (automatically). There’s no need to integrate anything further with s2Member. All you need to do is configure your affiliate offering within your ccBill® account, and that’s it.

If you’d like to integrate another affiliate software application, like iDevAffiliate® (as one example), that can be accomplished with s2Member, through one of various methods available. Either through API Tracking codes, or with one of several types of API Notifications.

See: Dashboard -› s2Member® -› API / Tracking -› Signup Tracking Codes
See: Dashboard -› s2Member® -› API / Notifications -› Payment Notifications

Thanks for the heads up on this request for support.

Yes, this looks very strange indeed. A 4020 error would certainly indicate an issue with your PDT Identity Token from PayPal. However, it could also be caused by corrupted HTTP communication, or with PayPal account settings. Here are some things I would take a look at.

1. Is Auto-Return enabled in your PayPal account Profile? PDT and Auto-Return work hand-in-hand. While having Auto-Return off should not produce this type of error, I think it’s worth taking a look at anyway, just to rule out the possibility of a strange PayPal behavior in this regard. Please make sure Auto-Return is “on” in your PayPal account, and that “PDT” is enabled as well.

2. If problems persist, I’d take a look at the HTTP communication that’s occurring, even closer.

Please create this directory and file:
/wp-content/mu-plugins/http-api-debug.php
( these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins )

<?php
add_action('http_api_debug', 'http_api_debug', 1000, 5);
function http_api_debug($response = NULL, $state = NULL, $class = NULL, $args = NULL, $url = NULL)
	{
		$log = array('state' => $state, 'transport_class' => $class, 'args' => $args, 'url' => $url, 'response' => $response);
		file_put_contents(WP_CONTENT_DIR.'/debug.log', print_r($log, TRUE)."\n\n", FILE_APPEND);
	}

Then run your tests again. Check the /wp-content/debug.log file for further details about HTTP communication.