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.

Brett Adcock


My Latest Replies (From Various Topics)

Viewing 25 replies - 1 through 25 (of 32 total)
Author Replies
Author Replies
Posted: Monday Mar 25th, 2013 at 10:07 pm #45692

Thanks Eduan,
You were right. I did some more research and it seems that the WP core actually creates those rows in wp_usermeta. If anyone is interested, it’s easy to prevent: http://stackoverflow.com/questions/15582325/how-to-optimize-wordpress-wp-usermeta-table

Posted: Thursday Jan 24th, 2013 at 8:34 am #39402

Thanks for your help. I was able to resolve this by adjusting some settings of stop spammer registration plugin…
I turned off several features but I believe the one that did it was the option to block connections with incomplete headers. Now it works again.

Posted: Tuesday Jan 22nd, 2013 at 5:25 pm #39009

Thanks!

The installation of that plugin is probably around the time this problem started. Disabling it is a possible solution, but it is highly effective in preventing SPAM in conjunction with the QA plugin offered by WPMU. (We were getting pounded by SPAM before we installed it.)

I’d love to keep it active if possible. Can you tell me anything more about where you’re seeing the plugin blocking s2Member functionality? Maybe I will be able to make some adjustments.

Posted: Sunday Jan 20th, 2013 at 10:41 am #38412

Hi again Jason,

I have the new http logs following a new specific post/page purchase. I’m not exactly sure what to look for, and I don’t think it’s safe to post them here, but I can point to line # 4181 which appears to be a purchase notification. Are you able use the credentials provided earlier to have a look?

Also, I see the following error quite often in my general server log:

[20-Jan-2013 04:55:57] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/streetof/public_html/wp-content/plugins/s2member/includes/classes/files-in.inc.php(387) : eval()’d code:1) in /home/streetof/public_html/wp-includes/pluggable.php on line 876

  • This reply was modified 3 years, 11 months ago by  Brett Adcock.
Posted: Saturday Jan 19th, 2013 at 8:07 pm #38353

Hi Jason,
I installed the mu-plugin as instructed in the link. I’ll report back with whatever findings result from that. In the mean time, are you able to tell me any more about the failing http connections? How do you know they’re happening and is there more details that I could use to investigate it further.
-e

Posted: Thursday Jan 17th, 2013 at 7:04 pm #37972

Thanks Jason, I just submitted the requested credentials.

Posted: Tuesday Oct 2nd, 2012 at 3:02 pm #27240

And another update. I was wrong about what I said before: the redirect parameter WILL override the s2member redirect!

WONT WORK-> wp_loginout( $redirect_url );
WILL WORK – wp_loginout();

Posted: Tuesday Oct 2nd, 2012 at 2:22 pm #27236

Just a quick follow-up. After extensive trial-and-error, it seems like the s2Member login-redirection setting isn’t working at all, or at least very infrequently. No matter what setting I use, I just end up on the same page from which I started. I’m generating the login/out link with: wp_loginout(); Even when I overtly specify a target redirection as a parameter, I STILL end up on the same page. It’s very confusing.

Posted: Friday Aug 24th, 2012 at 4:15 pm #22997

Thanks for the response. I’m still debugging this but I don’t think it is a result of a plugin conflict after all. I think the user has no first_name or last_name property at the time when that hook fires.

Posted: Wednesday Jul 25th, 2012 at 9:05 am #20196

Or were transactions happening normally and the only thing off were emails?

This is exactly what was happening. The users were able to access the purchased pages/posts normally too. The only missing piece was the confirmation email (both to the client and the notification to the admin).

Did you see the other two logs included above? Were those instructive at all?

Posted: Tuesday Jul 24th, 2012 at 9:43 am #20080

Hi Christián,
Thanks for getting back to me…

As for our specific post/page email problem…
We HAVE suddenly started receiving emails. Which is WEIRD because they weren’t happening for at least a month, and I didn’t do anything. The emails started working properly RIGHT after I submitted the private contact details, which is why I assumed that Raam or you had done something to fix it. Since you didn’t, I’m even MORE confused about what’s going on.

I do still see one of those error messages at the bottom of the log file. It’s hard to know what it’s connected to because the problem/error entries don’t include what time they happen. So it’s hard to go back and figure out what should have happened at that time.

=e

Posted: Sunday Jul 22nd, 2012 at 8:47 pm #19954

I haven’t heard from you guys in a few days, after submitting the info via the private contact… but the email notifications JUST started working. Coincidence? I doubt it. Can you catch me up on what’s going on?

Posted: Wednesday Jul 18th, 2012 at 2:35 pm #19658

Just to keep you up to date, I’ve checked in google apps (who hosts my site’s mail), and I also ran a test using my host’s server (instead of gmail) by disabling the SMTP plugin. In both cases, the email is NOT getting sent. I see this again in the ipn log:

