I have it working without a problem on beta 2, so if there's a bug it's something that was introduced recently. Do you by chance have your store default weight set to something other than pounds? Can you print the request XML as well as the response (remove your user ID from the request before posting!). It sure sounds like the weight isn't being sent (maybe an error in unit conversion...), or that part of the XML is formatted improperly.

Hmm, I could swear it just did it when you checked the debug box at admin/store/settings/quotes/edit, but trying it out it doesn't seem to show up. I don't know, it's late. Anyway, stick the following line in uc_usps.module in the function uc_usps_quote(), just after the first call to uc_usps_rate_request():

That's actually good news - it narrows down the problem considerably. Either the weights aren't set for the products or the weight calculation in uc_usps got screwed up. I suspect the latter, since you said you checked your product weights and because a lot of work has been done on the _uc_usps_package_product() function recently. Maybe Lyle can quickly spot the problem.

A quick way I use to see if the order weights are set right is to set up the Weight Quote shipping method to charge $1/lb. for shipping - that way on the checkout page when you get shipping quotes the shipping charge for Weight Quote will be = the shipping weight of your order. (Change this to $1/ounce if you want a more precise weight measure.) If Weight Quote gives the right answer then the problem is definitely in the uc_usps module.

I enabled the Weight Quote module, set $1/lb, disabled USPS (Domestic and International) in the Shipping Quote configuration, and am seeing the same issue. To be complete, I removed the product from my shopping cart, and re-added it, checked again. No dice. Removed it again, set the product's weight up in lbs so that it would be the same across the board, re-added, and am still seeing the same issue.

Alrighty...

I disabled the "Cart Links" module, which I had enabled, assuming I might use it in the future. The Weight Quote now seems to work with $1/lb. With USPS enabled, and Weight Quote disabled, I'm now getting

"There were problems getting a shipping quote. Please verify the delivery and product information and try again.
If this does not resolve the issue, please call in to complete your order."

This occurs without the XML error from USPS being spit out as it was before, even though the debug info is turned on. I looked in the uc_products table, and the weight is in there.

Updated to Ubercart 1.0b4, same issue...

Decided to do a little more digging...

If I turn off "all in one" in the USPS shipping configuration, it seems to work, but I'm getting this now:

Right, I had the debug XML on because it was not functioning with 'all in one'. It looks like others are having this problem, though. Does anyone have the USPS module confirmed working with 'all in one' enabled?

Moving along.
I've removed a shipping module I was not using and hoping not to use as it hasn't worked perfectly in the past, that module was the uc_tablerate module.
http://www.ubercart.org/forum/general_discussion/830/shipping_quotes_wei...
http://www.ubercart.org/comment/4203/Tablerate-module-alpha7e

Removing has helped somewhat. In that I am now getting quoted a price, albeit expensive and not correct one.

Yet under the price, it's still telling me to enter the package shipping weight.

I just installed beta 4 and unfortunately it looks like the weight of packages still isn't being calculated properly when you use "All in one". When I switch to separate packaging my quotes work fine; otherwise I get "please enter package weight" from USPS.

(drupal 5.7 / workflow-ng 5.x-1.6, if it matters)

I found the problem with the "All in one" option for USPS. Lines 547 and 548 should have $package[0]->weight instead of $package->weight. This has been committed to the bazaar repository and will be in the next release.

I went to change those two lines, but I only saw where to change it on line 546 and 547.
Here's what I have.

I'm getting this when I go to review my order with what I have above.
It's also not letting me continue on to checkout, it just brings the review page up over and over again.

You ran update.php? That error was a known bug with clean install in beta 3, which was fixed in beta 4. You do need to run update.php for the fix to work, and you should *always* run update.php when you update any Drupal modules.

Hmm, looking at the fix that was made to uc_attribute, it looks like it didn't completely fix the problem in the narrow case where you did a clean install of beta 3 then upgraded to beta 4. If you had done an upgrade from beta 2 to beta 3, or clean install of beta 4 (or above), or upgraded from beta 2 directly to beta 4, etc., there would be no problem. I'm not even sure that it's worth it to patch the module anymore to address that case, since it will be fine for every other case.

Anyway, to fix:
Go to admin/build/modules and uncheck the "Attribute" module, then save
Go to admin/build/modules/uninstall and completely uninstall the "Attribute" module
Back to admin/build/modules, reload that page then check the "Attribute" module again and save

(I tested this procedure on a beta 3 installation, and it eliminated the problem).

Unfortunately, that destroys any product attributes you might have set up. If you want to preserve your attributes, INSTEAD of the procedure above, you can execute the following SQL on your DB:

Well then, I don't know what to suggest, other than do a clean install. The procedure above results in a clean install of uc_attribute, so that should have fixed your DB table.

Look in your uc_attribute.install and see if it defines the function uc_attribute_update_7() at the bottom - if it doesn't, you don't have beta 4!

Look in your DB at the uc_product_attributes table using phpMyAdmin - the above procedure will create that table with a column named 'required'. If it didn't, you don't have beta 4.

I don't see how uc_attribute could have been re-installed without this column created, unless you don't have the beta 4 version of uc_attribute.

Please start a new topic for that issue - we're drifting pretty far away from this forum topic. (My guess is those errors come from using PHP4 - please state your versions of UC, PHP etc. when you post the new topic.)