Custom Fields During Registration

Does s2member currently have the functionality to require custom fields during the initial registration process?

It seems the JS error validation is only used on custom fields during profile modification of an already registered user. Whereas the registration form doesn’t check for custom fields designated as “Required”.

If this is currently not possible, is it being considered for a future update?

Hi there. Thanks for your inquiry.

Interesting. What you’ve described is already built-in. Any Custom Registration/Profile Fields that you configure as “required”, should be validated by s2Member during the initial registration.

It’s possible that you have a JavaScript error being introduced somewhere else on your site, which might be affecting s2Member’s ability to validate this input. Have you taken a look at your site in Firebug to check this? If not, please post a URL to your checkout form so we can have a look :-)

Since you mentioned that the behavior I was looking for was already there, I went back and took a closer look at what was happening. The script was throwing an exception on the ‘first’ method call, stating it didn’t exist. Some research led me to find out that ‘first’ wasn’t added to jQuery until 1.4, which then led me to find out that the previous developer had deregistered the jQuery library that comes with WP and loaded up ver. 1.3.2 as a part of the Google Analytics implementation.

So I removed that all is well again. I haven’t checked to see if running 1.7.1 is going to impact anything else, but if it does I can always register a lower version.

Are there any known issues running jQuery v1.7.1 with s2Member?

So sorry for abandoning you in this thread.
~ It was not intentional. We had some issues during site
launch and some tickets were buried by mistake. The issue has now been corrected.

Are there any known issues running jQuery v1.7.1 with s2Member?

None that I’m aware of, no.
s2Member has been fully tested in WordPress v3.3.1, and it ships with jQuery v1.7.1.

Thanks for the reply. I haven’t seen any issues since going to v1.7.1, so thanks for the help!

Closing this topic, thank you VERY much for the follow-up :-)