Closed (fixed)
Project:
Commerce Core
Version:
7.x-1.x-dev
Component:
Order
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Jul 2010 at 03:49 UTC
Updated:
3 Jan 2014 at 01:42 UTC
Jump to comment: Most recent
Comments
Comment #1
rszrama commentedComment #2
bojanz commented[23:29] bojanz: nah, nuke it
[23:29] bojanz: although I guess I'm a little undecided hehe
[23:30] bojanz: nah, it needs to go... needless UI atm I think
[23:30] bojanz: eventually it might be nice to make this a core feature, but I'm not sure it's necessary now...
[23:30] well, just having the hook is okay to me
[23:31] on the other hand, no need to nuke something which isn't broken
[23:31] bojanz: yeah, my thought, too
[23:32] bojanz: I'll think about it... I mean, we're allowing reordering of checkout panes via the UI in a similar manner
[23:33] bojanz: so it's not like we're keeping the core completely free from these "window dressing" features
[23:33] bojanz: I suppose the larger question is how often should we expect people to want to customize the order statuses... and part of me wants to say quite often
[23:34] one voice is telling me that's true, but the other is asking, customize to what?
[23:34] Not sure how much room for creativity there is in order statuses
[23:34] bojanz: that's true, and customizations might not be necessary... it would be mostly reordering and disabling some
[23:35] still, that requires an UI too..
Comment #3
pcambraComment #4
pcambraTasks
- Remove both tables
- Change reference of the functions of loading states and status so they don't use the tables
We'll figure out later what to do with those tables when order status/state UI is created if it is.
Comment #5
pcambrahttps://github.com/pcambra/drupalcommerce/commit/93714ce96d9039e6b6fe455...
Comment #6
rszrama commentedExcellent work - committed.