I changed the view to use draggable, everything works except that when you save, rather than leave the order chosen by me, all upside without a clear criterion.

why?

attached pictures of the configuration.
thanks

CommentFileSizeAuthor
#5 draggableviews-[418068].patch946 bytessevi
2.jpg38.88 KBsanluca
1.jpg61.39 KBsanluca
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sevi’s picture

Hm, I'm stuck. Don't know O_o.
Do you use "exclude" option for any field?
Try to remove the views arguments to see if this causes the problem.

The html output may help me to debug. Can you upload the html output (or just the code of the concerned table)?

Junro’s picture

Title: Problems with draggableview native handler. » draggable view does not order

@ Sevi

I had never use native hander, and I test it all the day.

I 've got problems with it. Sometime I don't have any value in input fields. Sometime when I want to drag, my page reload and reload... I've got in the url things like ....page=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0......

I don't know what to think about native handler method. If I have to use native or cck handler...

Junro’s picture

With pager, my draggable views was working, I set pager: No. ---> Draggableviews don't work anymore... impossible to drag nodes... I've got no value in input field. So each time i drag the view, the display don't mean anything. The order changes everytime.

I create a little draggableview from scratch... it's working well.

Maybe i should start all my draggableview from scratch...
But I don't understand why it's not working when I change only the handler setting. It should work, no?

Junro’s picture

Title: draggable view does not order » Problems with draggableview native handler.

Is it not more safe (to keep the right nodes order) to use CCK handler?

sevi’s picture

FileSize
946 bytes

No, i'm sure, CCK handler and Native handler are equal in this context :)

Thanks for the last posts. Now I know what's wrong. I haven't test enough with items_to_display = 0.

The attached patch fixes this issue.

Junro’s picture

OK, thanks it's working, I continue to change cck handler to native handler with all my draggableviews.

Junro’s picture

With another draggableviews, after saving the draggable views, the page reload and reload and reload....

to each reload I've got one "?uid=Junro?page=" more.

...../Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=?uid=Junro?page=....

and:

Request-URI Too Large

The requested URL's length exceeds the capacity limit for this server.

ps: Same problem with both handlers, CCK & native.

mishoboss’s picture

Well, I have the same issue. I use the Native handler

mishoboss’s picture

Maybe I'm wrong with something... I would like to sort nodes via draggable view using the Draggableviews: Order. Then on another View I want to list these nodes ordered by Draggableviews: Order. Is this doable? I just can't make the nodes in the second View to sort by the order I made.

Junro’s picture

Draggableviews: order field is unique to a view, if you want to use the order of you're draggable views, you just have to create a new display (page, block...) inside the draggable views, and use another style.. like table.

sevi’s picture

Currently I cannot reproduce the reload reload reload bug.
What kinds of arguments and exposed filters do you use?

Junro’s picture

I'm using user: name as arguments, no exposed filters for this view.
It's strange because it's one of my simple draggable views...
Big ones work great.
I'm looking for where the problem could from but can't find.

Junro’s picture

Hum If I change the name of my draggable view page, it's working.

sanluca’s picture

I upgraded to beta 5 and everything works properly as in the first configuration with that

thanks

mitchell’s picture

Status: Active » Fixed

looks like this is fixed.

Status: Fixed » Closed (fixed)

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