Why not use CCK date fields instead of using a custom built solution? An option in the Product Content Type settings could ask a user to select which date field (created first under manage fields) to use as the LTO datefield. This would not only already be integrated with views, but would give a user much more flexibility in what he could build.
Thoughts?
Comments
Comment #1
JGonzalez commentedNote - The functionality I'm talking about is similar to how Ubercart does for the product image
"Product image field:" -> select a cck image field.
Comment #2
JGonzalez commentedSomething along the lines of this, and removing the custom datefield all-together. Would provide a patch to do this but I suck at writing stuff back to the db :-\. Only have gotten this far.
Comment #3
BManuel commentedSubscribing
Comment #4
WebNewCastle commentedHi,
Thank you very for the suggestion and contribution. I apologize for the delay acknowledging this. It's been a busy month, but I am going to try to schedule time to take a closer look very soon. And I think this is something I should review further before moving forward with the process of Views integration - since that process would change if this is included.
- Matt
Comment #5
g.k commentedSubscribing
Comment #6
bturoque commentedSubscribing
Comment #7
wallbay1 commentedsub
Comment #8
avpadernoI am closing this issue, as Drupal 6 is now not supported.