Ubercart Order Node

Thanks for the pointers joachim, I've committed a couple of changes to address them. Changing the status of this issue back to needs review so you can take a look... (thanks again!)

Quick summary:
- Got rid of the $Id$ lines.
- Fixed the @file comments in all files.
- Added @param comment lines where necessary.
- Changed a bunch of my comments to use sentence case rather than title case.
- Made all comments into complete sentences.
- Added a bunch more comments to uc_order_node_edit_from to explain what it's doing and why.

As for your last suggestion (using hook_node_info() to define an order nodetype in code), I agree that it would reduce complexity to define the nodetype in code. I decided against doing that for two reasons: 1) I generally prefer when modules don't make that kind of assumption (just my own opinion), and 2) (more importantly) the feature was requested by another user so I made it happen (http://drupal.org/node/1080698).

Thanks for the review.

This module differs from the three cited in that it's purpose is to provide admins who are managing orders a way of giving more information to an order via the node type's CCK fields. When an admin is looking at an order in the Ubercart interface, they see an order pane with the node's edit form embedded, so they can change values of data. This is in contrast to the three modules above, which are all centered around allowing customers to add more information during the checkout process.

The best way to demonstrate why this is different is with a direct example. Imagine a company that has a dozen sales reps on the phone with customers, taking orders and entering them into Ubercart via the backend order admin interface. With this module, the company can define any number of customizable fields to add to the order, such as the Sales Rep's name, the date when the order should be shipped, etc. These fields are not for customer use, but they are essential to the day-to-day management of the orders in the system. And combined with the Views module (which this module provides support for) and the Views Bulk Operations module, a fully customized order management interface can be created with filters for finding orders quickly based on the node and CCK fields associated with them.

Ubercart does not have a way currently to add custom fields to an order for order management purposes. This module bridges that gap with minimal code to seamlessly integrate a node into the order interface. The node's edit form is displayed when you are on the "Edit" tab of the order, and the node's view is displayed when you're looking at the "View" tab of the order. All of it works without having to leave the page you are on, which is essential when you're on the phone with a customer taking down their information.

Great! Thank you so much!

I am currently using this module on a site that will be going into production soon. We've been banging on it pretty hard, and it's working great thusfar.

You betcha: http://drupal.org/project/uc_order_node