I had to deal with this same problem when I wrote my Package Tracking module (http://www.ubercart.org/contrib/2852), because I needed to display a tracking number with a link to the tracking information on the order page.

There is no theme function to override here. That page is generated by uc_order_history(), so the whole function needs to be replaced. Without hacking core, I overrode the user/#/orders menu to call my own function instead of uc_order_history() - you can look in my code to see how I did this.

I think uc_order_history() could be re-designed so that it is easy to hook into. For this to happen, someone has to rewrite the code and post it as a proposal. I don't have the time myself.

Actually, what I REALLY think needs to be done is that "Order" needs to be a node type (for many reasons I've discussed before) instead of just DB tables as it is now. If that were done, then a page listing the order history could trivially be generated with views, and trivially themed to include/exclude/reformat information using the normal Drupal theming mechanisms. Ubercart's capabilities would be increased, while at the same time a lot of Ubercart code could be eliminated because this stuff would be done by core modules or other contributions. Again, I don't have time to tackle this project myself.

Two quick questions... would you also recommend taking the link off of the order number and maybe adding another operations link for the pop-up invoice? Also, I'm willing to entertain the idea of orders as nodes in UC 3.x, but I'm curious if the same problems would be solved by exposing order tables to Views 2.0.

Orders as node, OMG, is my wonderfull dreams will be realized ? ^^

The icons have never really "worked" for me - I always have to hover my mouse over the icons and read the tooltips to figure out which does what. So I personally would just turn those into text links for view, delete, edit, etc. I don't think it's necessary to add a link to the invoice in the order summary, since the first thing a user will do is drill down into the order view to see if it's what he wants, and the invoice tab is right there once you've drilled down.

Ryan wrote:

Also, I'm willing to entertain the idea of orders as nodes in UC 3.x, but I'm curious if the same problems would be solved by exposing order tables to Views 2.0.

That would help with a number of small issues. I wouldn't assign much priority to it though. The big win comes only when you switch orders to nodes, then things like the order summary list would just be a normal list of teasers that users can theme with css, theme functions, or templates! Data added to orders by contributed modules would then be automatically included in all the order views, rather than having to implement various ubercart hooks. etc. As you said, fodder for another thread...

Well... it could be wrapped in a theme function, but the theme layer isn't necessarily supposed to change something like all the contents of a table. It's more to be used for changing the HTML output of an element... if it's just CSS you need to adjust, I should be able to add a class to the table no problem.

I suppose what should happen is this should be turned into a TAPIr table, though I'll need to investigate how effective paging is with TAPIr right now. In fact, I think that might be the best thing to do right now. Reason being... when I look at the table in 1024 x 768 with two sidebars, there's no room for another column in the table. If I'm going to overcrowd it, I'd like for people to be able to turn off columns to make it fit in their theme. Thoughts on that? This would most likely then become a D6 feature only.