Possible to use as an administrative widget too?
Zach Harkey - October 13, 2008 - 01:37
| Project: | Autocomplete Node Finder |
| Version: | 5.x-3.1 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
This is a pretty cool feature to offer front-end users, however, the place where I could really use this is in the node edit form as an administrative widget.
My clients always complain about how cumbersome it is to reference certain kinds of nodes using the default Select List or Autocomplete Text Field where all you have to go by is the Title, which may or may not be the best way to search.
For example, it can be very frustrating to locate the correct Image node from a list of titles such as: DSCN_0001, DSCN_0002, DSCN_0003, etc. In these situations, the ability to use a teaser with a thumbnail would be an enormous usability improvement.
How difficult would it be to offer this as one of the CCK form widgets?
#1
This is a utility for finding nodes. Your administrators can use it for exactly that purpose as is.
However, this is not a CCK module, and I am not turning it into a CCK module.
Node Reference and/or Field Reference work closer to what you want. Maybe use theme functions to change the display of the autocomplete suggestions.
http://drupal.org/project/fieldreference
I suggest looking into using that module as it might already do what you want to do!
The only problem I can forsee is if you want to reference the whole node by the identified field, not just to reference the field by itself, and if Field Reference doesn't tell you which node it got the field from, in which case I think that stuff should be added to the module as a feature.
Feel free to toss around some more ideas as I'm interested in CCK reference modules too.
Well then how would you identify an image? Are you using keywords/tags or something?
I am confident the ability to do teaser suggestions already exists with nodereference and quite possibly fieldreference (if it follows the same code as nodereference) with a theme function.
The module you use as a basis would have more to do with what the user was typing into the input field.... if it was a node title then it would be nodereference, if it is a field value then fieldreference ? I assume fieldreference is based on field values not field names or node names....
#2
Thank you so much danielb for taking the time to outline so many great suggestions. I never even considered some of these approaches. I'm off to do some experimenting. I'll report back on my findings.
P.S. Field Reference looks very bad ass. Downloading now.
Zach
#3
--project followup subject--
Automatically closed -- issue fixed for two weeks with no activity.
#4
Automatically closed -- issue fixed for two weeks with no activity.