Not working with Group By feature

#54 isn't really working for me. I have a taxonomy with hierarchy where a parent's children may have the same labeling as another parent's children (e.g., Term A > Financial, Term B > Financial). They get their own tables appropriately, but they don't consistently get the draggable crosshairs. I think it looks like the second table with the duplicate labeling is the one that doesn't get the draggable options.

I found an issue with the patches when table titles were not unique. Tables with the same title inside the same view get the same HTML ID. Because of this, the tabledrag JS is not applied properly.

In my case, I was using 2 group by clauses - by primary category and secondary category. With the secondary category usually empty, I had many subtables with an empty table title (title = ""), and all of them had the same ID.

I'm not sure how this should be fixed. I've attached a patch that extends #54 which works for me, but it's not a very clean one.

I found an issue with the patches when table titles were not unique. Tables with the same title inside the same view get the same HTML ID. Because of this, the tabledrag JS is not applied properly.

In my case, I was using 2 group by clauses - by primary category and secondary category. With the secondary category usually empty, I had many subtables with an empty table title (title = ""), and all of them had the same ID.

I'm not sure how this should be fixed. I've attached a patch that extends #54 which works for me, but it's not a very clean one.

Patch #48 worked for me on version 2.1.3 of the module

Patch #48 worked for me on version 2.1.3 of the module also.
Thank you

just found out - if you add new node (if there is group by)...it will create a temporary table until anyone click SAVE Order.
so this is not good I would say.

Patch #54 worked for me on version 2.1.3

Well, it seems #54 can't be applied to 2.1.x anymore.
So here is a re-roll of it for 2.1.x.

As the module moved to 2.x and the patches also, lets set that in the version of this issue report also.
FYI: I did not test the functionality so can't confirm this works and you should read previous comments.

This patch is not working for me, I am grouping by taxonomy terms and loading it through a relationship.

I was able to reproduce the problem, and verify that the patch in #63 resolved the issue. I tested with a list field, with a taxonomy reference field (displaying as a label), and I also verified that this module still worked with an ungrouped view after patching. Merged in, so that simple use cases can be resolved.

@nicxvan Yours sounds like a most complex use case, so please file a separate issue for that, including detailed steps to reproduce.

Looks like this was committed as of June 1, 2024. Could someone confirm?

This is already marked fixed.

The commit was actually May 28th, but it's in 2.1.4 which was released on June 1st.

Is there a specific issue you're having?

Automatically closed - issue fixed for 2 weeks with no activity.

No, just double checking to make sure the patch is now obsolete.