1) I know this shouldnt be a problem with existing WPP (Payflow should also work fine with the same API)

2) There is a hook_order which can take care of this.

3) I think this should be possible and I suppose the guys already have a solution. My solution would be node api and add an extra check box. Check for the products which are shippable in the checkout/order screen and then only display the shipping address.

Honestly, I just think it's awesome that other people in the community are jumping at the chance to answer questions. I did have a chance to chat briefly with the folks at Warner Brothers and am excited they'll be using Ubercart. I imagine their name is at least a little more recognizable than our company's (Prima Supply... you haven't heard of it?).

Mostly, I just hope it works out great for the membership portions of their site! That was one of the most requested core features at Drupalcon, and having Shawn take care of that worked out great.

A little more insight on the issues where applicable:

1. A custom module can implement hook_order() and on the 'update' $op see if an order is moving from the in_checkout state to the post_checkout state. At that time, it can call uc_payment_balance() to see if the order has a $0 balance. If so, it can go ahead and move it into payment received. I had a lot of fun integrating Workflow-ng further this morning and have events for checkout completion and order updates. I'll probably be adding in a balance check in the morning, at which point you'll no longer even need a module to do something like this.
2. As cosmo mentioned, hook_order_update() would be applicable here again. Other possibilities would include adding a submit handler to the form uc_cart_checkout_review_form or creating your own Workflow-ng action (pretty simple) in a module and using that with my checkout completion event.
3. A few solutions to this popped up based on the responses in this thread and this thread. The latest Bazaar version includes a checkbox on the product node edit form to mark a node as shippable or non-shippable. I'm encouraging product feature developers to include this checkbox if applicable to their individual features if they may be applied to individual SKUs on a product.

All in all, today was a good day of coding, and I'm looking forward to tomorrow. My Alpha 8 Battle Plans are winding down... we just might get it out earlier than expected.

One issue I've encountered since I upgraded to newest version today... My products no longer want to save the SKU or price anymore. Is this something anyone else has encountered? Should I post a real bug report in the bugs section?

That's something I have also seen, but I thought it was because I had wiped my uc_products table clean, but had left data in the node table - so I was under the impression things weren't updating for some reason or another.

But I haven't been able to reproduce it. I would try uninstalling and reinstalling some of the modules .. make sure all of your tables are there

Seems the other guys aren't around .. and I am on West Coast time... I'm not sure what the exact problem you're having is. What versions of Drupal / Ubercart / PHP / MySQL are you running? Are you able to get into phpMyAdmin and adjust the price in the database directly? It seems that my issue was fixed after I did that.. but I also monkeyed around with a couple previously existing products.

I was at first not able to update existing products (they existed as nodes but not entries in the uc_products table) until I had added them in as products themselves. I'm wondering if truncating your database tables would help.

You say you start with a fresh install, but does that include a fresh database install as well? If you have old / stale data there, it could be causing an issue? My theory is that Ubercart is checking for a product as a node, finding it, and moving forward with the attempted query; but since a product doesn't exist, it doesn't actually update any data. That's where my "adding the entry to the products table" method came into play.

A bit convoluted, I know, but it's the best I can do without duplicating the issue. I can try a new install on another box and see if I get the same results as you.

For item 1 (PayFlowPro):

Has this module been successfully used by anyone, and is the contributor on the boards?

Glad to know you found it. I just updated to the current bzr version myself... I'll take a gander and double check. I had a feeling it was a silly database issue ..

@sarasioux: bug finder badge, ftw. Thanks for finding that... syncing install functions with updates can be easy to forget.

So I've been testing out the PFP module today, and in my infinite optimism I hoped that this module would be implementing hook_order as per Ryan's comment above to automatically move the order status to Payment Received. It appears as though it does not.

How does everyone else achieve this need? Doesn't it seem like this functionality should be a part of the PFP module itself? Should we start forking it & adding in this piece of the logic? Do people normally just write their own helper module to do these tasks? Is there some documentation I should be reading before asking these questions?

Thanks in advance for your continued support, sorry for being such an Ubercart newb I promise to be much more fluent in the coming weeks.

Much Love,
Sara