Closed (fixed)
Project:
Entityqueue
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Dec 2013 at 22:44 UTC
Updated:
28 Jun 2014 at 21:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jojonaloha commentedAttached patch to uses the Drupal.theme('tableDragChangedWarning') for the warning message. It also tries to mark the table as changed when adding an item in Drupal.tableDrag so that:
only shows one warning message. The one weird thing still is that when you click one of the "Shuffle", "Reverse" or "Clear" buttons, the message shows the first time, but because we are replacing the whole form it disappears the second time and the table is already marked as changed, so adding or rearranging items doesn't display the message anymore either.
I also think this patch conflicts with the one in #2157159: Dragtable widget does not work with multiple instances of a form on the same page. I might combine the issues since they touch a lot of the same code. It might also be nice to use the same ajax callback for both the field widget and the "Shuffle", "Reverse" and "Clear" buttons, since after this patch they are starting to look very similar.
Comment #2
jojonaloha commentedIt'd help if I actually attached the patch ;)
Comment #3
arcane commentedDidn't completely work for me. Applied the patch, but I still get an extra line that displays "Show row weights" for each addition that pushes the table down. It does limit the warning to only display one time.
Comment #4
dmitriy.pokhodenko commentedHere is the patch based on #2 answer. Should solve problem with duplicate warnings and also solves problem with tabledrag switcher.
Comment #5
joelpittetAwesome, I this a try and did fix this issue for me.
Thanks @dmitriy.pokhodenko and @jojonaloha
Comment #7
jojonaloha commentedNice work @dmitriy.pokhodenko!
Committed 7c84cc7
There was a whitespace issue, which I corrected, and an added line that wasn't needed. Attached is an interdiff between what was committed and the patch in #4.