Hi,

Some fields in my registration form are read-only for authenticated Users (e.g. accept Terms and conditions). I do have two read-only fields, a dropdown and a checkbox.

So, when a user makes some changes to his profile, and presses "Update registration", after the update the values of these read-only fields are null, although the values are still stored in the DNN Database (table UserProfile).

This is a big problem, because this two fields are required fields, so the user isn't able to update his profile once again.

Bug?

If i completly hide the fields for authenticated Users -> Next problem: depending on the dropdown value (that is now hidden) i display different additional fields. If the user now updates his profile these values aren't saved and aren't displayed anymore!

I don't know how i can handle this. The only way that works, is to display all fields and allow users to change all of them. But that is not what i want, so please help me!
 

Sorry, wrong Product, this is about Dynamic Registration.

 Hi Sabe,

I just moved your topic to Dynamic Registration Forums.

What Dynamic Registration version are you using (from Host, Module Definitions)?  Also, what DNN version are you on?

I assume the user will not be allowed to register if they don't check the 'Agree to terms,' right?  If that is the case, can you try to  default it to marked and then from Advanced Field Options, also choose 'Always Force Default Value even for Authenticated Users?'  Let me know how that works.  Thanks!

Candace

 

Hi,

thanks for moving!

I'm using DR 4.0.50 and DNN 5.4.1.

The problem with terms and conditions is solved, i made this invisible for authenticated users. My problem is the Dropdown. With the dropdown, unauthenticated Users can choose in which Role they want to register, and depending on this value (or role), role-based fields are displayed to the user. But, if this dropdown is invisible for authenticated users, the values of the role-based fields are not saved on update, and if i disable the dropdown, the value of the dropdown is "gone" on update(it is still stored in the database, but in the dropdown nothing is chosen) . But it is a required field, so the user won't be able to update his profile again. The only way it works, is to set the dropdown visible and enabled, but that is not what i need.
 

Hi Sabe,

Are you testing while logged in as a Host?  Can you tellme if the problem persists if you're logged in as a regular user with the right role?  Thanks!

Candace

Hi Candace,

no, i'm not logged in as host while testing. I am logged in with the different roles in my portal (which are available in the dropdown to choose).

sabe

Hi Sabe,

I believe this might be a bug if read only fields are getting saved as null... Basically that is what you are saying right? We will work to confirm this on our end and in the mean time if you can setup a demo / example on www.betasprings.com (login as host/dnnhost) and can duplicate it there we can usually get a patch/fix out quicker. That or create a support ticket and provide us with temporary edit rights to the module. If we can duplicate this as a bug we can probably help figure out a work around for you.

-Chad

 HI Chad,

no thats not exactly what i said. The value isn't saved as null, because the dnn core field value in the database is still there, but the dropdown "forgot" the value (I don't know how to say).

I have made an example:

 

http://www.betasprings.com/DynRegis...fault.aspx

 

On the bottom of the page you find my Test-Registration "Dynamic Registration - Read Only Test". When you look at the values of the drop down, you will see two values: one with an empty string and one with value "Test". With the empty string, i want to not preselect a value for the User, so he had to choose one by himself.

Now log in as

 

username: TestSabine2

 

password: Test.123

 

and go to my registration form. You are not able to change the dropdown value. Now click "Update", and go back to the registration form. You will see, that the value of Dropdown is set to the empty string value. If you are able to have a look at the dnn core field in the database, you will see, that it is still set to "test".

Hopefully you have a work around for me.

Thanks in advance
 

 

HI,

anyone had a look at my test registration? Would be really important for my site to set the dropdown as read only.

Please give me a feedback.

 

Thanks

sabe

Hi Sabe,

The dropdown field is generally not designed to be read only as it begs a response from the user.  Is there any particular reason why you want this field type to be read only?  We might look at other options to consider depending on what you're trying to achieve.

If you want users to see options as just information, how about using a Text/HTML field instead?  Thanks!

Candace

 

Hi Candace,

no, i can't make it a text or html field. as i post above, the dropdown gives the user the possibility to choose the role they wanted to register. And depending on the selected role, different other fields appear. But the user shouldn't be able to change the role, once they are logged in. So it needs to be read only, or it needs to dissapear completly. But both ways are not working (see my post on 5/14/2010 12:03:24 AM)

 

sabe

Aaaah,  I see.  Instead of the read-only, how about you set that field to Hide from Registered User Role in Advanced Field Option?  That way, the unauthenticated user will see the field and make the selections, but when they log in, they won't see the field anymore.  Let me know how that works for you.  Thanks!

Candace

Yes, i tried this before, as i already post. That is also not working! In this case, all values of the role-based (= dropdown value based) fields are lost on an update Registration.

But i wanted to give it another try and tested it 2 hours ago again. Now i do have the problem, that my dropdwon values aren't stored to the database anymore. No completion events are fired anymore. If i change the dropdown to a radio button list, everything works fine. I spent two hours to check, what causes this issue. The only thing i changed was to set the dropdown field to "Hide to registered users". I removed this setting, but that does not change anything.

To be honest, your module is driving me crazy. For 170 $ i expect more than this.

Also, if a dropdown field "is generally not designed to be read only ", why the hell can i choose the "read only" property for a dropdown field?!

Now i set all my dropdowns to radio buttons, and let the user change it s values after registration. As soon as i have time, i'm going to write my own registration form.

Chad / Candace,

We are also running into the exact same issue. A drop down list, if set to read only for authenticated users does not save and reverts back to the default value upon registration update. What is strange is that the core DNN filed it is linked to still holds the correct value of the dropdown list but not in dynamic registration.

Is there a fix out there for this as of yet?

Dustin
10Poundgorilla.com

I setup a work around by creating a text box field that is hooked to the same core DNN profile property. The Text box field is displayed only to Registered Users and set to Read only.

The drop down list field is hooked to the same core DNN profile field and is only shown to anonymous users. So upon initial registration they can select the option, but once on registration update, they can see the option they choose via the text box field but can not edit it.

Dustin

Hello Dustin,

Thank you for your contributed knowledge of this work around.

I didn't initially see a question in your forum post, but if you do have any questions please let us know.

Thanks,

Ryan