Jason (Lead Developer)

Thanks for the heads up on this thread.

@ Peter Hall

You are correct. s2Member converts all date calculations on the s2Member side of things, into days for it’s integration with Authorize.Net. Therefore, a monthly charge becomes “once every 30 days” according to s2Member Pro. I’m going to have this updated in the next maintenance release, to accomodate true monthly billing as mentioned in the context of this thread. Until then, you may unzip and upload the attached file, allowing it to override your existing copy of /s2member-pro/includes/classes/gateways/authnet/authnet-utilities.inc.php

http://d1v41qemfjie0l.cloudfront.net/s2member/uploads/authnet-utilities.inc_.php_1.zip

Thanks for the heads up on this thread.

What was the original payment for exactly?
Was it for X number of days/weeks/months/years?
Was that initial term completed prior to the cancellation taking place?
If you can post the original s2Member PayPal Button Shortcode the customer used to purchase, that would be great.

Thanks for the follow-ups.

Details received via email for http://www.troop80-bsa.com
~ Investigating the site now.

Thanks for the heads up on this thread.

Add one of the following variables please.

txn_id = A unique transaction ID.
or... subscr_id = A unique subscription ID (recommended in this case).

See also: http://www.s2member.com/paypal-ipn-pdt-vars

Thanks for the heads up on this thread.

As Cristian mentioned, this bug was corrected in the last maintenance release of s2Member Pro v121023. Please upgrade to the latest version and try this again for us. If the problem persists, please let us know!

http://www.s2member.com/forums/topic/authorize-net-error-92/#post-23908

s2Member Pro integrates with Authorize.Net AIM.

Thanks for the follow-up.

I had never been in the Alternative View Protection Area prior to this moment…. Thank you for that info. I have unchecked the item…. My guess is that this must have happened when I upgraded???

Yes, it may have happened during an upgrade… but only if you had selected the “all” option in the Dashboard at some point. Earlier verisons of s2Member did NOT include Nav Menus as an option here, but if you had “all” selected prior to upgrading, the “all” option having been selected prior, would result in the automatic inclusion of Nav Menus as well, which is a feature introduced in more recent versions of s2Member.

Very sorry for any confusion.

Investigation completed.

Upon a review of both of these log files in /plugins/s2member-logs/:
paypal-api.log and paypal-payflow-api.log

I find that s2Member Pro was successful as recently as Oct 26th (today) in speaking with your Payflow API, as is indicated by this portion of your s2Member Pro log file: paypal-payflow-api.log.

'RESPMSG' => 'Approved',
'PROFILEID' => 'I-NTFT6JVEG690',

I also find that s2Member Pro fails to get a valid result from the Payflow API for this section of your log file, pertaining to Recurring Profile ID: I-G1F4EG4835TD (and others like this one).

'TRXTYPE' => 'R',
'ACTION' => 'I',
'TENDER' => 'C',
'ORIGPROFILEID' => 'I-G1F4EG4835TD',

...

  'RESULT' => '1000',
'RESPMSG' => 'Generic processor error: 11546-Profile ID is not valid for this account.  Please resubmit request with the correct profile ID.',
'HOSTCODE' => '11546',
'TRANSTIME' => '2012-10-26 06:55:54',
'__error' => 'Error #1000. Generic processor error: 11546-Profile ID is not valid for this account.  Please resubmit request with the correct profile ID.',
)

The reason for this error (which you’ve already spoken to PayPal about), is two different PayPal accounts having been used for a single installation of s2Member Pro (and also with two different API flavors).

What’s happened is that at some point, you ran this site with s2Member Pro running under a completely different PayPal account. Now you’ve changed to a new PayPal account (which is also using a different API flavor… you’re now running a PayPal Pro account with the Payflow edition), and s2Member is trying to pull details related to existing user subscriptions that were created with the previous integration, but those details are unavailable, because the PayPal account that was integrated previously is no longer in use (i.e. s2Member Pro is communicating with your new PayPal account via the Payflow API).

As a result, any queries made by s2Member Pro to collect details (perhaps to analyze existing subscription details prior to an upgrade, downgrade, or cancellation attempt made by a customer), are failing.

The difference between APIs would be one problem, but with both of these problems combined, I’m afraid there’s no solution that I can offer, other than to wipe away any existing integration details associated with old customers (e.g. those created prior to Oct 4th), and to keep all information associated with new members (e.g. those which were in fact created with the PayPal account you intend to keep, starting on Oct 4th I believe).

According to your log files, the last communication that s2Member Pro had with your old account, was on Oct 3rd. So my advice is to go through all of your existing members (those which paid prior to Oct 4th), and simply empty (delete) the Paid Subscr. ID field provided by s2Member in your Dashboard. You’ll need to do this manually, for each paid customer that signed up prior to Oct 4th.

While this solution is not nearly as elegant as I would prefer, it’s the only way forward that I see for you. By removing those old Paid Subscr. IDs, you’ll eliminate any further errors going forward. At the same time, your existing customers may continue to enjoy their paid access, and no service interruption will occur.

Up sides:

