Cristián Lávaque

Great! Thanks for confirming it! I’m glad it was so simple. :)

I checked your Auth.Net account details in s2Member and, although I can’t verify they’re right because I don’t have access to your Auth.Net account, I can tell that the MD5 hash seems really short in your configuration. These are usually 32 characters long, yet yours is just 7 chars long.

Could you double check that you have your configuration right? All the fields here: [hilite path]Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details[/hilite]

Thanks!

I can’t find something that tells me what could be causing the behavior you mention, with the user’s punishment continuing long after the time it’s supposed to last according to your Unique IP restriction setting.

I’ll forward this to Jason and wait for his opinion, and maybe testing, to find what the cause may be.

By the way, I checked your installation with a script we have and it threw a couple warnings you may want work on. http://yoursite.com/s2member-server-check-120703.php (You had another similarly named file, but it was an older, more limited version of the script I used this time.)

Sorry, I hadn’t noticed it. It was caught in the server’s spam folder and I only realized it after you told me you had sent it. I’ll look at it now…

Got ya.

Well, I don’t want to raise your interest in the new s2Member, since you’ve already waited this long, but it may be able to do what you describe here: give the user one ccap, and then create child ccaps, which give new access to the user with the parent one.

That’s why I asked about how urgent it is. Jason is still working on this, but he is close to beta for testing now, and I’ll try to have you in the testers team, if you want to. But no date for it yet, don’t know it myself.

If you don’t want to wait, which is understandable, you may want your developer to look into it based on the suggestions I made earlier in this thread, or any new ideas he may have.

Hi Tim.

Perhaps add some information about PayPal Payflow Pro as well if s2member supports it?

You mentioned PayPal’s PayFlow Pro, so I wanted to clarify this: s2Member Pro doesn’t integrate with it yet.

s2Member Pro integrates with PayPal Pro. Now, depending on the PayPal Pro account you have, it may use the PayPal Pro API or the PayFlow API for the Recurring Billing service. The latter is called PayPal Pro (PayFlow Edition). It’s a naming mess that PayPal is doing with these products, confusing everybody.

So, depending on the API your PayPal Pro account uses, you’d need to configure the PayFlow settings or not in your s2Member PayPal Options page. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› PayFlow[/hilite]

Haven’t heard from Jason yet, but I did a test creating an admin for a child blog in a multisite network without s2Member Pro. Logged in with this account making sure it wasn’t an admin for the network, just the blog, and it had the link to add a new user, it wasn’t disabled.

I don’t know why you don’t have the Add New User link available. Are you sure you are logged in to an admin account? Is it there if you deactivate s2Member? Do you have another active plugin that may be changing this in your installation? Try deactivating them to see if it changes. Have you done any WP role editing?

Okay, so what’s the conclusion you reached after the tests?

/wp-signup.php may not be available to people if registrations are closed, but that would not give a redirection to the Membership Options page, much less one that doesn’t exist. When registrations are closed, /wp-signup.php says “registration has been disabled”, no redirection.

But I see that you’re now taken to /register/ as BP wants it, and the proper message about closed registrations is shown now. Cool, what was the problem with that? Something from .htaccess tests?

This issue has to be incompatibility between the S2 restriction option level 1 = ‘/microsites/create/ or just /create/’
and the Buddypress plug allowing a non S2 level 1 user to get ‘redirected’ back to S2 options.

Well, I haven’t had experience with BP’s /microsites/create/ combined with s2’s URI restriction before, but it wouldn’t surprise me to see something odd, happen. Especially if you have two URI strings match at different levels: /microsites/create/ will match /microsites/create/ but also /microsites/.

When you’re trying to solve something with too many variables, it’s much harder than doing, and uncertain than testing, one thing at a time.

What I’d do in your situation is deactivate s2Member for a moment and test how BuddyPress works by default. Then I’d deactivate BuddyPress and activate s2Member and see how that works. Then I’d have them both active, and apply only one restriction at a time with some testing for each.

With each round I’d test: wp-signup.php, /register/, /microsites/create/, at least, and with users at different levels each.

And remember to put -at least some of- the Membership Options page vars, so you know what’s sending you there when it happens (e.g. “was it the Level 1 or Level 0 URI restriction?”)

If you don’t want to touch what you have, you can install a clean WP and set it up for the tests. The cleaner, the better for the tests, cause then you don’t have hidden things from previous tests you did, like the .htaccess thing throwing another variable at it. Don’t add more plugins until you sort those behaviors out between s2 and BP, again: less variables.

I hope that helps find what the issue is being. :)

Great! Glad you sorted it out. Thanks for the update, Adam. :)

Well, you could sell a Specific Post/Page with the link to the protected file with a download key so the user is not required to have an account at a certain level or with a custom capability.

Video » s2Member (Specific Posts/Pages)
[hilite path]Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions[/hilite]

I hope that helps. :)

No problem, glad I could help and that it’s working! :)

Hi Tony.

There isn’t a replacement code available in emails for the level. I’ll let Jason know that you asked about this and add it to the feature requests.

One thing you could do is integrate with a service like MailChimp/AWeber, so the user gets added to a particular list based on the level he got, and send the email from there. Video » s2Member (API List Servers)

I hope that helps. :)

Hi Leah.

I googled that error and found that you probably have the Company field set to required in your Authoriz.Net account. Just make sure that isn’t the case and the error may go away.

http://community.developer.authorize.net/t5/Integration-and-Testing/Error-quot-Bill-to-Company-is-required-quot/m-p/14074#M8326

http://www.zen-cart.com/showthread.php?72741-quot-Bill-to-Company-quot-error-What-!&p=416489#post416489

I hope that helps. :)