latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

About: Ryan Collins

Sorry, I've not written a description yet. I'll get to it soon!


My Latest Replies (From Various Topics)

Viewing 15 replies - 1 through 15 (of 15 total)
Author Replies
Author Replies
Posted: Saturday Jul 20th, 2013 at 10:28 am #53733

Thanks Cristian.

I am using the latest release of s2member.

Today I changed the “allow infinite IPs” back to only allowing 20 different IPs. I tested it by logging in as the above mentioned user, and this time was able to login.

So to make a long story short the issue is resolved for now. I appreciate your efforts looking into this and if the problem creeps up again I will let you guys know.

Thank you!

Posted: Tuesday Jul 16th, 2013 at 6:34 pm #53531

I based my conclusion that he was not over the Max IPs on the message from s2member within his user account.

In my WordPress dashboard: All Users–Edit User–Scroll Down–“*Note* this User is NOT currently banned by any of your IP Restrictions.”

I’ve attached a screen shot of the option.

Every other time when someone receives a 503 Error message, s2member lets me know that they are over their max allowable IPs by telling me that they are over their limit. In this case, I did not receive that particular message and instead s2member told me he was not over his limit.

I hope that helps clarify things. If you have any ideas I’m all ears. Thank you!

Posted: Thursday Jul 11th, 2013 at 4:49 pm #53317

Thanks! Looks like I have some diagnostic work to do.

Take care,

Ryan

Posted: Wednesday May 15th, 2013 at 8:04 pm #50039

*This issue has been solved*

Just an update here for anyone else dealing with this issue.

It is not an s2member issue at all, it’s a buyers’ issue – according to PayPal support.

What happened in my case was the buyer purchased a membership, and s2member created their account as it normally would.

However, I don’t know if PayPal delayed the initial charge, but a few hours later that transaction failed. According to the PayPal support team, the buyer’s credit card or PayPal account failed and the new member was demoted.

Still not sure why the account was approved in the first place, if the initial transaction to setup their membership failed.

I suppose I’ll go bug PayPal again. lol

Thanks,

Ryan

Posted: Tuesday May 14th, 2013 at 12:28 pm #49959

Awesome Bruce – thanks so much for looking into this issue for me. Really big help.

I’ve dealt with W3 Cache issues in the past, so I should be able to handle this one from here.

Just diagnosing this is as a W3 issue is the help I needed.

Thanks!

Posted: Saturday May 11th, 2013 at 5:06 pm #49760

Hey guys,

Just a friendly “bump” here to see if there has been any progress looking into this issue.

I did submit a private contact form, so please let me know if you received it at your convenience.

The website houseflippingschool.com is now live, so there is no need to login via a web proxy as described in the private contact form message.

Thank you! Would love to get this one figured out – I am stumped!

Take care,

Ryan

Posted: Wednesday May 1st, 2013 at 11:27 am #48925

Hi Cristian,

Thanks for the prompt response, much appreciated.

I have been testing the signup process by creating new signups. So no, they are not existing users upgrading their account.

I went ahead and submitted a private contact form. Thanks for offering to look into this further – I’m stumped!

The website is currently in a secure environment, which is accessible via a proxy server. I have attached instructions for accessing the site, via a word document that I included with the private contact form.

Of course keep me posted with anything you need from me.

Thank you!

Posted: Wednesday May 1st, 2013 at 9:53 am #48906

Quick update:

I had my hosting company disable APC on my server, however the problem still persists.

Thanks for any insight and take care,

Ryan

Posted: Tuesday Mar 19th, 2013 at 8:35 am #45161

No worries on the delay Bruce. Whenever possible I prefer to figure stuff out on my own anyways. Good for my self confidence.

Have a great day!

Posted: Saturday Mar 16th, 2013 at 3:49 pm #44940

After trying a lot of things I have figured this one out. Looks like you need to be cognizant of your W3 Cache settings if you plan on using that plugin with s2member.

If you encounter the same issue as I, and you are using W3, try disabling “Database Caching” – that solved the problem for me.

A better alternative would probably be to just use Quick Cache instead of W3.

Thanks,

Ryan

Posted: Friday Mar 15th, 2013 at 1:30 pm #44727

Any ideas on this one?

I had another person sign up as a Level 1 Member last night, but unfortunately granted only subscriber access.

I’ll keep working on a fix on my own and will be sure to post the fix if I find one. Again any insight is much appreciated.

Take care,

Ryan

Posted: Tuesday Jan 15th, 2013 at 8:36 am #37571

Awesome, thank you Bruce for your prompt response-much appreciated!

Take care,

Ryan

Posted: Tuesday Jan 1st, 2013 at 9:45 pm #35946

Gotcha. No worries, thanks Eduan.

Take care,

Ryan

Posted: Tuesday Jan 1st, 2013 at 7:19 pm #35940

Thanks Eduan. I really appreciate it.

Quick question – Do you know of a wordpress squeeze page plugin that works well alongside s2member?

Thanks!

Ryan

Posted: Saturday Dec 29th, 2012 at 12:02 am #35685

Figured it out.

The Insta Builder plugin was conflicting. I suppose I should contact Insta Builder?

Anyone know of a fix?

Thanks!!

Ryan

Viewing 15 replies - 1 through 15 (of 15 total)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.