About: Bruce

Gotcha. Yes I can see why this wouldn’t work with multiple Pro Forms, but I honestly can’t tell you an easy way to get Username to go through validation.

This is because s2Member does something similar to what you were asking about with multiple of the same fields in your post:

another question i have: since the information is virtually the same but needs different codes: film_title, and film_title_2; is there an easy way to copy all the fields I need, and then just edit who the field is viewable by rather than remake each section three times?

The hack that Raam posted here will only check for the first of these fields. If you need to bypass all of the checks for Username, you’ll have to check the number of options there are, and alter the JavaScript code snippet to work correctly with each of the options. The part of the snippet you’ll want to focus on is here:

$ (email).keyup (function ()
                            {
                                $(login).val ($.trim ($ (email).val ().split (/@/)[0].replace (/[^\w]/gi, '')) + randomNum.toString());
                            });

Another developer familiar with JavaScript could throw something together here, but it goes beyond what I can do in just a forum post, sorry.

Thank you SO much! I deleted the other file and now it works!!! Thank you!!!!

Great! Sorry, this is the one thing that seems to get people with the security badge. This directory needs to be completely empty except for that .htaccess file for s2Member to verify your security badge. :-)

Hi Faith,

Sorry to hear you’re having problems with this.

The only thing I’m seeing here that you haven’t touched on is the s2Member Security Encryption Key. Is that set?

See: Dashboard -› s2Member® -› General Options -› Security Encryption Key

If that’s not it, then I would recommend logging into your site’s FTP server, and checking your /wp-content/plugins/s2member-logs/ directory, and ensuring that there is nothing but a .htaccess file in that directory.

Also, be prepared to allow up to 24 hours for s2Member change your Security Badge to green.

If that doesn’t help let me know. :-)

However…

Before diving right in I thought I’d follow your advice and read up about ccaps in the Dashboard but found that

So sorry, I linked to that from memory. That’s the old location of the documentation for Custom Capabilities. The real name of this section is Custom Capabilities (Packages).

My only problem now is that I no longer seem to be receiving the EOT from PayPal. And, when a level-1-user cancels their subscription, their recurring payment is cancelled in PayPal, but nothing appears to happen on site.

s2Member won’t immediately demote a User when they stop paying usually. Instead, it will set an Automatic End of Term time on their profile. I’d recommend looking at the profiles that have been canceled by a User and see if that EOT Time is set. If it is, then s2Member is working correctly, and that User will be demoted after the time that they have paid for is up (i.e. when they hit their EOT time).

s2Member should get notification of the recurring subscription being cancelled almost immediately.

There’s detailed information on Auto EOTs here:

Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior

If the EOT time isn’t set on the profile for the User it’s supposed to be, that probably means that there’s something wrong with your PayPal IPN setup. Try turning on logging here, and checking your PayPal settings to make sure that IPN is set up correctly:

Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration

Hi Glyn,

I think I can help answer your questions. :-)

(1) What does the “Custom String Value” do (i.e. custom=”” on a ProForm) and why does it contain the domain name?

The custom attribute is an attribute that PayPal gives s2Member access to, and s2Member uses it to verify that the transaction is meant for s2Member to process. s2Member checks that the custom attribute is set to your domain name (along with checking a few other values) to make sure that the transaction it’s getting is not meant for, say, an eBay sale, or a different site that you have your PayPal account hooked into. This should always stay as your domain name to prevent conflicts.

(2) What happens to a (level 1,2,3, or 4) user’s recurring payments if I change their role to author, editor or admin? What happens if I then change them back to level 1 again?

s2Member does not perform any changes when a recurring payment is performed to users. In fact, you could take someone that is paying for level 1 and manually push their account up to level 3, and s2Member will not demote at any point other than when they stop paying and lose access.

If you don’t want a User to be demoted even if they stop paying for access, you can simply remove their Paid Subscription ID from their profile, and s2Member won’t link the User’s transaction to their account anymore, making it impossible for s2Member to automatically demote them.

See: Dashboard -› Users -› Edit

(3) I understand that all financial details are held by PayPal, but does s2Member keep any record of how much a user has paid, which ProForm was used during signup, and which coupon codes were used?

