Allow admins to hide prepopulated fields
JBrauer - April 28, 2008 - 06:07
| Project: | Prepopulate |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | patch (code needs work) |
Description
I had the need to allow users to hide a field if it had been prepopulated. There are perhaps some downsides to this as it pertains to users mistaking this for something that would prevent changes. In the use case we had it was simply to create links to create documents with a fixed taxonomy. The patch also includes a couple of coding style cleanups (very minor).
#1
#2
Er... Not quite sure why the last patch seemed to work at some point... because it clearly doesn't really work. So here's version 2 of the patch.
#3
This sounds like a great feature and one the I may like to use. I've not installed the prepopulate module yet, so can you give me a run-down of how this feature works. E.g. What options are available? Can an admin determine which prepopulated fields will be hidden? etc...
Thanks
Ian
#4
It doesn't allow an admin to work on a field-by-field setting... that would have to be added as more GET arguments. It allows the administrator to say on a content type basis whether the prepopulated fields should be hidden on the form.
#5
This is a bit different now in 6.x-2.x (HEAD code) where we have removed the node type checkbox and prepopulate now works on all forms. I'm sorta thinking I'd rather have a settings page that lists content types and lets you select which ones will be hidden rather than spreading them out to each content type page.
Also we need to make it clear that this can only be set on content types (not any other kind of form.) We could also just have a "master" toggle that either hides or shows all of your prepopulated fields on all forms on the site.Giving folks both options (global or by content type) or some variation(s) of that needs to be determined and make sure we come up with a clear UI for selection.
I'm going to move this to v2 and needs work due to this.