Do not change timestamp
ultimateboy - November 10, 2008 - 17:22
| Project: | DraggableViews |
| Version: | 6.x-3.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Description
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.
#1
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.
#2
Works like a charm. Thank you so very much!
#3
After further testing, this patch breaks when using draggableviews to create a tree-like structure.
#4
Continued this patch to work with a tree like structure. Should work just fine.
#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
oh, I forgot:
therefore changing status to "won't fix"