Bruce

Hi Mark,

Thanks for reporting this important issue.

s2Member’s processes have many reasons that they might fail to work properly, which can be diagnosed through the log files. Do you have Logging enabled? Please check Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details -› Logging. Once logging is enabled, can you please run a test transaction and post the log info from the files within /s2member-logs/ here, wrapped in <pre></pre> tags, please?

Hi Kim,

Thanks for the info!

She clicked the button and it canceled her subscription within PayPal. So far, so good.

Then I went into PayPal and refunded her payment. Nothing happened within s2Member.

As per the documentation under Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior:

*Some Hairy Details* There might be times whenever you notice that a Member’s Subscription has been cancelled through PayPal®… but, s2Member continues allowing the User access to your site as a paid Member. Please don’t be confused by this… in 99.9% of these cases, the reason for this is legitimate. s2Member will only remove the User’s Membership privileges when an EOT ( End Of Term ) is processed, a refund occurs, a chargeback occurs, or when a cancellation occurs – which would later result in a delayed Auto-EOT by s2Member.

s2Member will not process an EOT until the User has completely used up the time they paid for. In other words, if a User signs up for a monthly Subscription on Jan 1st, and then cancels their Subscription on Jan 15th; technically, they should still be allowed to access the site for another 15 days, and then on Feb 1st, the time they paid for has completely elapsed. At that time, s2Member will remove their Membership privileges; by either demoting them to a Free Subscriber, or deleting their account from the system ( based on your configuration ). s2Member also calculates one extra day ( 24 hours ) into its equation, just to make sure access is not removed sooner than a Customer might expect.

Essentially what this means is that s2Member will ALWAYS give the user access to whatever amount of time they originally paid for. When a user cancels recurring billing, s2Member is told to revoke access when the user was supposed to be charged once more.

Note that, also, if you are manually refunding a user, you will need to also manually demote them. So where you said that you refunded the user and they were not demoted, this is the expected behavior. The user will be automatically demoted by s2Member when the subscription ends, or you can manually demote them. This allows the most flexibility within the processes.

Hi Chico,

Thanks for your great question!

Since free pro registration forms are created using the paypal pro forms and we don’t have paypal pro in Australia will it still be possible for me to get the free registration forms working?

This is very possible. As of right now s2Member does require you to have PayPal info filled out within Dashboard -› s2Member® -› PayPal® Options -› Account Details to allow Free Registration Forms to work. You can, however, put “filler” or fake data in this section and s2Member will function correctly, assuming that you do not use anything other than Free Registration Forms.

Will I also be able to integrate Aweber with this forms and get it to work seamlessly?

s2Member fully supports Aweber for all signups, including free subscribers. You can check out info on integrating Aweber under Dashboard -› s2Member® -› API / List Servers -› AWeber®.

Hi there,

This is how s2Member’s processing this. The link that is generated in page is the link that you have set up here. If you’d like to automatically have it go to the page set up, add this to a Must-Use plugin file by putting this into a s2hacks.php file and uploading it to you /wp-content/mu-plugins directory (you may need to create the directory) via FTP:

Hi Patrick

It sounds like the thing to do here is set up custom capabilities, instead of using multiple membership levels. Find info on Custom Capabilities here:

Dashboard -› s2Member® -› API / Scripting -› Custom Capabilities
Video » s2Member (Custom Capabilities)

Hi Carlo,

You could possibly do this. The info in Knowledge Base » Protecting Non-WordPress Content with s2Member should be useful. You WILL need to one of the following things to get this to work, though.

1) Integrate your other web app with the WordPress database, and use the logins and SALT key within WordPress to access user data. This would be the most advanced and user-friendly route.

OR

2) Add an API that would send user data to the other app whenever a user is created/edited/deleted within WordPress, and vice versa. I would try to stay away from this if you can, but it is a viable alternative.

Both of these solutions require an advanced knowledge of PHP and you’ll want to get a developer to do this for you if you don’t feel comfortable doing it yourself. Note that this is something that’s set up outside of s2Member. You’ll be integrating WordPress with your Ruby on Rails app, not s2Member. You may be able to find some info on setting this up in the WordPress forums.

Hi Cassel,

There really isn’t a way to get this patched from within s2Member. I’ll let Jason know about the issue with wpautop, but I do not think that there is a way for this to be fixed within s2Member. This issue is more of an incompatibility between IE9 and wpautop than IE9 and s2Member.

However, I don’t think they are registered as “recurring commission”. Can someone point me to the right direction please?

Jason posted something in the old forums that explains how this works:

http://www.primothemes.com/forums/viewtopic.php?f=4&t=6275&p=14129#p14111

Hi Kelli,

The best way to do this would be to set up a simple PHP script under Dashboard -› s2Member® -› API / Notifications -› Signup Notifications and Dashboard -› s2Member® -› API / Notifications -› Modification Notifications. You can have s2Member send this info to a file and that file can mail the email automatically.

Hi there,

This is currently not possible through s2Member as stated in Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained):

accept=”paypal,visa,mastercard,amex,discover,maestro,solo” Accepted Billing Methods. A comma-delimited list of Billing Methods you want to accept. Due to a PayPal® policy, you may NOT exclude PayPal® from this list; s2Member won’t let you. Not valid when cancel=”1″.

If you’d rather not accept PayPal, then I’d recommend checking out the other processors that s2Member has. Authorize.net sounds like it would work better for you.

Carmen,

It looks like this may be an issue related to sandbox (See: http://www.s2member.com/forums/topic/error-1-user-authentication-failed-2/). You started getting Error #1 after you started using Payflow which leads me to believe that this is probably caused by Dashboard -› s2Member® -› PayPal® Options -› Account Details -> Developer/Sandbox Testing? being set to ON. Can you check and see what you have set up there?

Also, if that’s NOT on, can you please copy the data in the log files you listed out in your previous post and post some of the data in the files here, wrapped in <code></code> tags?

Jorge,

I can’t really say what the problem is from that code. You should have two plugins, one on the blog that’s adding users to the other, and one that’s receiving the data and using it to edit user roles/capabilities, correct? Could you post the other snippet, and only comment out the sections that you’re not using.

Note: You have an error with commenting on this which is probably causing things to pop up on your website.

Hi Alan

I’m very, very sorry about the delay

The only other way I see to accomplish this is like so:

add_action('ws_plugin__s2member_before_configure_user_registration', 'ss_registration_validation');

function ss_registration_validation($vars = array()) {
	$_p = $_POST;
	
	if(!isset($_p['ws_plugin__s2member_custom_reg_field_field_name']))
		exit('Error: you have attempted to pass an invalid configuration.');
}