Active
Project:
UC Profile
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
15 Nov 2009 at 07:49 UTC
Updated:
17 Nov 2010 at 22:25 UTC
in admin/store/orders/16 for example
Comments
Comment #1
indytechcook commentedGiorgosK, The data isn't stored against an order, it's stored in the profile only.
I can see a need for have the data associated to an order. I'm changing the title to reflect the feature request.
Comment #2
feuillet commented*subscribe
Would like to see this too...
Comment #3
derhasi commentedAs profile information is associated to a user, I think this should stay so. But maybe some profile-revision/-versioning module, like it is possible with nodes, could solve this fact, so an order can link to a specific profile version, instead of the current profile.
Comment #4
EvanDonovan commentedI think this is out-of-scope for this module, and thus "won't fix", if I am understanding correctly.
The reason I say this is the module is intended to do a simple integration between Ubercart and Drupal's core profile module, via providing a checkout pane. To track data on an order-by-order basis would essentially either mean tracking it in nodes (i.e., CCK), or else using a custom database table, which is a different kind of integration entirely.
Drupal core profile tables have no versioning capability. To extend them to have such is to step outside the (limited) architecture of the profile.module.
Anyone else have thoughts?
Comment #5
EvanDonovan commentedTagging.