Posted by sushmsn on September 16, 2009 at 7:15pm
Jump to:
| Project: | Node Hierarchy |
| Version: | 6.x-3.x-dev |
| Component: | Autocomplete Widget |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | Autocomplete in Node hierarchy |
Issue Summary
There should be a better way to select the parent of a particular node. Like instead of a selection list, if it were a Autocomplete it would be better.
This is a big problem when the number of nodes are high. It makes it difficult to select from thousands of nodes.
Comments
#1
Anyone have an input on this? The site I'm working on has thousands of nodes in the hierarchy and it takes a number of seconds to load up the whole "Node Hierarchy" picker that lists all candidate parent nodes.
Honestly, my site is running in Drupal 5.x as well - are there significant improvements to performance that have been made in Drupal 6.x that would be helpful to look into backporting?
Thanks!
#2
One solution: we cut down on the time it takes to open a Node Create/Edit page by about half by adding an index to the "parent" column in the "nodehierarchy" table in our MySQL database.
#3
I have added an experimental autocomplete widget to the latest 2.x dev. To enable it, turn on the 'Node Hierarchy Widgets' module now included with Node Hierarchy.
I'm not really planning on backporting this to D5 or to the 1.x branch so hopefully this will be useful to you if you upgrade.
#4
Ronan,
Thanks for the update. I'll try to check out the widget sometime soon.
It seems like it would be helpful to site performance out of the box to add Indexes to database columns. I mean, it wasn't hard to add them once we realized they weren't there, but I kinda expected the table to have indexes. Any plans on adding them to existing versions? Any reason why this has not been done?
#5
Automatically closed -- issue fixed for 2 weeks with no activity.
#6
I have a request for the autocomplete field. Can it be set to only show a max of 10 items in the drop down? Right now, my drop down shows every node that I have. Next, can it be set to "starts with" instead of "contains?" It wants to try every option when you are typing the name in right now. I tried to look in the module to see if I could change the settings, but couldn't find out how.
Thanks.
#7
I just realized that if you have edit rights to the parent, the autocomplete works perfectly. If you don't have edit rights, you get a dropdown choice of every node and the auto typing doesn't work right. Seems to start at the beginning of the list.
#8
Sorry I haven't gotten back on this. I'm not sure what you mean by your last report. You mean a node exists with a parent and when an editor who doesn't have edit rights on the parent tries to edit the child node they get the weird results in the autocomplete?
#9
#10
Moving this to the 3.x branch and reducing the priority. This feature was a haste implementation for the 2.x branch however a proper way of implementing it will more than likely happen in the 3.x branch. This feature will undoubtedly be closely involved with #1110196: Permissions Framework.
#11