I need some help troubleshooting a new install of Ubercart 2.x with the latest dev version of the Canada Post Shipping Quotes module. I think that I've installed things correctly and set up an account with Canada Post SellOnline and got a CPC ID to use.

The shipping quote blocks are appearing where they should but I never get any quotes: all I get is the shipping quote error message that is configured in the the Quote Settings tab.

However, no actual ubercart errors are showing up in the watchdog/dblog. Maybe my ISP is blocking port 30000?

Possibilities:
- My config is wrong
- My server is not passing the request on correctly
- The Canada Post server is down and/or rejecting my request for some reason
- The Canada Post response is never received

Am I right that any of those things might be happening and nothing would get written into my dblog as a failure/error? I've enabled "Log errors during checkout to watchdog" and "Display debug information" and I've logged in as user 1. I tried using DrupalForFirebug during checkout but couldn't figure out where to look. Could someone maybe help me figure out how to drop some code into the latest dev version of this module in order to test for a couple of these possible culprits? Or where to look in DrupalForFirebug?

Phil.

Comments

pkiff’s picture

pkiff commented
Issue summary: View changes

Noted that error logging was enabled.

pkiff’s picture

pkiff commented

Made some progress on this simply by changing the setting to allow purchases to go through without a completed shipping quote. When I do that, the shipping quote errors get written into the dblog the way one would expect. It looks like the module is creating a well-formed request. More and more I am suspecting that inbound port 30000 is blocked.

adraskoy’s picture

adraskoy commented

Same problem. Trying to set up Canada Post shipping quotes. They are failing with the standard message, but no debug-to-admin messages, or dblog messages. Seems like a bug to me. If the shipping quote fails and the appropriate debugging settings are enabled, an error should be logged. There's nothing more frustrating than an error message that says "There was an error" and nothing else.

tr’s picture

tr commented
Status: Active » Closed (cannot reproduce)

Not returning a quote isn't a "failure" - it's a normal, expected response of ANY shipping quote module when the conditions are such that no quote can be returned. For example, if you're trying to ship a product that's over the 30kg Canada Post weight limit, Canada Post will not return a quote. That's not an error.

The standard Ubercart "There were problems" message shows when none of the enabled quote modules can provide a quote. That's a configuration problem on your end - you should make sure that you have quote methods configured to cover every possible case. In my example above, that means you should have something like a flat rate method defined for when packages are too heavy.

If you want to figure out where your configuration is wrong, you will have to do some work on your end. First make sure you can get a flat rate quote and a weight-based quote. Perhaps your products don't have any weights defined. Look at the request being sent to the CP server and the response returned from the server. Perhaps you haven't set your ship-from address. Lots of things could be wrong, and there are literally hundreds of posts in the Ubercart issue queue in this issue queue, and on ubercart.org telling you how to debug shipping quotes.

tr’s picture

tr commented
Issue summary: View changes

Ubercart 2.x not 6.x.