First of all, lovely module. Works like a charm.

I have a request to not change the node's timestamp when saving the draggable view, or at least make it an option.

CommentFileSizeAuthor
#4 332523_do_not_change_timestamp_4.patch1.79 KBultimateboy
#1 332523_do_not_change_timestamp.1.patch19.55 KBcyberswat
#1 332523_do_not_change_timestamp.2.patch1.29 KBcyberswat

Comments

cyberswat’s picture

cyberswat commented
Status: Active » Needs review
StatusFileSize
new 332523_do_not_change_timestamp.2.patch1.29 KB
new 332523_do_not_change_timestamp.1.patch19.55 KB

FYI this patch is way larger than it should be as my editor cleaned up all the extra spaces and cruft to bring more in line with coding standards. So version 1 is a version that removes all the odd spacing and character returns while version 2 is a version that leaves them.

ultimateboy’s picture

ultimateboy commented
Status: Needs review » Reviewed & tested by the community

Works like a charm. Thank you so very much!

ultimateboy’s picture

ultimateboy commented
Status: Reviewed & tested by the community » Needs work

After further testing, this patch breaks when using draggableviews to create a tree-like structure.

ultimateboy’s picture

ultimateboy commented
Status: Needs work » Needs review
StatusFileSize
new 332523_do_not_change_timestamp_4.patch1.79 KB

Continued this patch to work with a tree like structure. Should work just fine.

sevi’s picture

sevi commented

There will be a fundamental change with the next release. CCK-support will be an option and order/parent information will be saved in special database-tables (no cck-field-creating any more :) )

Furthermore the programmer will be able to use his own draggableviews-handler, which handles saving (and outputting) of order/parent information. (reffering to #1176637: Support non-CCK weights). But I think you'll not need to create your own handler because the default implementation will not change the node.

sevi’s picture

sevi commented

There will be a fundamental change with the next release. CCK-support will be an option and order/parent information will be saved in special database-tables (no cck-field-creating any more :) )

Furthermore the programmer will be able to use his own draggableviews-handler, which handles saving (and outputting) of order/parent information. (reffering to #1176637: Support non-CCK weights). But I think you'll not need to create your own handler because the default implementation will not change the node.

Changes committed, development snapshot available soon,
greetings sevi

sevi’s picture

sevi commented

uups, double post :\

sevi’s picture

sevi commented
Status: Needs review » Closed (won't fix)

oh, I forgot:
therefore changing status to "won't fix"