Custom registration field not got default val

Hi – this is a weird one – got me baffled

I have created a custom profile field (text field) that is set to hidden during registration and after in profile management

I have assigned a default value to the field (text string)

I have setup and tested my regsitration process – via paypay buttons and back to the site to finish regsitration – all working

except, the new users account, whilst it has the hidden field in the profile (I see this by looking at admin to user profiles) – the hidden field has no default value assigned to it (its blank)

this is breaking some other site functionality that depends on the value of this hidden field

can anyone help please ?

Si

bump

Hi Simon.

That’s odd. I just tested this in my installation and it worked fine. The field is hidden on registration and profile, and when I check for it as the admin it’s there with the default value.

Are you using the default registration page or a pro-form?

Maybe there’s something in your installation causing it to not work? You can try as a test to use the default theme, or deactiving other plugins and trying after each if the problem continues.

Let me know how it goes. :)

using a paypal button to pay for registration, this redirects back to out of the box s2 registration

after it completes the hidden field is in users profile but has no value

no other plugins are involved in this process

Joe

So it’s a clean WP installation, with no other plugins installed and active? And you’re using the default theme?

A clean installation doesn’t have the problem you mentioned, so there must be something else interfering in yours. Deactivating plugins and using the default theme, helps remove conflicts and spot where they may be.

this is my s2member

120309

Just to re-iterate, in my version of s2member pro, the hidden at registration, custom field, assigned a default value – does not work as it should.

Its not until I show the custom field that that the value is assigned to it during regsitration.

To work around the issue – I have given it a friendly name, made it a pre-checked checkbox and made it required (so the user cannot uncheck it when filling out reg form)

It now retains the correct value (in this case ‘1’) – which I cab use elsewhere

Joe

Glad you found a way that worked for you. It’s odd that the one you tried first didn’t, though, even if it’s a slightly older version of s2Member. We haven’t had reports of it not working, or made any changes to that code since that release that I know of.

Anyway, with that workaround you now have the functionality you need. Thanks for the update! :)