Closed (duplicate)
Project:
DraggableViews
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 Sep 2009 at 14:44 UTC
Updated:
9 Feb 2013 at 06:47 UTC
Jump to comment: Most recent file
Comments
Comment #1
sevi commentedThe "group by" functionality was kicked out by me. Actually it has never worked.
This would require completely different configuration as well as a different settings form. I plan to implement support for the "Grouping field" for the next releases.
Comment #2
cybernomad commentedHi sevi,
thanx for the reply, waiting for the new releases then, you guys are doing a great job
Comment #3
aether commented+1 for the return of this functionality.
Subscribe.
Comment #4
joachim commentedI'm interested in this too. Being able to order nodes and move them between terms too would be very useful.
Comment #5
dixon_Moving items between terms can be quite tricky as that would mean a
node_save()needs to be triggered with the new term. And with all the possible types of argument, a system like that could be very complex.Comment #6
aren cambre commented+1
Treating the taxonomy term as a parent-child relationship may be an alternate solution.
Comment #7
Michael Zetterberg fd. Lopez commentedsubscribe
Comment #8
squarecandy commented+1 for this.
PS - Awesome plug in! Intuitive admin interfaces make everyone happy.
Comment #9
my-family commentedSubscribe and thanks for this module.
Comment #10
geek-merlin+1
Comment #11
iamjon commented+1 This functionality would be awesome!!!
Comment #12
fearlsgroove commentedAttached is a simple starting point that works for me. You can drag items within a group, but not between groups.
Comment #13
Rob_Feature commentedI've got #12 running on a production site and all works well. I'd suggest we get this rolled into the dev release if more can test it. Marking as reviewed.
Comment #14
burgs commentedThis is fantastic. Any chance we can add dragging between groups?
Comment #15
Rob_Feature commented@burgs
I think the comment was made earlier (and is quite true) that dragging between groups would actually have to alter node data (ie. remove one term and add another to a node). I think that's overstepping the purpose of this module.
This is really an ordering module, not a node alteration module. So, I might suggest that keeping dragging within groups is a good path and that dragging between groups might not be good for this module's path forward. That's my 2 cents.
Comment #16
geek-merlin@rob
i dont see a problem in group ordering.
changing a taxonomy field for every node seems not too different from changing a parent field for every node!
Comment #17
aren cambre commentedProbably should get this in on v7 first since it's a new feature.
Comment #18
baaj commented+1
Comment #19
jdln commentedSubscribing.
Comment #20
JayKayAu commented@axel.rutz - However, what happens if the Grouping field isn't a Taxonomy term?
For example, I have a view where Candidates are listed, grouped by an Agent, which is a nodereference field. So in that case, dragging between groups means changing the nodereference on the Candidate nodes.
In a general sense, this could get a little tricky, as the grouping field could be of any CCK type, which means to drag to another group means knowing how to reassign values of any given CCK type. I have no idea how hard this could be, but I suspect it's not trivial.
On the other hand, perhaps inter-group dragging could be done on fields you KNOW to be a taxonomy term, or other known type of field. So you could provide this functionality but limited to only supported types. That could still be quite useful.
Comment #21
geek-merlinah ok, i think i get your point:
is it possible to change and save a field value generically, without knowing its type.
dont know, but a quick peek in the source looks like no big problem.
we already have a type switch in implementations/draggableviews_handler_fieldapi.inc
which suggests that only noderef needs special treatment.
and wow, i hope i find some time soon to look into this, this looks like very good and well commented code!
Comment #22
elly commentedsubscribing - is the patch in #12 for the d6 version? very interested in being able to group draggable views by fields in d7.
Comment #23
mstrelan commentedsubscribe
Comment #24
sachbearbeiter commentedsubscribe
Comment #25
xtiansimon commentedThe patch above was submitted during the status as a 6.x module. Only this issue was moved to 7.x for integration, and I see it also under Pending Patches as 7.x.
Is this patch on this page OK for DraggableViews 6.x-3.5 testing?
UPDATE: Tried to apply this patch to zero success. I'm a newbie to git, so maybe I didn't do it right?
UPDATE2: applied the patch manually. No errors; however, the views list is draggable across groups. The inverse was described above and is the desired behavior.
Comment #26
webankit commented+1
Comment #27
steinmb commentedReading up on the thread. +1 to this feature in 7.x, but from what I can understand, is this patch for the ver. 6 version of dragableviews and Views 2. To get with working with Drupal 7 we port this patch to Views 3, and merged it with dragableviews-7.x-1.x-dev.
Comment #28
bluesband commented+1
I need group by feature for any field, like html list format. Thanks.
Comment #29
mindaugasd commented+1
Comment #30
mattsmith3 commentedwow... really needed this for a project. confirming that patch isn't working on d7 and views 3.
here to test when someone can port this patch.
Comment #31
cindyr commented+1
Comment #32
lorenlang commented+1 - could REALLY use this on my current project as it would be so much easier for my end user than manually setting weights
Comment #33
istryker commentedThis issue was tagged 7.x-1.x-dev. This branch is now unsupported.
In the latest 7.x-2.x-dev I was able to Group By with Native Handler. Draggableviews 7.x-2.x-dev currently doesn't support Taxonomy Terms, though there is 2 issues that are rtbc, and is on the TODO list.
#1716912: Add a taxonomy term weight handler
#1851752: Drag handler for saving weight into any column in any base table
I am marking this as duplicate of #1514116: Group by support, multiple native sorts per display. Comment #3 has an tarball example which is what I tested with.
If you want this to work with 6.x-3.5, please open an new issue.
If you want this to work with taxonomy handler & 7.x-2.x, please open a new issue.
I am closing this issue as this is an