No, s2Member won’t store any information like that by default. If you want to track your User types, I would suggest that you check out Custom Capabilities (ccaps). These (Custom Capabilities) are standalone capabilities that are given to Users on signup or upgrade and can be used to protect content or separate members aside from Membership Levels.

See: Dashboard -› s2Member® -› API / Scripting -› Custom Capabilities

To give you an example, you might give your Student members the Custom Capability “student”. Then, you can check if any particular User is a student with Shortcode Conditionals.

Example of using Shortcode Conditionals:

[s2If current_user_can('access_s2member_ccap_student')]
	You are a Student User!
[/s2If]

See: Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals

You can generate Pro Forms / Buttons with Custom Capabilities baked right in, or add them in later by editing the ccaps attribute that’s in your Buttons and Pro Forms’ Shortcodes.

Does that help?

@hundredvisionsguy

How can I modify the shortcode so the template attribute looks in the child theme folder instead of the parent theme?

The template attribute looks in your /wp-content/themes directory (or whatever your themes directory is set to) first if you provide it a template that way. You can move your custom template to your root theme directory, or keep it in your child theme’s directory, and instead change it to look in that directory (as in /child-theme/my-template.php).

@mrmacscience

Anyone know what would account for this change? And what does it mean? I didn’t change anything in the registration process.

I believe this is a change with WordPress’s storage functionality. This is essentially saying the same thing. The only difference is that s:1:”1″ means that there is a string with 1 character being stored, and the character is one; b:1 means that it’s storing a boolean 1, aka TRUE. They both equate to the same thing when you check them for being TRUE or FALSE (as WordPress will be). The only difference is the way it looks.

@mrmacscience

FWIW — I also noticed that since March, there have been a number of new users whose profile info looks fake. Mismatched combinations of cities, states, and countries; names and email addresses that appear to be randomly generated strings of letters, etc.

The best thing you can do to prevent spam registrations are to turn off the ability for Users to set their Passwords without receiving an email from you first, available in this part of the Dashboard:

Dashboard -› s2Member® -› General Options -› Registration/Profile Fields

Here’s that part of the Dashboard (click to see full image):

You might also want to switch to using a Free Registration Pro Form along with enabling an Captcha on this form to keep bots from creating accounts as well:

Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms

Thank you for your inquiry.

Sorry for the delay in response.

s2Member does not allow Users to be “reinstated” after a payment fails and PayPal sends s2Member a message telling it that the User’s Subscription is over (based on what you have set up in your Shortcode’s RRA attribute).

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained) -› rra

To have a User gain access after they have been demoted by s2Member, they need to sign back up at your site through s2Member again. Check out these forms for information on how you can let Users bump their account status back up:

Dashboard -› s2Member® -› PayPal® Pro Forms -› Billing Modification Forms

Thank you for reporting this important issue.

I would say that the likely problem here is with a Plugin/Theme Conflict (as @RandyKing mentioned). However I have also seen things such as this happen with special Apache rules on your server causing random errrors, or with Mod-Security.

See: Knowledge Base » Mod Security, Random 503/403 Errors

If using the information that Randy does not work, then I would suggest contacting your server provider to see if they can help. :-)

Thank you for your inquiry.

Sorry for the delay in response.

@davefft

How can i change that email link to point to wp-login_new.php? I’ve look everywhere, but no luck. I’d keep looking but my client’s sites s2Member functionality is not working so this is urgent.

You can change the link manually here:

Dashboard -› s2Member® -› General Options -› Email Configuration -› New User Email

You will need to change it so that s2Member is allowing you to edit the emails there. It should be pretty simple to make this change, but let us know if you have any problems. :-)

@lg

Before I give you Dashboard assess I want to know what you assume will happen to users based on our current setting. And yes, I have logging turned on.

Based on your current settings, Users should not ever get immediately demoted unless you issue them a refund, or they ask PayPal for their money back directly (i.e. a chargeback). At the top of this section the documentation covers this detail. I’m not sure why this would happen other than if a User both cancels and you give them their money back for the access they last paid for.

Thanks for your patience. Sorry about the delay. I’m taking a look at this and I’ll see if I’m able to reproduce this myself.