Jason (Lead Developer)

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

Invoice numbers are unique for every transaction that s2Member processes. They are not the best way to associate a User/Member with an ARB at Authorize.Net. Please use the ARB Subscription ID for this.

s2Member stores this value in the WordPress® database and you can search your list of Users by ARB Subscription ID in the Dashboard (aka: Paid Subscr. ID).

Thanks for the follow-up :-)

I investigated your installation and reviewed your s2Member® log files. As you mentioned, I find repeated log entries like this during s2Member’s attempts to communicate with the PayFlow API. Found inside: /plugins/s2member-logs/paypal-payflow-api.log

-------- Output string/vars: ( Fri Feb 8, 2013 7:08:50 pm UTC ) --------
RESULT=1&RESPMSG=User authentication failed
array (
  'RESULT' => '1',
  'RESPMSG' => 'User authentication failed',
  '__error' => 'Error #1. User authentication failed.',
)

This indicates one of three possible issues…

1. You do not have a PayPal Payments Pro account, you have a PayFlow-only account. s2Member® supports PayPal Payments Pro (PayFlow Edition) and PayPal Payments Pro (without PayFlow). However, s2Member® does NOT support PayFlow-only accounts. See: Knowledge Base » PayPal® Compatibility (Account Types)

2. You have a PayPal Payments Pro (PayFlow Edition) account, but you have entered details for s2Member® that PayFlow is rejecting. Please review your configuration here (Dashboard -› s2Member® -› PayPal® Options -› PayFlow™ Account Details), and also speak with PayPal Merchant Support to verify that you have the correct PayPal Pro (and PayFlow) API Credentials. I suspect this is the underlying issue on your installation.

3. You have a PayPal Payments Pro account (without PayFlow). From what you’ve said, I doubt this is case. However, if this IS the case, please remove your configuration from this section of the Dashboard, so that s2Member® is not attempting to communicate with the PayFlow APIs. See: Dashboard -› s2Member® -› PayPal® Options -› PayFlow™ Account Details

Please let us know if problems persist :-)

Thanks for the follow-up :-)

My problem still persists. I’ve checked everything and I can’t figure out why my S@ member restricted information is being revealed to non members. It’s now costing me a lot of money and I had the theme developer correct some broken issues with the theme hoping that it may have been the problem but it wasn’t. Can someone please have a good look at this and tell me what I am doing wrong? I have already set you up with a dashboard log-in previously. Please advise if you need it again.

If you feel the issue is NOT related to anything I discuss in the video, and you are unable to resolve this with s2Member’s Alternative View Restrictions, please submit a Dashboard login privately, along with instructions on how to reproduce the issue. We’ll run diagnostics for you. See: s2Member® » Private Contact Form

Thanks for the follow-up :-)

@Jason Thanks for the reply, we’ll try and set up a test installation, although surely it would be easier for you (can you not add the Easy Tables plugin to one of your test installations and see if there is a conflict with PayPal Pro forms?)

Please reproduce the issue that you had before on a test installation, and then send it to us for review. We can’t give a high priority to troubleshooting 3rd-party components and plugins, but if we’re going to investigate this for you; it would be nice to have it reproduced in the same environment in which the issue occurred, under the same configuration, etc. Thanks! See also: s2Member® » Support Policy

You may also want to contact the developer of the Easy Tables plugin for assistance on this. Between the two of us, maybe we work to resolve whatever conflict exists. Perhaps the developer of that component can offer some insight as well.

However, on the other matter raised (with Easy Tables plugin deactivated) about returning to the website from PayPal after agreeing the payment, getting sent to the link http://www.nbo.org.uk/membership/individual-member/?s2member_paypal_xco=s2member_pro_paypal_checkout_return&token=EC-XXXXXXXXXXXXXXXXX and the process stops – have you any ideas why this is happening?

Did you have logging enabled when you ran your tests? I just took a look at your installation and I find three log entries in the s2Member® Auto-Return log file (paypal-rtn.log). All three log entries were related to a preview from the Dashboard only, nothing from a test transaction yet.

See: Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging

array (
  'subscr_gateway' => 'paypal',
  's2member_log' => 
  array (
    0 => 'Test preview of Return Page `proxy_use`: ( `x_preview` ).',
    1 => 'Redirecting Customer to the Home Page. Test preview of Return Page `proxy_use`: ( `x_preview` ).',
  ),
  's2member_paypal_proxy' => 'paypal',
  's2member_paypal_proxy_use' => 'x-preview',
)

