Cristián Lávaque

http://wordpress.org/extend/plugins/s2member-control/

Seems nice. It gives a page where you can set some types of exceptions to the s2Member restrictions. It could be useful in some cases, yes.

Haven’t tried using it yet, so I don’t know how well it works. Just installed and activated it to see the admin settings for it. [hilite path]WP Admin -> Settings -> s2Member Control[/hilite]

I also noticed that you have an older version of s2Member, it’d be good to update to the lastest.

Yeah, it’s fine to have the billing update form, but I’d first complete the transition to avoid more complications. The transition should not take too long.

If you really need to have the billing update form for users, then you could put it inside a condition that checks whether the person has a subscr. ID before showing it, so those users you edited to remove it, won’t be shown the form.

As for testing it, I don’t think that’s possible because this is happening rarely. Too rarely to successfully and consistently reproduce with a test.

I see. It’d be good if you could find a common denominator between them… Did you review and compare the log entries for those specific transactions?

4) user profile s2member payment fields not updated (left empty)
5) payment notification never fires

The payment notification not happening is most likely because of the auto-login. Does it happen with other transactions, or it just never happens?

You could modify the auto-login hack, removing the redirection in the last line. Then the user would be logged in, but not redirected and the script can work normally. If you really need a redirection, test where the user ends up normally and see how you could add the redirection there.

Payment fields not updated seems to be a problem in only those rare cases, right?

we took authorize.net out of test mode

Was going to suggest this, but when I looked at your Auth.Net settings in s2Member, you had not set it to testing, so I assumed you were doing live transactions. [hilite path]Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details -› Sandbox[/hilite]

If your account was set to testing, but s2Member wasn’t, that would result in failed tests. And when you set the account to live and it matched the setting in s2Member, it worked. Pretty much what you had found here: http://www.primothemes.com/forums/viewtopic.php?t=6578&p=15978#p16599

We set up a PayPal Sandbox account to try and circumvent the problem and ran into the same issue.

I don’t recommend the PayPal Sandbox, it’s much better to do live 1 cent transactions for your tests. The Sandbox introduces its own problems which you then have to fix, making it more complicated although they won’t exist in the live transactions.

Default theme resulted in ajax function for password strength indicator working but form still displaying after successful submission. Why?

Then the theme you’re using is affecting the JavaScript in some way, it’d be good to find why and fix it.

About showing the pro-form to the user again after payment, are you using the [hilite mono]success[/hilite] attribute? [hilite path]Dashboard -› s2Member® -› Authorize.Net® Pro Forms -› Custom Return URLs Upon Success[/hilite]

The pro-form in the test page doesn’t have it:

[s2Member-Pro-AuthNet-Form level="1" ccaps="" desc="$0.01 USD / One Time ( for lifetime access, non-recurring, no trial )" cc="USD" custom="golfgurls.com" ta="0" tp="0" tt="D" ra="0.01" rp="1" rt="L" rr="BN" rrt="" accept="visa,mastercard,amex,discover" coupon="" accept_coupons="0" default_country_code="US" captcha="0" /]

If your thank-you page is at /gettinggolfready/thank-you/, then the attribute would be [hilite mono]success="ht[/hilite][hilite mono]tp://golfgurls.com/gettinggolfready/thank-you/"[/hilite]

Hi. I wanted to respond with the resolution of this issue. It appears we have solved this issue, thankfully!

That’s great! Thanks for the update. :)

Its a very long and convoluted story, but basically they mistakenly created 2 accounts for me back this summer and PayPal looked at the wrong account the entire time they were trying to figure out my issue!

PayPal…

I also have one more slight issue that just popped up.. we just noticed the members now are not being able to access restricted pages we have locked!

Could you please double check that the content is actually restricted by s2Member in some way?

Also please make sure that you have a Membership Options page set, or the restrictions won’t be applied. [hilite path]Dashboard -› s2Member® -› General Options -› Membership Options Page[/hilite]

And if you don’t have the Membership Options page set, but did before the update, please make sure that you have the Deactivation Safeguards enabled. [hilite path]Dashboard -› s2Member® -› General Options -› Deactivation Safeguards[/hilite]

Other than that, please try the suggestions in this article: Knowledge Base » Common Troubleshooting Tips

Cool. :)

Got ya. I’ll wait for your update. Have a great weekend!

When you test, try the suggestions here too: Knowledge Base » Common Troubleshooting Tips

Ah okay. I thought the emails would be personalized, so a unique link for each user would make sense, since it’s safer than one for everyone, because it could be shared.

If you want to protect the page so you send them a code they have to enter to view the page with the pro-form, maybe password protecting the page in the WordPress editor, may do what you want. Go to edit the page and you’ll find how to password protect it under [hilite path]Publish -> Visibility -> Password Protected[/hilite].

Thanks, I could login to the FTP this time. :)

I activated s2Member and don’t see the problems you mentioned. The s2Member Pro Login Widget is in the Widgets page, but not added to any widget area. And I don’t see any pages being restricted by s2Member in the Restriction Options.

Could you point me to the exact URLs I should look in and point me at what to look in those pages? You can send the URLs via email too if you want. Thanks!

Hi David.

It shouldn’t appear if you disabled it for that pro-form. You may be having a JavaScript conflict causing the pro-form to not behave as expected. Could you troubleshoot it following the suggestions in this article? Knowledge Base » Common Troubleshooting Tips I’d start with the theme test.

I hope that helps. :)

Hi Terry.

Yes, you can use the initial term for the first year, then the regular term would be the monthly payments. In the pro-form generator, it’s the line that says: I’ll offer the first ___ days at $___. [hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Membership Level # Forms[/hilite]

I hope that helps. :)