Cristián Lávaque

I took a new look at your site and realized that it’s a multisite network, so I went to the network administration plugins page and noticed many more plugins than I had seen before in the blog I logged into with the credentials you sent.

I was looking for a caching plugin. Noticed Quick Cache, but that one doesn’t cause trouble. Then in the drop-ins I noticed advanced-cache.php, which may be a file left from a previous cache plugin you tried. Try removing that one and see if you have the problem again over the next days.

Hi Eddie.

No, something seems to be wrong, the role should be set properly too.

Please enable logging and do a test checkout for 1 cent, try to reproduce the problem you’re having so we can see what it looks like in the logs. [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration[/hilite]

When you have the logs for a transaction with that problem, could you submit the site’s info? Let me know when you sent it. s2Member® » Private Contact Form

The 2nd button’s code seems okay, but the 3rd button’s code is not. The theme or another plugin seems to have altered it. You can test following the tips in this article. Knowledge Base » Common Troubleshooting Tips

I see you have Open Registration enabled, and the registration form looks quite customized. Doesn’t look like the default one. It is possible that what you used to customize it, is ignoring s2Member’s cookie, which is set after checkout to tell s2Member what access the new account should get on registration. Again, please follow the tips in the troubleshooting article for this, please.

If you don’t want have users register/login, this may help: Video » s2Member (Specific Posts/Pages).

Hi Jeremy.

Well, you could customize the s2Member Level role you’re selling, to have the capability that would let the user edit that, I guess.

http://wordpress.org/extend/plugins/user-role-editor/
Knowledge Base » Locking s2Member Roles/Capabilities

Ah, yes, I’ve seen some site owners do something like this in the past. You can customize it dynamically with some PHP in your shortcode. Knowledge Base » Using Variables In A Shortcode

Not trying to be contrary and I’m sorry for the snippy tone of my previous reply, I was a bit frustrated.

Oh, no problem, I know how that can be.

that may be true for s2Memebr itself in its current state but that is certainly not because of limitations in WordPress itself as far as I can see

I know it’s not impossible, but it does require a plugin/hack because the default behavior is not that, as far as I know.

I would think a powerful membership plugin like s2Member should have this built-in or maybe true a smaller plugin addon one could install on sub sites.
…
Just food for thought.

I’ll add this to the feature requests list to consider when we look again at the multisite support. Thanks for the feedback! :)

The pro-form seems fine. Llike I said in my previous reply, you’ll need to have the DPRP service enabled in your PayPal Pro account to sell that. That’s what PayPal is requiring you to do in that error message. Or do you have it and you still get that error?

I can’t seem to solve the issue from that the trouble-shoot unless updating the s2member plug-in worked.

Do you think that’s what could of been the issue?

I’m not sure I understand. So the problem is fixed or you’re still having it?

If still having it, I can take a look at your site. Could you submit the login info? Please include ClickBank’s so I can review the configuration over there. s2Member® » Private Contact Form

I don’t think it’s a bug. Maybe at that point in the script, the user’s account had not been changed to that role yet and thus the condition isn’t true?

Have you tried checking what the user’s role is at that point? Maybe with [hilite mono]S2MEMBER_CURRENT_USER_ACCESS_LEVEL[/hilite]. [hilite path]Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants[/hilite]

when it says “punish for 15min”, this just means that they will not be able to log in for 15min. But after the 15 min, does their IP counter reset?

Here’s a detailed explanation Jason gave me:

Jason Caldwell said:

No, it just ends the punishment period; that’s all.
The IPs only reset every 30 days by default.

If you reach the max IPs and a punishment period kicks in; it locks everyone out. If someone else comes in with an existing IP on file, they will get in. If they come in with yet another new IP, it pushes the limit again (because the counter does not reset); and the punishment period kicks in again.

Look at it like this:

Username: johndoe22 (this is what we are guarding)
Max IPs for this Username are set to 5 unique IPs every 30 days.

IP 123.456.789.1 logs in under this Username.
IP 123.456.789.2 logs in under this Username.
IP 123.456.789.3 logs in under this Username.
IP 123.456.789.4 logs in under this Username.
IP 123.456.789.5 logs in under this Username.

Everything is OK so far.

IP 123.456.789.6 logs in under this Username.
~ Now EVERYONE is locked out of the account (this new IP and all previous IPs too).

If the punishment period is 1 hour, after one hour if one of the first five IPs attempts to access; they will get in. If someone new attempts to access this Username; they are ALL locked out for another 1 hour period.

Another important point to make, is that it’s not actually every 30 days (collectively). It’s 30 days per IP. So if IP 123.456.789.1 accesses the site on March 1st, they drop off the list (i.e. they are reset) 30 days later. This works independently for each IP address that is tracked.

In addition, there is a throttle switch connected to this behavior; which will automatically increase or decrease the 30 day drop-off rate; based on the number of abuses we track; or a lack of abuses. There is a behavioral pattern in the code. When we say 30 days; that’s really a baseline which s2Member® throttles from. It is designed to be VERY difficult to circumvent.

Ah, I know what you mean. This happened to me too. Normally the link is removed from the login page when I have Open Registrations disabled, but once I had the link be there although registrations were closed. It took me a while before I realized that I had a cookie in the browser from an old signup test, which was letting me register and thus the link was there.

By the way, here’s what Jason told me a moment ago:

We could ask him to place this in his /wp-config.php file as a quick test; and then remove it after the test is done.

[hilite pre_code]
$_SERVER['HTTP_RANGE'] = NULL;
[/hilite]

http://answers.microsoft.com/en-us/ie/forum/ie8-windows_other/ie8-http-range-header-internet-explorer-8-sends/bab46da5-587a-4c09-99fe-4c33fa4f6c18?msgId=58b5bb40-f86c-49e6-9788-d73375a52236

I will investigate this further tomorrow.

Could you please try that?

Sorry about the delay.

Okay, I found your email and couldn’t login to the admin area, but was able to login to the FTP. I got the log files and searched for the entry you quoted above, but could not find it. What other transactions had this problem? I’ll look them up in the logs to see what may look wrong.

Have you asked PayPal about these failed transactions? After all it’s them processing the payment and failing, s2Member is not in control of that.

Now that I have the logs, I’m also asking Jason about this so he can review them. Could you submit the working login info for the admin area? Let me know when you sent it, please. Thanks.