• No more errors associated with Recurring Profile IDs created under the previous PayPal account.
• No more confusion about which PayPal account is integrated with s2Member Pro.
• While the connection between s2Member Pro and the old PayPal account will remain broken for these members that joined prior to Oct 4th, those members will continue to have access, and so long as your old PayPal account remains open, billing will continue to occur at the proper intervals, as established when the billing profiles were originally created.

Down sides:

• Members that joined prior to Oct 4th (if they cancel or fail to make payments), s2Member Pro will have no way of communicating with the old PayPal account (e.g. no way to respond to these events in any automatic way). Thus, these members will have ongoing access, until such time as you decide they should be demoted manually (should the need for that arise some time in the future).

Without the shortcode, offering only free memberships to my users will not work, so I am stuck with using only level 0. It’s entirely possible that the problem is being caused by my theme, but I have spent a lot of time designing the site with my theme, I love the functionality of the theme, I paid for the theme, and I’m not willing to start from scratch because your plugin is incompatible with it.

This is NOT a valid claim against our product. If you suspect the shortcode issue is related to theme compatibility, you will need to (a) chose a different theme; or (b) work to resolve the issue with compatibility (either with our help, or on your own – perhaps with the assistance of your theme designer).

We (and other customers) have all confirmed that shortcode processing against s2Member’s WordPress shortcodes DOES work flawlessly against a default WordPress installation. In addition, we are not aware (and we in fact know first hand), that s2Member’s shortcodes are parsed properly 99.9% of the time, regardless of which other plugins and/or themes are in use. The fact that you’re having a problem with shortcodes, suggests there is a deeper issue that needs to be resolved on your installation. If you suspect your theme, please disable your theme temporarily, reverting back to the default WP theme. If the issue is resolved, please contact your theme developer for assistance, or consult the documentation for your theme.

Please see: http://www.s2member.com/terms/#s2-terms-warranty

I wanted S2M Pro for the import feature, but when I found out that it wouldn’t email members their passwords upon import, that feature became useless to me too. How would I let 125 people know what their passwords were?

This is also NOT a valid claim. While I understand your desire to have the ability to email your customers immediately upon import, this is NOT a feature that is offered with s2Member Pro, nor is it advertised as a feature provided by s2Member Pro. Our list of features at s2Member.com states only the following.

Thus, emailing members their password, in whatever way you choose to accomplish this, will need to be made possible through custom coding, or perhaps with another plugin. I believe we’ve already made some recommendations/suggestions for you regarding this issue. In the mean time, we’ve accepted this as a feature request, to be considered in a future release of s2Member Pro.

Without the shortcode, offering only free memberships to my users will not work, so I am stuck with using only level 0. It’s entirely possible that the problem is being caused by my theme, but I have spent a lot of time designing the site with my theme, I love the functionality of the theme, I paid for the theme, and I’m not willing to start from scratch because your plugin is incompatible with it.

This is NOT a valid claim against our product. If you suspect the shortcode issue is related to theme compatibility, you will need to (a) chose a different theme; or (b) work to resolve the issue with compatibility (either with our help, or on your own – perhaps with the assistance of your theme designer).

We (and other customers) have all confirmed that shortcode processing against s2Member’s WordPress shortcodes DOES work flawlessly against a default WordPress installation. In addition, we are not aware (and we in fact know first hand), that s2Member’s shortcodes are parsed properly 99.9% of the time, regardless of which other plugins and/or themes are in use. The fact that you’re having a problem with shortcodes, suggests there is a deeper issue that needs to be resolved on your installation. If you suspect your theme, please disable your theme temporarily, reverting back to the default WP theme. If the issue is resolved, please contact your theme developer for assistance, or consult the documentation for your theme.

Please see: http://www.s2member.com/terms/#s2-terms-warranty

I wanted S2M Pro for the import feature, but when I found out that it wouldn’t email members their passwords upon import, that feature became useless to me too. How would I let 125 people know what their passwords were?

This is also NOT a valid claim. While I understand your desire to have the ability to email your customers immediately upon import, this is NOT a feature that is offered with s2Member Pro, nor is it advertised as a feature provided by s2Member Pro. Our list of features at s2Member.com states only the following.

Thus, emailing members their password, in whatever way you choose to accomplish this, will need to be made possible through custom coding, or perhaps with another plugin. I believe we’ve already made some recommendations/suggestions for you regarding this issue. In the mean time, we’ve accepted this as a feature request, to be considered in a future release of s2Member Pro.

Thanks for the heads up on this thread.

@ Greg Dalberri

I’ve just reviewed your request for a refund. We’ll be happy to process a refund for you, but only if the following conditions are met please (see our NO REFUND policy below). Cristian has asked you to confirm some additional questions related to the issue you’ve been having with AWeber. To our knowledge, there is no bug in the s2Member integration with AWeber. If we find there is, we’ll be happy to refund your money. In the mean time, please continue the conversion with Cristian. I feel that he is on the correct path to resolving this for you. That path is aimed at identifying the underlying cause, which we are not convinced is an issue with s2Member at this time. If that view changes, a refund will be processed for you.