Editing Forms - Hidden Fields and Captcha
Permalink Browser Info Environment
I have 2 questions/requests please.
1. There is a field called a hidden field. I had thought/hoped this would be a field that would not display on the front-end but would be editable via the admin and likely even when displayed via Data Display on the front end. But this is not the case in editing the form in the back end. Is this a bug or intended that way. Otherwise I don't get the idea of a hidden field. (My intent was to have a few fields where an admin could add info to a form that would not be seen by non-admin.)
2. With Captcha enabled for a form, and in the admin area of the site looking at the form Results, if I click on the edit button, the Captcha displays, I assume requiring me to fill it in to make an edit from the admin area. I figure this is an error and wanted to point it out.
Thanks.
1. There is a field called a hidden field. I had thought/hoped this would be a field that would not display on the front-end but would be editable via the admin and likely even when displayed via Data Display on the front end. But this is not the case in editing the form in the back end. Is this a bug or intended that way. Otherwise I don't get the idea of a hidden field. (My intent was to have a few fields where an admin could add info to a form that would not be seen by non-admin.)
2. With Captcha enabled for a form, and in the admin area of the site looking at the form Results, if I click on the edit button, the Captcha displays, I assume requiring me to fill it in to make an edit from the admin area. I figure this is an error and wanted to point it out.
Thanks.
| Type: | Discussion |
|---|---|
| Status: | New |
1. Got you. I figured another solution for my needs in that case, and now understand the hidden fields.
2. Huh. I guess I couldn't imagine any developer allowing the general public access to edit content in a form, and thus if someone had access enough to edit, that they would then be pre-approved as such not to be a spammer. But I guess my assumption was too broad. You know your audience better than me, so I appreciate the potential option when you have time for the extra coding.
Thanks
2. Huh. I guess I couldn't imagine any developer allowing the general public access to edit content in a form, and thus if someone had access enough to edit, that they would then be pre-approved as such not to be a spammer. But I guess my assumption was too broad. You know your audience better than me, so I appreciate the potential option when you have time for the extra coding.
Thanks
Regarding CAPTCHA...I suppose you're right actually. :) There would be no need to have CAPTCHA when editing since no one is going to allow edits for unauthenticated users anyways. I'll probably just go ahead and make that adjustment so that it doesn't require CAPTCHA when editing.
CAPTCHA no longer required when editing. Change made in 1.4, posted 4-12-11.
2. I think I'd want to go the route of having an option like "Disable CAPTCHA for authenticated users?" or something like that, but that would take some time to code.