[drupal-devel] [task] introduce node autofill

Bèr Kessels drupal-devel at drupal.org
Tue Jul 26 19:54:32 UTC 2005

Issue status update for 
Post a follow up: 

 Project:      Drupal
 Version:      cvs
 Component:    node system
 Category:     tasks
 Priority:     normal
 Assigned to:  Bèr Kessels
 Reported by:  Bèr Kessels
 Updated by:   Bèr Kessels
 Status:       patch

from the top of my head:
* a search.
* the book-parent selector
* clipper.module (node-node relations)
* anywhere else where you need to select a single node. 

About the types: I thought about that for a few seconds, but thought
* OTT. this works perfectly fine. Whenever the need for a type
subselector appears, it can still be added.
* userunfriendly. users should not have to bother about node types.

So, it was intentional that I left out types. 

Oh, And i am aware of any restrictions when there are a /lot/ of nodes.
youwill get a lot of nodes with similar titles. But that is a general
problem, which occurs in freetagging and user autofill just the same.

Bèr Kessels

Previous comments:

Tue, 26 Jul 2005 17:41:13 +0000 : Bèr Kessels

Attachment: http://drupal.org/files/issues/node_autocomplete.patch (1.25 KB)

This patch introduces an autofill for node titles.
It is not yet used anywhere, but at least we have the node/autofill url
available where contribs &c can query for node titles.


Tue, 26 Jul 2005 17:52:59 +0000 : Bèr Kessels

Attachment: http://drupal.org/files/issues/node_autocomplete_0.patch (1.26 KB)

this one adds rewrite sql :)


Tue, 26 Jul 2005 18:09:04 +0000 : chx

and so gets a +1 from me.


Tue, 26 Jul 2005 18:18:13 +0000 : moshe weitzman

How do you see this being used?

I wonder if developers will want further restrictions on returned nodes
like type=x, for example.

More information about the drupal-devel mailing list