Posted by a_c_m on February 20, 2009 at 2:27pm
4 followers
Jump to:
| Project: | Nodequeue |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
Currently on the admin page there is no pager, this means when you have very long lists (1000 + items) the page takes quite a while to load.
It would be really good if there was a pager added to the admin section, perhaps with a per queue items per page.
Comments
#1
Unfortunately you would then have to have a way to move queue items from one page to another.
I'm not sure 1,000 length queues are an appropriate use of nodequeue; you may want flag.module for something like that.
#2
We will look at migrating to flag, i assume its better at dealing with larger data sets?
However as nodeque's re-ordering is not a ajaxy drag and drop re-ordering, but a "one position at a time" movement (or jump to top/bottom), i dont see the problem in moving from page to page. If you move +1 on the top of page 2, you go to the bottom of page 1, etc. But i've not looked at the code so may be making incorrect assumptions.
#3
As with the latest AJAX drag'n'drop feature I run out of memory with my large nodequeues, I'd like to implement a paging option for nodequeue. So far, my idea is to
1) add an option "number of nodes to be displayed on nodequeue reordering pages (enter 0 for unlimited)" to the admin page
2) add the possibility to change the number and the offset of nodes to be displayed on each nodequeue reordering page
I only want to reorder the last few nodes. But if I really want to push one node to a different page, I can do so by using the offset option. I'd implement all these features purely optional so that the default behaviour does not change.
Additionally, I'd like to
3) add options "show shuffle button" and "show reverse button" to admin page
The reason for 3) is that I use nodequeue as an archive and don't want to accidentally mess it up.
What do you think of these ideas?
#4
@bartolomeo If you don't wish to change the order of nodes, then Nodequeue might not be a good fit for you. You might want to use a cck integer field and enter an order for a node, or sort by an existing field, or another method that more appropriately fits your use case.
What's the size of your php memory limit? If you wish to address Nodequeue's memory footprint, you might be interested in helping with the patch at #462290: Move admin functions to separate .admin.inc .