Custom Registration Fields not being saved.

Since we upgraded the other day to S2 Pro & started to use Paypal Pro Forms for registration none of our custom fields are not being saved, they all appear as the same value.

We have various text fields for a customers address & a space for them to tell us a bit out about them, and they all appear in the database as “1”

I’ve just upgraded to the latest version of S2 & S2 Pro & the problem is still happening, although the user I tested with had all his data set to “B” instead.

The user’s Paypal payment info is as expected though, as is their username & email address, it’s only the custom fields that are effected.

Thank you for reporting this important issue.

Do you have logging enabled? See: Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration

If you do not, please turn this on temporarily and run a test transaction. Also, could you check to see if the custom fields work with Free Registration Pro Forms?

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms

After you get log files, please send us a Dashboard Login so we can take a look at them. You can do that here:

s2Member® » Private Contact Form

Does the dashboard user need to be a full admin?

Does the dashboard user need to be a full admin?

Yes we need admin privileges to see your log files.

Thanks, I sent you the login details you required on Sunday, hopefully we can get a quick resolution to this.

Details Received.

I’m taking a look now.

The logs you have in here most recently are showing May 3rd. Currently you have logging disabled. Can you please enable logging, and 2 test transactions, one with all of your plugins running, and one with plugins disabled.

I did test your free registration form and that works just fine, so my guess is that this is a problem with either the connection from your site to PayPal, or from PayPal to your server that’s messing up your custom fields up.

Stuart, I took a look at your users list and didn’t find one that has the custom profile fields with those values you mentioned. The custom profile field definitions in the General Options looked okay too.

Do you still have this problem? Could you tell us the usernames of those who have this problem in their profiles? Or a way to reproduce the problem you’re reporting? Thanks!

If you have a look in the reg-handler log, the log entry at “2012-05-03 14:21:20” has the problem I’ve described.

I have re-enabled logging, but it is worth noting that I have currently reverted back to the default S2 signup process so any new members that sign up following our “Join” link at the moment will be ok, it’s only members that sign up using the Pro forms that have this problem. We use the names & addresses to post membership packs so I can’t leave the broken signup live

Our Pro forms are available here for adults & here for juniors, we don’t use the pro forms for free subscriptions but I have created one for this problem and captured the logs for user sg_s2test, who’s data is all blank when you view it in admin.

Thanks.

I did a test free registration and saw that all the custom profile fields were populated with “s”. I don’t know what’s causing this.

I did the server scanner test and didn’t see any errors with the s2Member directories, but it does mention an error with cURL. I don’t know if that’d cause the above problem, but you should still fix this. Please see: yoursite.com/s2-server-scanner.php

What I’d suggest next is to do the plugins/theme conflict tests. Knowledge Base » Common Troubleshooting Tips

I have narrowed down the problem to the theme we are using, I disabled ALL plugins other than S2 and still had the same problem, so I reset the theme to the default WordPress theme & registration worked as expected.

However the theme we use is InFocus, and seeing as it’s the theme you recommend in conjunction with S2, I would have expected it to work?

I have narrowed down the problem to the theme we are using, I disabled ALL plugins other than S2 and still had the same problem, so I reset the theme to the default WordPress theme & registration worked as expected.

However the theme we use is InFocus, and seeing as it’s the theme you recommend in conjunction with S2, I would have expected it to work?

That’s interesting. Would you mind putting surrounding your shortcode with [raw] tags and see if that helps?

They already have [raw] tags

That’s odd, we’re not having that problem with inFocus. Are you using a clean copy of the theme or has it been customized? Did you ask the inFocus guys about this problem the theme is causing?

The only modifications we have made are to some of the CSS, and that’s done by using the “Skins” tab on the Infocus config.

I will ask on the Infocus forum too, but this feels to me like it’s an issue with the validation that gets done on the form before it’s submitted, looking at the logs they are already corrupt in there.

