Previous versions of nodequeue allowed you to stage a "batch" of content in a nodequeue by incrementally adding nodes, and then pushing the queue's contents live in the corresponding view by saving the queue when you were done.
Is there a way to keep the "add" and "save" functions separate?
Thanks,
Dave
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | nodequeue-add_without_saving-572918-11.patch | 5.59 KB | jenlampton |
| #7 | nodequeue-add_without_saving-572918-7.patch | 3.56 KB | janchojnacki |
| #6 | nodequeue-add_without_saving-572918-6.patch | 4.54 KB | firebird |
| #5 | nodequeue-add_without_saving-572918-5.patch | 4.55 KB | firebird |
Comments
Comment #1
ezra-g commentedThis is a good point -- This is a distinction that was eliminated when we moved to the new queue ordering interface. I would accept a patch to incorporate it back in.
Comment #2
EmanueleQuinto commented+1
My users are screaming for this: you can't reorder, you can't modify, you can't reverse/shuffle.
I didn't have yet the time to work on a patch but, to me, this should be considered a bug, and a serious one.
Comment #3
ezra-g commentedSince you can still order the queue without saving, this seems like a feature request to me. Patches are welcome.
Comment #4
amateescu commentedPutting on my to-do list.
Comment #5
firebird commentedHere's a patch that adds this functionality.
Comment #6
firebird commentedRemoved whitespace errors.
Comment #7
janchojnacki commentedMade patch work for adding multiple items. Also removed javascript validation because it validates anyway on adding item.
Comment #8
killua99 commented#7: nodequeue-add_without_saving-572918-7.patch queued for re-testing.
Comment #9
jenlamptonChanging branch to 2.x since the patch still applies cleanly, and this might be a good first step for #2280415: Unable to add/remove+rearrange nodes to queue without also saving before all desired changes are made
Comment #10
jenlamptonAlso, nice work! Patch still works perfectly and is a massive UX improvement! :)
Comment #11
jenlamptonHm, looks like that broke tests. This should fix it.