DraggableViews

..makes views draggable

The DraggableViews module can be used to organize simple lists and complex structures via drag n' drop. The configuration is quite easy as you just have to access the style-plugin settings.

If you want it QUICK

1. Navigate to the edit-page of an existing view.
2. Add the field "Draggableviews: Order" at the Fields section.
3. Now change the Style-plugin at the Basic settings section to Draggable Table and enter the Style plugin settings.
4. Scroll down to the Draggable Table settings and choose the Order field you added just before. Choose "Native" handler.
5. Save the settings. You'll be prompted to sort the view by the Order field. Save the view and you're done.

Simple lists

See "If you want it QUICK".

Hierarchies

If you want to build hierarchies you have to set the parent field. Use "Draggableviews: Parent" and choose "Native" handler if no third-party modules tells you something else. The maximum hierarchy depth can be specified at Define the depth limit.

What you should be aware of

• Don't rely on the live preview. Commonly its output differs from the actual output.
• Using paging for large views with hierarchies can result in dramatic loss of performance because the view needs to be reloaded one to three times in order to display all relevant nodes. Actually this already takes effect when Items to display (Basic settings) are limited.

Third-party modules can implement their own handlers to save the structure information where ever they want. Always use "Native" handler if you don't use a third-party module that tells you something else. The fields "Draggableviews: Order" and "Draggableviews: Parent" (use both in combination with native handler only) are unique for each view but not unique for different displays of the same view.

Additional settings

• Show input fields?: You can decide whether order input fields (order, parent) should be visible or not (If javascript is disabled all fields will be visible anyway).
• Define the depth limit: You can constrict the user in building hierarchies. -1: Unrestricted. 0: No hierarchies allowed. 1: Only one hierarchy level allowed. 2: Only two hierarchy.....
• Node type: You can define certain node-types to be "root" or "leaf". "Root" nodes cannot be subordinated. "Leaf" nodes cannot have child nodes. (this options will only be shown if the views base table is "node")
• Show expand Links: If checked little blue triangular icons will be shown next to the first field of a parent row. The expand/collapse state will be saved after hitting the "Save" button.
• Default is collapsed: Self-explaining..
• Unique for each user: The user-ID will be used to store/read the expand/collapse states from/to the database.
• How many rows should be displayed of the previous/next page: This setting makes it possible to drag a node (or term, user, etc.) from one page to another. (only makes sense if Items to display are restricted)
• The user cannot rearrange nodes (locked): No drag handles will be shown. Rearranging will not be possible but indentation of subordinated nodes (or terms, user, etc.) will be themed.
• Behavior of new nodes: Self-explaining..

Native handler settings

• Use arguments as well as view ID to order nodes: The views argument will be used to read/write order/parent values to/from the database.
  If any display uses arguments (and defines the "DraggableViews: Order" field; Native handler assumed) all displays (non-"Draggable Table"-style-plugins) will use arguments in their queries too (except they tell us explicitly something else). See #565146: Defined order not respected when Style different than Draggable Table