What a great module !
I want to use it for a picture gallery with a couple of pages. The user can order the pics using draggableviews and he can decide how many pics each page contains: All Pics with the same weight_level1 are on the same page - this is easy be done with view+arguments.
BUT: therefore the numbering of weight_level1 has to start with "1" (or maybe 0) but after some rearranging the lowest Number is growing on...
Question: is there any way to force a reorder beginning by 1 (or 0) ?
Thank you !
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | draggableviews_paging.patch | 8.27 KB | sevi |
Comments
Comment #1
sevi commentedIt's not prospective that draggableviews will support paging in the future.
Maybe someone will implement this at some point.
Comment #2
sevi commentedOk, future is now :)
With the attached patch draggableviews supports paging.
Each page has its value-range (ascending) which means that e.g. order values on the third page cannot collide with values on the first page.
There's another change coming with this patch: Now the number of order values displayed equals to the number of listed (visible) nodes.
This patch affects both native handler and cck handler.
The only (still remaining) problem is that you get always redirected to the first page (e.g. after saving the third page) (see #332632: Drag nodes using an exposed filter doesn't work.).
I hope this works so far,
please try and report,
greetings, sevi
Comment #3
sevi commentedI think this issue has been fixed in the meanwhile. The module changed very much. In order to provide paging the order values have to start with "0" (increasing with each node, without any gaps). With the latest changes (available with the next snapshot) the module seems to be very stable.
Please try the dev-version and report,
greetings,
sevi
Comment #4
sevi commentedComment #5
sevi commentedComment #7
kle commentedThanks - I will try this by my next projekt !
Gruesse aus Hamburg