Project:DraggableViews
Version:6.x-3.1
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:closed (won't fix)

Issue Summary

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.

Comments

#1

Status:active» needs review

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.

AttachmentSize
332523_do_not_change_timestamp.1.patch 19.55 KB
332523_do_not_change_timestamp.2.patch 1.29 KB

#2

Status:needs review» reviewed & tested by the community

Works like a charm. Thank you so very much!

#3

Status:reviewed & tested by the community» needs work

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

#4

Status:needs work» needs review

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

AttachmentSize
332523_do_not_change_timestamp_4.patch 1.79 KB

#5

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.

#6

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

#7

uups, double post :\

#8

Status:needs review» closed (won't fix)

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