Raam Dev

Could you try redirecting to just https://legacymovement.net/checkout-thank-you/ and testing again? Also, it’s a shot in the dark as I don’t think this matters, but try adding the success=”” attribute to the end of the shortcode instead of the beginning.

As a last resort, I’d try disabling all other plugins and testing again, as the most likely cause of an issue like this is a conflict with another plugin.

You’re most welcome. Glad I could help! :)

Hi Thomas,

My apologies for the delay on this. I heard back from the lead developer and this is what he said:

“Great question. s2Member Pro does support response filters from the Authorize.Net APIs.

Please create this directory and file to eliminate the response code from the error message, and instead report only the textual representation reported by Authorize.Net. With a little more hacking/understanding, a site owner could certainly work some magic of their own (i.e. custom messages for certain error codes).”

/wp-content/mu-plugins/s2-hacks.php

<?php
add_filter('ws_plugin__s2member_pro_authnet_aim_response', 'my_authnet_response_filter');
add_filter('ws_plugin__s2member_pro_authnet_arb_response', 'my_authnet_response_filter');

function my_authnet_response_filter($response = array())
{
	if(!empty($response&#91;'__error'&#93;))
	{
		$response&#91;'__error'&#93; = $response&#91;"response_reason_text"&#93;; // Use error text only (excluding error codes).

// See also: $response&#91;'response_reason_code'&#93; to help identify certain response codes (if you like).
// When debugging, use print_r($response) for a full list of data about each response.
// Also check the /s2m-pro-extras.zip file, for the documentation regarding the Authorize.Net API error codes.
	}
	
	return $response;
}
?>

Tim,

I’ll send Jason a message to see if he can take a look at your site, but it’s hard for us to diagnose problems that may be caused by 3rd party plugins, which is why disabling *all* the plugins is the only course of action in scenarios like this.

Hi Robert,

You will need to consult with your web host to resolve the Temporary Files Directory error. Once that has been fixed, please try running another test.

Hi Wayne,

I’ve tested s2Member on my own mobile phone (an iPhone 4) and it blocks content as expected.

Can you provide more information about what’s happening and what you’re testing with? If you can give an example URL to test with, that would help as well.

Hi Kevin,

While s2Member is compatible with WordPress Multisite Networking, the sites within a WordPress network are separate and not interconnected. That means you cannot share users, logins, or other data across the sites (including access control).

Please see the following from WordPress.org:

The sites in a multisite network are separate, very like the separate blogs at WordPress.com. They are not interconnected like things in other kinds of networks (even though plugins can create various kinds of interconnections between the sites). If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution.

The s2Member Multisite feature allows you to offer the s2Member plugin to sub-sites, giving your sub-sites the ability to setup and use s2Member on their own. When you upgrade s2Member on the primary site, the s2Member plugin is automatically updated for all your sub-sites. However, things like access restrictions on one WP installation are not shared across WP installations (again, the WordPress Multisite feature itself isn’t designed to work like that).

There are plugins that allow you to get around these WordPress Multisite limitations, however they may or may not work with s2Member.

Hi Kevin,

cassel is correct. The s2Member Pro Coupon codes cannot currently be restricted to specific member levels, however you can restrict coupon codes to specific WordPress Post/Pages.

For example, if you had three pages, with a signup form on each page, you could create a coupon that only works on one of those pages. For example:

Level 1 Signup form on Page Id #123
Level 2 Signup form on Page Id #124
Level 3 Signup form on Page Id #125

Now, if you create a coupon SAVE-10|10%|||124, the SAVE-10 coupon will only work on the signup form that you’ve placed on the page with ID #124 (in this case, the Level 2 signup form).

Please see Dashboard -› s2Member® -› Pro Coupon Codes -› Coupon Code Configuration File for more information and examples.

Hi Ben,

Since the recurring payments are processed by the gateway and not s2Member itself, this is not currently possible. s2Member has no knowledge in advance that a recurring payment will take place. It only gets notified when a payment has been made or fails (via the IPN messages).

To add such a feature, you’d need to write some PHP code that builds a database table whenever someone makes a purchase and records the length of the recurring membership. That way you could periodically check the table to see if any recurring transactions will be occurring in the next two weeks.

Peter,

The Login Welcome page (Dashboard -› s2Member® -› General Options -› Login Welcome Page) is the page that users see after logging in.

If a non-member (or someone not logged in) tries accessing a protected page, s2Member will redirect them to the Membership Options Page (Dashboard -› s2Member® -› General Options -› Membership Options Page).

With s2Member you can generate payment buttons/forms that include an Initial amount. So, if you were charging $100/year and you wanted to charge $25 “setup fee”, you could do that. s2Member would charge them $125 to sign up, but then the recurring amount would be $100/year.

Jeremy,

There are two important things to understand here:

1. Access to files protected by s2Member can be given in two ways: First, by specifying the level of access that is required. For this, a member must be logged in to gain access to the file. The second way is by generating a download key (see Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions) and including that key in the URL to the file. With this method, the person accessing the file does not need to be a member and does not need to be logged in to your site… as long as the URL contains the download key, access will be provided.

2. The Specific Post/Page feature of s2Member is designed to sell things on a one-time basis, in a way that does not require a membership account. For this to work, s2Member generates a unique URL to the post or page that the person purchased. This URL contains a special key that tells s2Member things like how long access to the post/page should be given and which page/post the access is for.

It’s important to understand that these URLs are different: One is for accessing protected files, the other is for accessing protected pages/posts.

When you sell access to a post/page using the Specific Post/Page feature, the person accessing the page will not be logging into your site. So, if the page they’re accessing contains a protected video, the video must not be protected using membership-type restrictions. (See my two descriptions of protected files above.)

If you want to protect your video files with s2Member and sell access to the pages where those videos are loaded using a URL generated by the Specific Post/Page feature, then you must point your Video Player to video URLs that contain a special download key (again, you can read more about this on Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions).

If the URL to the video doesn’t have the special file download key, then when one of your Specific Post/Page buyers gains access to the page, they won’t have permission to view the video (because using the default download restrictions, access is determined by membership-level, which requires being logged in).