Could it be related to the javascript validation that happens before the form is submitted?

Sorry for the delay in response.

Could it be related to the javascript validation that happens before the form is submitted?

This is likely the problem. s2Member is receiving the information from PayPal corrupted, so something is happening before the information is sent to s2Member. We are using inFocus here at s2Member aren’t having this issue so I’m unsure how this could be causing the issue.

Could you provide a link to a page where one of your Pro Forms is, and I’ll take a look to see if you have any JavaScript errors causing this.

Hi Bruce,

All our links are in this post: http://www.s2member.com/forums/topic/custom-registration-fields-not-being-saved/#post-49676 but the free registration I’ve created for testing this issue is here:

http://www.roverstrust.com/test-free-subscriber-page/

Is there any way to make S2 use uncompressed Javascript so I can trace it myself to see what’s going on too?

Thanks for the information. I’m taking a look now.

Is there any way to make S2 use uncompressed Javascript so I can trace it myself to see what’s going on too?

If you go to /s2member-pro/includes/separates/gateways/paypal/, there is a paypal.js file, and a paypal-min.js file. If you change the name of paypal-min.js to something different, and paypal.js to paypal-min.js, s2Member will then use the uncompressed version of this file. This is true with all of s2Member’s JavaScript files.

Any progress Bruce?

Sorry for the delay in response.

I took a look and I’m not seeing the issue here.

Can you please check to see if you can recreate this behavior creating Users through the registration form at /wp-login.php?action=register, and through your Dashboard, just so we can make sure that this is something non server-side? If that’s okay can we have permissions to run test signups to see if we can find the problem?

As I said originally, the problem only exists when we use the Paypal Pro forms to register users & your colleague Christian can also recreate the problem http://www.s2member.com/forums/topic/custom-registration-fields-not-being-saved/#post-49742

You can see the problem by using this for: http://www.roverstrust.com/test-free-subscriber-page/ when you fill in all the details & get the captcha at the end wrong, all the values are 1, or in Christian’s case “s”. This is how the data gets written to the database if the captcha is filled in correctly.

This thread has been open for a month now & I don’t feel like we’ve made any progress at all, if we’re not going to be able to find the cause of the problem then can I please get a refund & I’ll use a different membership plugin, that would be a shame if I had to do that & migrate all the data but the 2-step registration process is causing us real problems at the moment with paying customers either not getting, or not understanding the final email they need to follow to complete signup.

Thanks for the information.

I just tested this and did some logging on your POST variables that are passed to s2Member when the form is submitted. The variable that should hold your custom fields is completely empty. I looked at the source code for your page and s2Member is generating the HTML input tags correctly, and nothing there is corrupted by the theme. I’m not sure exactly what’s going on yet but we are getting closer.

I understand this is frustrating, but at the current time we are attempting to figure out what exactly is causing this error. You’re saying that inFocus is causing this error yet in our tests we are unable to reproduce this error with inFocus. So I’m assuming that the error is to do with inFocus + something that’s on your site. I’m going to continue to try to diagnose the issue here.

Hi Bruce,

Did you manage to find anything?

If the field names are correct but by the time the POST hits the server they are empty that would suggest something to do with the client side validation of the fields?

We use the same custom fields on the non-Pro signup forms and they are submitted OK there, what are the differences between those two forms? Is the validation different?

Any update Bruce?

So sorry for the delay in response! My list of threads buried this and Cristian just notified me of this. I did take a look at your installation again, but I’m unable to find the issue here. I’m going to ask Jason about what might be causing this.

We use the same custom fields on the non-Pro signup forms and they are submitted OK there, what are the differences between those two forms? Is the validation different?

Custom fields through buttons don’t go through the payment gateway, and are processed by a different file in s2Member. The issue here isn’t actually with the validation, it’s that s2Member isn’t actually getting any information from the $_POST variables except what you’re seeing. I’m not sure what would cause this at all.