Hi,

I got an API key, installed the module and tried to enter the key in the Shipping settings. It gave me an error saying the API key had to be numeric,.

So I guess that's one thing, would be good if people could just paste the key they get in, and the dashes could be stripped automatically when it is used.

Then it kept saying I wasn't authorised to use the service after I removed the dashes to get it to work. I tried working with the Aus post API via CURL, and it won't work with an AUTH KEY which has the dashes removed. If I do remove the dashes, I get the same error on the command line I get when trying to put the API key into this module. So I think the module shouldn't worry about stripping dashes in any case.

How far away is this module from being production ready btw?

Comments

elc’s picture

elc commented
Assigned: Unassigned » elc

Your key has dashes? Hmm.. that is a different format than the one I have, as mine just looks like an MD5 hash and so did the 3 before this one. Could you post a composite of your key please? eg. N for number, A, alpha, - for dash etc. making it look like NNANANANANAA-NNAAN-AN. There's some simple validation in there as I expected all keys to be MD5 hash like, but if that's incorrect, I'll rethink the validation of it. I do also check with AusPost to see if the key is valid so I may reduce it down checking if the key is safe ASCII. They have to be used exactly as it is given by AusPost, so removing the dashes will not work. There is no specification of what a valid key is, so I made it up based on what I had.

I am in the middle of doing some cleanup of the Packing API, and testing a new method. There is an updated README.txt file with a "State of the Module" section in it which explains where it's all at.

Essentially, the module will take the contents of the cart, pack every single item in its own package, ask the AusPost PAC API for a quote on each of those using all of the available and enabled mutually exclusive shipping options, sum the results, and present them as a choice to the purchaser. No sub-options are used.

If that's all you want out of the module, then it's production ready ;) What probably doesn't make it ready is that I'm not taking any care to keep the settings/database/internal API's safe between pushed updates at present. I'll only start doing that once I hit a tagged release such as an alpha. At the current rate, that should be by the end of the month, but that is subject to change based on how busy I get.

elc’s picture

elc commented
Status: Active » Fixed

I signed up for another key and received one which matches your description, and is completely different than the one I was originally assigned. I have updated the validation of this field to be a lot more liberal, allowing any string of letters, numbers and dashes to be accepted.

http://drupalcode.org/project/uc_auspost_pac.git/blobdiff/f3c631d1d1ede9...

Thank you!

camerongreen’s picture

camerongreen commented

Great thanks, accepting the key now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.