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: Christian Bell

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

My Latest Replies (From Various Topics)

Viewing 16 replies - 1 through 16 (of 16 total)
Author Replies
Author Replies
Posted: Thursday Jun 13th, 2013 at 8:52 am #51885

It’s now seeming like it might be Adrotate that’s causing the issue.
I thought I had deactivated it too but maybe not.
Sorry for bugging you guys.

Posted: Thursday Jun 13th, 2013 at 7:55 am #51884

My hosting guys sorted that. Server check now comes up perfect.

Doesn’t seem to have made a difference though…

Posted: Thursday Jun 13th, 2013 at 7:33 am #51880

Tried switching themes and going through all the plugins. No difference.

The server check tool did throw up this error:
[ERROR] cURL Extension / Or fopen() URL
One or more HTTP connection tests failed against localhost.
Cannot connect to self over HTTP — possible DNS resolution issue.

I’m getting my hosting guys to look into it. Would that be likely to be the cause?

Posted: Tuesday Jun 4th, 2013 at 8:51 am #51317

Just been looking into how to implement this.
Do you know what files were changed for this update? Where should I be looking?

Any help much appreciated.


Posted: Friday May 24th, 2013 at 8:31 am #50551

I was afraid that might be the case…
Guess I’ll have to come up with a workaround.

Multisites are so much more trouble than they’re worth…

Posted: Monday May 20th, 2013 at 6:25 am #50217

The users are only on one site of the network and always have been.

The problem is that the login used to work on all the sites but now seems to be site specific.

Posted: Friday Apr 5th, 2013 at 12:19 pm #46714

I just did a test and it seemed to work for me too. Strange. Maybe it just needed time to settle. I’ve tentatively put the forms back on the site. I’ll let you know if they act up again.

Posted: Wednesday Mar 27th, 2013 at 10:30 am #45873

I just sent you the message. Realised I forgot to add the link to the pro form page after I sent it.
The link is:

I was doing tests with the form on this page:

Posted: Tuesday Mar 26th, 2013 at 1:16 pm #45802

The shortcodes are being used on the same site as the one that manages the members. It’s just that site is not the main site of the multisite installation. I don’t need it to work across the sites as all the membership stuff is on the membership sub site.

I’ve disabled the other payment options on the pro form. Still no closer to resolving my issue though. As I said before I can fill in the form and complete the paypal checkout but when I do I just end up back on the signup page without any error messages. So it seems like something is going wrong on the return from paypal.

I just had a dig through the logs and can see that someone made a couple of failed attempts to sign up this morning.

Really hoping you can resolve this or I’m going to have to move the site back to a standalone installation… Which would be a massive pain.

Posted: Wednesday Mar 6th, 2013 at 5:49 am #43847

Sorry. Should have been more specific.

I need to migrate all s2member settings as well as all users.

Posted: Thursday Jan 24th, 2013 at 10:36 am #39411

Finished our move to a new server and now the Paypal forms are working fine.

Many thanks for all your help at any rate.

Posted: Tuesday Jan 22nd, 2013 at 7:14 am #38942

I’ve tried reinstalling the framework before and I don’t believe I’ve modified any of the core files.

I’m about to move our site to a new server so we’ll see if that changes anything. If not I’ll give the http logging routine a try.

I’ll keep you posted.

Posted: Wednesday Jan 16th, 2013 at 10:16 am #37725

I tried the server check tool and it mostly passes. Though it did come up with this:

[WARNING] Plugin Directory Checksum (s2member)
Although NOT required, s2Member® recommends that you reinstall the following plugin directory: /home/rghjbrw/public_html/premium/wp-content/plugins/s2member. The checksum for this plugin directory (cc4870a41a3ee6b46af5aed5e36af405), does NOT match up with the official release of this plugin (afc37ccab81c6d39df41e3f6c7737e5c).

I tried deactivating plugins and switching the theme over to twentytwelve, met with the same issue.

Just tried another transaction and this is what i’ve got from the log:

Log entries removed for security purposes. Your log entries contained sensitive information that should be XXXX’d out before posting in the future please. Or you can email us log entries privately. See: s2Member® » Private Contact Form

That’s from the paypal-api log. The other two files don’t seem to have updated for this transaction.

Posted: Monday Jan 7th, 2013 at 8:29 am #36451

The logs don’t have anything particularly insightful to say… This is what comes up for the failed transactions:

——– Output string/vars: ( Mon Jan 7, 2013 1:01:10 pm UTC ) ——–

array (
‘__error’ => ‘Error. Please contact Support for assistance.’,

I’ve attached a screenshot of the error message.

I’ve checked through the common troubleshooting tips. I don’t think it’s any theme or plugin conflicts as the trouble just started suddenly without any changes being made to the site.

It could be related to a security issue we had on our site about a month ago. Our hosting provider disabled our site as there were a couple of vulnerable scripts – since removed. Is there anything they might have changed on the server that could be causing this?

Posted: Thursday Jul 12th, 2012 at 12:07 pm #19046

I’ll give that a try.

Thanks a lot!

Posted: Wednesday Jul 11th, 2012 at 6:50 am #18906

I’ve done that. The problem is that I want to allow access to just a couple of pages. I need multiple membership options pages. Obviously one of them is made public by default but I can’t make the others public.
I’d really rather not have to restrict access to each of my sites pages individually when I only want to give access to 3 or 4 pages.

Viewing 16 replies - 1 through 16 (of 16 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.