One view to organize, one to display?

Well, I had a similer problem, and created a block with the ordering field visible, then a page with the ordering field hidden. The block is displayed only on the page view, in a sidebar, and only for admin users.

This issue can be closed, true?

I'm reopening this as a feature request.

I would like to have separate views (not separate displays) with one as the controller and one as front end. The way I would see this working is when you add the sort criteria one of its settings is the view that hosts the sort order. By default the current view would be used, but you could choose another view and potentially another display. If you were choosing another display the database schema would need to change, so I'm happy to not have that feature.

I haven't had a good chance to look at the draggableviews code, but I imagine when it defines the Views sort handler it can simply reference another value of the db column draggableviews_structure.view_name

subscribe

Well, yes if you use native handler, it is directly connected to view id. So it won't be possible to use separate views to build an order and then another one to show.

But in 7.x you are welcome to use Field API handler for field of integer type. I think you would be able to achieve your task. The idea is that you add integer field to your node and sort by this field.

Please let me know if it doesn't work and feel free to reopen this issue.

Well, yes if you use native handler, it is directly connected to view id.

I guess what I was suggesting is that it could be directly connected to any view. I'm aware this would require changing the architecture of the module. I have achieved what I need with the Field API, but was trying to avoid creating a weight field. If I wanted to display the same node in two different views in a different order I would have to create two weight fields.

If we remove views key from native handler then if you would need to have two different orders it wouldn't be possible as well.

Please share your opinion how better to do achieve what you need with native handler.

I never said to remove views key. My idea would be to allow the display view to specify a controller view. The controller saves it as per normal, but the display can read from a different view name / display / args.

Yes, that is very good idea! Thanks for explanation! Moving issue back to active state.

Going to implement this feature in 7.x-2.x branch. Moving to different branch.

Now it is implemented. So welcome to test. Marking this issue as fixed.