PHP v5.2.17 :: WordPress® v3.4.1 :: s2Member® v120703 :: s2Member® Pro v120703
Memory 34.20 MB :: Real Memory 34.50 MB :: Peak Memory 34.23 MB :: Real Peak Memory 34.50 MB
www.streetofwalls.com/?s2member_paypal_notify=1&s2member_paypal_proxy=paypal&s2member_paypal_proxy_use=pro-emails&s2member_paypal_proxy_verification=xxxxxxxxxxxxxxxxxxx98c7d&s2member_paypal_proxy_return_url=
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
array (
  's2member_log' => 
  array (
    0 => 'Unable to verify $_POST vars. This is most likely related to an invalid configuration of s2Member, or a problem with server compatibility.',
    1 => 'If you\'re absolutely SURE that your configuration is valid, you may want to run some tests on your server, just to be sure $_POST variables are populated, and that your server is able to connect/communicate with your Payment Gateway over an HTTPS connection.',
    2 => 's2Member uses the `WP_Http` class for remote connections; which will try to use `cURL` first, and then fall back on the `FOPEN` method when `cURL` is not available. On a Windows® server, you may have to disable your `cURL` extension; and instead, set `allow_url_fopen = yes` in your php.ini file. The `cURL` extension (usually) does NOT support SSL connections on a Windows® server.',
    3 => 'Please see this thread: `http://www.s2member.com/forums/topic/ideal-server-configuration-for-s2member/` for details regarding the ideal server configuration for s2Member.',
    4 => 'array (
  \'s2member_paypal_notify\' => \'1\',
  \'s2member_paypal_proxy\' => \'paypal\',
  \'s2member_paypal_proxy_use\' => \'pro-emails\',
  \'s2member_paypal_proxy_verification\' => \'xxxxxxxxxxxxxxxxxx698c7d\',
  \'s2member_paypal_proxy_return_url\' => \'\',
)',
  ),
  's2member_paypal_proxy' => 'paypal',
  's2member_paypal_proxy_use' => 'pro-emails',
  's2member_paypal_proxy_verification' => 'xxxxxxxxxxxxxxxxxxx698c7d',
)

It seems pretty clear that the break-down is occurring between s2member and PayPal. Can you confirm this much? Is this a known bug? I’m not sure what, if any, additional info I can provide to move this along, but I’m getting a little bit desperate because my site is selling digital content to non-members. Without this email, the customers can’t access their purchase. Even if you don’t have a solution/fix yet, I would really appreciate any insight you can provide on this situation.

Posted: Wednesday Jul 18th, 2012 at 10:17 am #19641

I raised the PHP memory limit to 64MB, just to be safe. Although it’s still showing 32MB in the server check script, I know it’s at 64MB because I have a phpinfo() in the same directory, which shows the limit to be 64MB.

Posted: Wednesday Jul 18th, 2012 at 9:35 am #19639

I just noticed that the second and third pages were clipped off in my previous post. They were all “[PASS]”. I’ll look into the two notices at the top, but they don’t seem relevant to my current issue.

Do you have any other suggestions for why this might be happening?

Posted: Wednesday Jul 18th, 2012 at 9:18 am #19635

Hi Raam,

I have followed the email troubleshooting tutorial and installed the Email Log plugin. It shows other emails being send (like new registrations) but NOT specific post/page emails.

I ran the php script that you provided and all tests were “passed”.

Posted: Tuesday Jul 17th, 2012 at 10:17 am #19519

It’s the code that’s currently live on our site. It seems to work fine, with the exception of the confirmation email (with the access link) not getting sent.

Did you have a look at the logs? I’m really hoping you or Christián can take a look because I suspect there’s useful information there, but I’m not entirely sure what to look for.

Thanks!

Posted: Monday Jul 16th, 2012 at 9:44 am #19358

This just in!
This post describes the exact same problem I’m having:
http://www.s2member.com/forums/topic/specific-post-page-email-link-not-being-sent/

Although (unlike the OP) I don’t have line breaks and bold-faced type in my shortcode, I am generating my shortcodes programmatically with a template, so it’s possible that the s2member shortcode has evolved and the shortcode in my template needs to be updated.

The OP sounded like a dickhead (why gripe at the support team that’s helping you??), and never responded to confirm the solution you and Jason offered, but it sounded promising.

