Custom Field & Order Forms

[10RUPTiV]

I think I found a bug.

 

If you create a custom field, for example, a text box and you set it to be visible to client but read only.

 

Then you create an order form with Registration, you will be able to enter some stuff in this custom field.

 

[10RUPTiV]

Any update about this bug ?

[Tyson]

I'm not able to duplicate this issue. Read only works fine for me. What browser are you using? Does it support the 'disabled' attribute on input fields? Are you sure you're viewing the correct order form for the client group for which you setup the read only custom field?

[10RUPTiV]

Tyson,

 

Not sure if it's resolv in 3.1 but I just re-test this morning with 3.1 and works fine.

 

The only thing I will add, it's the custom field is set to visible to client and read only.  I think that visible to client and read only need to be hidden in the registration form.  Client will try to write something and will probably tell us they can't fill the form correctly without knowing the field is for us not them!

[Michael]

I do this (Provided afterwards) in the Name. You could put something like (read only) (Staff use)

[10RUPTiV]

The problem I think, it's we use a custom field visible to client and read only, 'cause we need to show this information to the client.... but I don't want to see it in the registration form when a new client fill the form!

[Tyson]

Part of being "Visible to Client" means that they should see it. The distinction that they should not see it on the client registration order form if it is disabled may not be what most people expect. I'd be curious to hear what people think about this, or if it's preferred to have a new setting to make that distinction. I'd recommend opening a feature request for this.

 

As for the original bug report, I'm going to close this thread as not a bug.