After more testing have now discovered that after getting to PayPal and after logging in and clicking the ‘Agree and Continue’ button which says I’ll be sent back to my site for confirmation of payment I get sent back to the original page:

http://www.nbo.org.uk/membership/individual-member/?s2member_paypal_xco=s2member_pro_paypal_checkout_return&token=EC-XXXXXXXXXXXXXXXXX

No payment is taken from PayPal and no user registered.

From reading the settings page I was expecting to return to a page like http://www.nbo.org.uk/?s2member_paypal_return=1&s2member_paypal_proxy=paypal&s2member_paypal_proxy_use=x-preview

Oh. I see now. You’re running s2Member® Pro Forms. The PayPal Auto-Return handler is used only in PayPal® Standard Button integrations. With Pro Forms, this is not necessary because the customer comes back to your Pro Form, where a message is displayed; thanking the customer on-site. Not with a generic thank-you page handler.

In short, the behavior you’ve described would be expected. If you would like to customize the thank-you page that works with your Pro Forms, please use the success="" Shortcode Attribute and create a custom thank-you page that contains whatever you like better.

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Custom Return URLs Upon Success
See also: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained)

Thanks for the follow-up :-)

That’s a beautiful site. Please let us know if problems persist.

Details received. Thank you!

~ Investigating now.

Thanks for the follow-up :-)

Please let us know if problems persist.

@ Vince DiPasquale

Please submit a Dashboard login privately and we’ll run diagnostics for you.
See: s2Member® » Private Contact Form

Unable to reproduce this so far. Sending this to Raam for further MAC testing.

Thanks for the heads up on this thread :-)

1. Is your Badge Status API enabled?

See: s2Member -> General Options -> Security Badge -> Badge Status API

2. Does your /wp-config.php file have all of these configuration values?

See: http://codex.wordpress.org/Editing_wp-config.php#Security_Keys
(each of these MUST be at least 60 chars, and must NOT contain: ‘unique phrase’)

3. Have you created a Security Encryption Key for your s2Member installation?

See: s2Member -> General Options -> Security Encryption Key
(this MUST be at least 60 chars as well)

4. Does your /wp-config.php file have both of these configuration values?

DB_USER and DB_PASSWORD. These must be filled in, and must NOT be the same value.
See: http://codex.wordpress.org/Editing_wp-config.php#Set_Database_Name

5. Have you configured your Unique IP Restriction Options yet?

See: s2Member -> Restriction Options -> Unique IP Restrictions
(this must NOT be set to: infinite)

6. Have you configured your Brute Force IP Restrictions yet?

See: s2Member -> Restriction Options -> Brute Force IP Restrictions
(this must NOT be set to: infinite)

7. If you visit this link on your WordPress® installation, you should get a plain text file that contains only a single value of: 1 (indicating your site is in the green w/s2Member®). If you don’t, one of the above is the likely cause.

See: http://jason.websharks-inc.net/?s2member_s_badge_status=1
This test installation is running WordPress® v3.6-alpha and the latest version of s2Member®.

Now look at your installation: yoursite/?s2member_s_badge_status=1

Thanks for your reply :-)

OK. So we still need to determine where this email is coming from. I understand now that you’re unsure about where it is coming from. If you’re unsure about this, let’s assume for a moment that it’s one of the following emails that you’re receiving.

1. The default email that comes to an Administrator whenever someone registers in WordPress®. This email is usually VERY basic (i.e. it would not contain any of those additional details unless a plugin was modifying this email for you).

2. You’re receiving an s2Member-modified version of the default email message; which is off by default in all s2Member® installations. If you’ve enabled this email notification customization; then you would know it.

See: Dashboard -› s2Member® -› General Options -› Email Configuration
Under this section, please see the customization options for the Administrative Notification.

3. It’s also possible that you’re receiving an email that you configured with another plugin; unrelated to s2Member®. Please advise. Thanks!

Thanks for the follow-up :-)

It actually looks like you might have made some modifications to s2Member? If not, please send us a Dashboard login so we can take a closer look at this for you. That’s a standard BuddyPress registration form, and s2Member already includes basic structural CSS that will cleanup that layout for you. It’s simply not being applied because your installation appears to be missing s2Member’s div wrapper around these custom fields.

Please advise. Thanks!

Please use: s2Member® » Private Contact Form