Here’s the line that builds the shortcode in my template files:
$shortcode = ‘[s2Member-Pro-PayPal-Form sp="1" ids="'.$guide_ID.'" exp="'.$time.'" desc="Purchase '.get_the_title($guide_ID).':" ps="paypal" lc="" cc="USD" dg="0" ns="1"'.
' custom="'.$domain.'|'.$current_user_id.'" '.
'ra="'.$price.'" accept="paypal,visa,mastercard,amex,discover,maestro,solo" accept_via_paypal="paypal" coupon="" accept_coupons="1" default_country_code="" captcha="0" /]‘;

Do you see anything problematic?

Posted: Monday Jul 16th, 2012 at 9:22 am #19357

Here’s the ipn log after my most recent test, just in case it’s useful:

PHP v5.2.17 :: WordPress® v3.4.1 :: s2Member® v120703 :: s2Member® Pro v120703
Memory 34.20 MB :: Real Memory 34.50 MB :: Peak Memory 34.23 MB :: Real Peak Memory 34.50 MB
www.streetofwalls.com/?s2member_paypal_notify=1&s2member_paypal_proxy=paypal&s2member_paypal_proxy_use=pro-emails&s2member_paypal_proxy_verification=xxxxxxxxxxxxxxxxxxxxxxxd&s2member_paypal_proxy_return_url=
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
array (
  's2member_log' => 
  array (
    0 => 'Unable to verify $_POST vars. This is most likely related to an invalid configuration of s2Member, or a problem with server compatibility.',
    1 => 'If you\'re absolutely SURE that your configuration is valid, you may want to run some tests on your server, just to be sure $_POST variables are populated, and that your server is able to connect/communicate with your Payment Gateway over an HTTPS connection.',
    2 => 's2Member uses the `WP_Http` class for remote connections; which will try to use `cURL` first, and then fall back on the `FOPEN` method when `cURL` is not available. On a Windows® server, you may have to disable your `cURL` extension; and instead, set `allow_url_fopen = yes` in your php.ini file. The `cURL` extension (usually) does NOT support SSL connections on a Windows® server.',
    3 => 'Please see this thread: `http://www.s2member.com/forums/topic/ideal-server-configuration-for-s2member/` for details regarding the ideal server configuration for s2Member.',
    4 => 'array (
  \'s2member_paypal_notify\' => \'1\',
  \'s2member_paypal_proxy\' => \'paypal\',
  \'s2member_paypal_proxy_use\' => \'pro-emails\',
  \'s2member_paypal_proxy_verification\' => \'xxxxxxxxxxxxxxxxxxxxx8c7d\',
  \'s2member_paypal_proxy_return_url\' => \'\',
)',
  ),
  's2member_paypal_proxy' => 'paypal',
  's2member_paypal_proxy_use' => 'pro-emails',
  's2member_paypal_proxy_verification' => 'xxxxxxxxxxxxxxxxxxxxx698c7d',
)

One curious thing is that the previous log entry DOESN’T show these warnings, but the email logs don’t show a specific post/page email getting sent to any users whatsoever. Only new user registration emails.

Posted: Monday Jul 16th, 2012 at 9:10 am #19356

For what it’s worth, my (uninformed) impression of the logs suggest that there’s a problem between s2Member and the PayPal API. If this is true, it might explain why this problem suddenly started happening without any changes in our site setup… I noticed that PayPal’s site changed a few weeks back. I wonder if this also coincided with changes in their API.

Has anyone else reported this problem? If my theory is correct, I’d image this problem to be pretty wide-spread, and not just isolated to my installation.

Posted: Monday Jul 16th, 2012 at 9:06 am #19355

Hi Christián,

I tried deactivating the New User Email plugin and the result was the same (no specific post/page email). I wonder, do the logs I posted tell us anything useful? I’m not entirely sure what to look for, but I thought this part might tell us something:

0 => 'No Return-Data. Customer must wait for Email Confirmation.',
1 => 'Redirecting Customer to the Home Page. Customer must wait for Email Confirmation.',
2 => 'Note. This can sometimes happen when/if you are offering a free Trial Period. There are times when a Payment Gateway will NOT supply s2Member with any data immediately after checkout. When/if this happens, s2Member must process the transaction via IPN only ( i.e. behind-the-scene ), and the Customer must wait for Email Confirmation in these cases.',

Also, the other post you asked about is not connected to this issue.

Thanks,
Emerson

Posted: Wednesday Jul 11th, 2012 at 12:00 pm #18933

Thanks for the advice. We found the problem and you were basically right. There was a bug in one of our custom functions that was breaking the system.

Posted: Wednesday May 23rd, 2012 at 12:39 pm #14340

I have one remaining issue: on my local development installation I’m not using SSL at all and I’m getting the same error message. I’m not using the custom fields and my paypal credentials are sandbox. Should this work normally?

Posted: Wednesday May 23rd, 2012 at 10:41 am #14332

UPDATE!
It worked once I removed the plugin!
Thanks!

Posted: Wednesday May 23rd, 2012 at 10:26 am #14329

Thanks Cristián,
I tried it using s2member_force_ssl instead of the plugin and it didn’t work. However, I want to make sure I did it correctly. Here’s how my set is (which doesn’t work):

My site url is http. I added s2member_force_ssl = true for the specific post/page that I’m selling. The checkout page appears with https (so far so good), but when I try to enter payment info into the form, it returns the error code listed above.

I also tried it by adding s2member_force_ssl = true to the checkout page (where the user is redirected to access the post they haven’t yet purchased. This didn’t work either.

Any more suggestions?
=e

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