Mike (Volunteer Moderator)

What would be a normal ratio of failed payments to new signups? We offer services to cab drivers and there is nothing about what we do that subject itself to anyone needing to supply fraudulent info.

I wonder if that relates to the problem of “Payment Skipped” message that I get at least 7 times a week from PayPal. Regular users who have made successful charges in the past (and do in the future) trigger these errors. Are you certain s2member is out of the equation regarding those situations?

The normal range would be very few (and perhaps none for several days at a time). That is, no failed payments, or just happens every once in awhile; i.e. NOT all the time.

There’s nothing that s2Member® can do about payment failures. However, I would be sure to contact PayPal about this also (that’s who’s processing the transactions), and just check with them to be sure there’s nothing wrong with your PayPal account configuration overall, which might be causing this inadvertently.

I myself, am not aware of anything that would cause this, other than a lack of funds or outright fraud.

Thank you for showing me the “real-time” feature I will utilize that. Is there something beyond “failed” that appears in the logs so I can know if it was declined, or wrong address or anything like that?

Yes, please keep tabs on this log file from your Dashboard.
See: Dashboard -› s2Member® -› Log Files (Debug) -› s2Member® Log Viewer
Keep an eye on this file: paypal-api.log or paypal-payflow-api.log.

Any updates on the Google Wallet integration??

The latest update is posted here, that’s all that I have at this time.
See: Knowledge Base » Google Checkout vs. Google Wallet

Please let us know if problems persist :-)

So sorry, I didn’t get a response back from the techs on this, but let me take a look and see if anyone ever came back and added any additional data to this request for support. One moment please.

:-) I should have said it’s not possible. However, I can’t really say that because you just never know. We don’t control PayPal of course, and they have their rules over there :-)

So I’ll say it like this. It MIGHT be possible, but good luck getting PayPal to actually do this for you). If you want to give it a shot, I would suggest writing to PayPal and explaining what you want to do (e.g. you need to have the IPN URLs updated across all members that joined up with Buttons). If they say no, at least you tried, and hopefully they’ll come around at some point and make this easier on folks.

What they usually say is that it’s up to you to build an IPN handler that can accept data from the old accounts and point it to the new ones. This is exactly the path you’re on here already, so it’s a good backup if they say no.

Very welcome. I’m sorry I can’t do more.
~ When you do figure this out, I will appreciate it if you can update this thread (if you think about it). That would be great and may help others also :-)

Thanks for the detailed follow-up TJ; we REALLY appreciate this. I’m glad we could help you out here, and I’ll be sure to relay this reply to Jason so that he will see it as well. If you are so inclined, we would LOVE to get a review from you at some point. Here’s the link. Just a couple lines will do fine :-)

and please let us know if you need any further assistance :-)

@Danny Kim I noticed that you’re running s2Member® Pro Forms. Do you have more than one account here at s2Member.com? The account you’ve written in on is listed as a Free Subscriber and not as a paying customer that owns a copy of s2Member® Pro. If you have a paid account, it is best to post under that account please.

Thanks for the follow-up :-)

The code to implement this custom modification would need to come from you, and it can go right into that same file (e.g. PHP tags are allowed in this file paypal-checkout-form.php when/if you need them).

The best I can do is provide you w/ a general outline below.

Getting a User’s array of custom fields.

$user_id = get_current_user_id();
$custom_fields = get_user_option('s2member_custom_fields', $user_id);

Addiing a new custom field to this array.

$custom_fields['unique_field_id'] = 'value';
// Ex: $custom_fields['teacher_search'] = esc_html($_POST['s2member_pro_paypal_registration']['custom_fields']['teacher_search']);

Updating custom fields after array modification.

update_user_option($user_id, 's2member_custom_fields', $custom_fields);

Putting it all together; it might look something like this.

$user_id = get_current_user_id();
$custom_fields = get_user_option('s2member_custom_fields', $user_id);
$custom_fields['teacher_search'] = esc_html($_POST['s2member_pro_paypal_registration']['custom_fields']['teacher_search']);
update_user_option($user_id, 's2member_custom_fields', $custom_fields);

See also: Knowledge Base » Hacking s2Member® Via Hooks/Filters
See also: s2Member® » Codex (Source Code Docs)

I’m sorry, there is nothing jumping right out at me on this. So far we’ve been unable to reproduce this on our side of things. However, one thing that is worth checking, is the version of JW Player that you’re using. You might want to just download and install the absolute latest copy of JW Player to rule out any bugs in the player JavaScript file.

You may also want to search the LongTail forums for a solution to this, because this really is not related specifically to s2Member® (from what I’ve seen thus far); it really looks like it’s a problem with JW Player on your end. For instance, here is a thread you may find helpful. I would look for others like this and see if you can track it down.

Thanks Craig! :-)

Some things that may help you.

1. Locking down the /wp-login.php file (not common, but you requested this).

Please create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
(NOTE: these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins)
(See also: http://www.s2member.com/kb/hacking-s2member/)

<?php
add_action('login_form_register', 'my_wp_login_redirect');
function my_wp_login_redirect()
	{
		wp_redirect(home_url('/register/')); exit;
		// Redirects to BuddyPress registration form instead :-)
	}

2. If you have custom fields that you’d like to integrate into your BuddyPress regisration form, s2Member® can help with this if you like. See: Dashboard -› s2Member® -› General Options -› Registration/Profile Fields

3. Understanding the difference between “Registration” and “Checkout” where s2Member® is concerned.

While it is absolutely OK to use your BuddyPress registration form with s2Member® installed; this does NOT facilitate checkout and payment processing. This is what s2Member® Pro Forms are there for.

Thus, if you want to charge a customer, you will want to use s2Member® Pro Forms for this; and perhaps redirect these members back to their BuddyPress profile after checkout is completed.

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Membership Level # Forms
See also: Dashboard -› s2Member® -› PayPal® Pro Forms -› Custom Return URLs Upon Success
See also: Knowledge Base » s2Member® Pro-Forms

Thanks David! :-) I’ll pass that along. Appreciate the feedback.

Yes, that’s what I would start looking at because your code is rock solid there. Something is happening after this code, and it’s probably tricking you into thinking there is something wrong with that code snippet. It looks good :-) It’s most likely something else that comes after this.

If the CAPTCHA is not enough, you could add a registration field that asks the user a question also; as a second line of defense. Please see: Dashboard -› s2Member® -› General Options -› Registration/Profile Fields

Very welcome! :-) If you have a moment, we appreciate ratings @ WordPress :-)